From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dmitry <dbaryshkov@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@suse.cz>,
Eric Miao <eric.y.miao@gmail.com>, Cyril Hrubis <metan@ucw.cz>,
lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, arminlitzel@web.de, pavel.urban@ct.cz,
thommycheck@gmail.com
Subject: Re: 2.6.28-rc3-git1: spitz still won't boot
Date: Sat, 8 Nov 2008 23:21:11 +0000 [thread overview]
Message-ID: <20081108232111.GD14351@flint.arm.linux.org.uk> (raw)
In-Reply-To: <bc64b4640811081512ta8bfd90m921760839bdf8ffa@mail.gmail.com>
On Sun, Nov 09, 2008 at 02:12:47AM +0300, Dmitry wrote:
> 2008/11/8 Richard Purdie <rpurdie@rpsys.net>:
> > 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.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-11-08 23:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 15:06 2.6.28-rc2-git1: spitz still won't boot Pavel Machek
2008-10-31 21:55 ` Rafael J. Wysocki
2008-11-03 10:40 ` Pavel Machek
2008-11-03 11:04 ` Russell King
2008-11-03 11:12 ` Pavel Machek
2008-11-05 14:23 ` 2.6.28-rc3-git1: " Pavel Machek
2008-11-05 15:13 ` Dmitry
2008-11-05 17:33 ` Pavel Machek
2008-11-05 23:00 ` Dmitry
2008-11-06 8:04 ` Pavel Machek
2008-11-06 19:14 ` Cyril Hrubis
2008-11-07 13:23 ` Eric Miao
2008-11-07 14:29 ` Pavel Machek
2008-11-07 14:57 ` Dmitry
2008-11-07 18:23 ` Russell King
2008-11-08 14:45 ` Richard Purdie
2008-11-08 23:12 ` Dmitry
2008-11-08 23:21 ` Russell King [this message]
2008-11-08 23:25 ` Dmitry
2008-11-08 23:28 ` Russell King
2008-11-09 11:45 ` Pavel Machek
2008-11-09 11:46 ` Pavel Machek
2008-11-09 12:30 ` Dmitry
2008-11-09 14:12 ` Pavel Machek
2008-11-09 14:52 ` Dmitry
2008-11-10 7:50 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081108232111.GD14351@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Dirk@opfer-online.de \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=pavel.urban@ct.cz \
--cc=pavel@suse.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.