Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754395AbYKHX3d (ORCPT ); Sat, 8 Nov 2008 18:29:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752733AbYKHX3Z (ORCPT ); Sat, 8 Nov 2008 18:29:25 -0500 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:51043 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752344AbYKHX3Y (ORCPT ); Sat, 8 Nov 2008 18:29:24 -0500 Date: Sat, 8 Nov 2008 23:28:57 +0000 From: Russell King To: Dmitry Cc: Richard Purdie , Pavel Machek , Eric Miao , Cyril Hrubis , lenz@cs.wisc.edu, kernel list , Dirk@opfer-online.de, arminlitzel@web.de, thommycheck@gmail.com Subject: Re: 2.6.28-rc3-git1: spitz still won't boot Message-ID: <20081108232857.GE14351@flint.arm.linux.org.uk> References: <20081106080416.GA1531@ucw.cz> <20081106191424.GA2273@atrey.karlin.mff.cuni.cz> <20081107142923.GA1616@ucw.cz> <20081107182311.GA28600@flint.arm.linux.org.uk> <1226155540.5379.5.camel@dax.rpnet.com> <20081108232111.GD14351@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2005 Lines: 41 On Sun, Nov 09, 2008 at 02:25:35AM +0300, Dmitry wrote: > 2008/11/9 Russell King : > > On Sun, Nov 09, 2008 at 02:12:47AM +0300, Dmitry wrote: > >> 2008/11/8 Richard Purdie : > >> > 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. > > ... > >> > >> I did rewrote your patch in a bit cleaner way (to apply the hack to > >> vmlinux.lds.in > >> in a cleaner way and only on PXA_SHARPSL), however I'm not submitting it > >> till I find what's the real reason for this problem. > > > > Even if the reason is found, I don't think it's something that should > > concern the kernel, especially as there is a script which writes the > > kernel image into the flash. If it's a case that the boot loader needs > > an extra 4K tacked on the end of the kernel image, that should be easy > > enough for this 'updater.sh' shell script to do. > > Actually on my tosa builds it's like 40k of zeroes (.bss is before .stack > and so is also present in the zImage). It seems that just 4k of padding > isn't enough (I tried that). That doesn't change my view - it's something that the kernel shouldn't be caring about. And as I point out, this script can add the padding itself which seems to be the right place to resolve the problem. (and I've finally dropped that bad email address from the CC line.) -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- 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/