Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754406AbYKHOqh (ORCPT ); Sat, 8 Nov 2008 09:46:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753317AbYKHOq2 (ORCPT ); Sat, 8 Nov 2008 09:46:28 -0500 Received: from tim.rpsys.net ([194.106.48.114]:45096 "EHLO tim.rpsys.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753060AbYKHOq1 (ORCPT ); Sat, 8 Nov 2008 09:46:27 -0500 Subject: Re: 2.6.28-rc3-git1: spitz still won't boot From: Richard Purdie To: Russell King Cc: Dmitry , Pavel Machek , Eric Miao , Cyril Hrubis , lenz@cs.wisc.edu, kernel list , Dirk@opfer-online.de, arminlitzel@web.de, pavel.urban@ct.cz, thommycheck@gmail.com In-Reply-To: <20081107182311.GA28600@flint.arm.linux.org.uk> References: <20081031150601.GA1457@ucw.cz> <20081105142329.GA1724@ucw.cz> <20081105173303.GC2038@elf.ucw.cz> <20081106080416.GA1531@ucw.cz> <20081106191424.GA2273@atrey.karlin.mff.cuni.cz> <20081107142923.GA1616@ucw.cz> <20081107182311.GA28600@flint.arm.linux.org.uk> Content-Type: text/plain Date: Sat, 08 Nov 2008 14:45:40 +0000 Message-Id: <1226155540.5379.5.camel@dax.rpnet.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1838 Lines: 48 On Fri, 2008-11-07 at 18:23 +0000, Russell King wrote: > On Fri, Nov 07, 2008 at 05:57:33PM +0300, Dmitry wrote: > > 2008/11/7 Pavel Machek : > > > On Fri 2008-11-07 21:23:41, Eric Miao wrote: > > >> Well, IIRC spitz still needs the patch to change the vmlinux.ld.S. > > >> Did you guys ever try that? > > > > > > I never heard about that patch, do you have it handy? > > > > http://rpsys.net/openzaurus/patches/archive/pxa-linking-bug.patch > > > > I plan to submit a bit modified version of this patch later. > > That doesn't look like something that should be accepted. Take a moment > to put some thought into the question. Why should we _allocate_ and > contain the stack in the resulting image? Does the stack contain any > data that must be pre-initialized? > > Obviously not. Firstly, I don't think that patch should ever make it into a mainline kernel. I can perhaps give some clues why its required though. I think the bootloader on the zaurus truncates the image when writing the kernel into flash using the standard flashing process. By having that much extra padding on the end of the kernel, nothing important is lost. How did the original 2.4 kernels ever work? Binutils used to be buggy and left this padding in. Nobody therefore ever noticed the bug in the bootloader. The above theory is guesswork based on the kernels I've seen work and not work and I wrote the patch mentioned above as a workaround a long time ago and more pressing issues meant I never got back to it. I'd love to see someone work out the problem for sure! Cheers, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/