LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Dmitry <dbaryshkov@gmail.com>, 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, 08 Nov 2008 14:45:40 +0000 [thread overview]
Message-ID: <1226155540.5379.5.camel@dax.rpnet.com> (raw)
In-Reply-To: <20081107182311.GA28600@flint.arm.linux.org.uk>
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 <pavel@suse.cz>:
> > > 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
next prev parent reply other threads:[~2008-11-08 14:46 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 [this message]
2008-11-08 23:12 ` Dmitry
2008-11-08 23:21 ` Russell King
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=1226155540.5379.5.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--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=rmk+lkml@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).