From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Uncompressing broken with commit e7db7b4270
Date: Fri, 19 Feb 2010 15:21:35 +0100 [thread overview]
Message-ID: <20100219142135.GB6959@pengutronix.de> (raw)
In-Reply-To: <20100203094107.GC11354@pengutronix.de>
Hello,
On Wed, Feb 03, 2010 at 10:41:07AM +0100, Uwe Kleine-K?nig wrote:
> Hello Catalin,
>
> On Tue, Feb 02, 2010 at 10:19:36AM +0000, Catalin Marinas wrote:
> > On Tue, 2010-02-02 at 09:55 +0000, Uwe Kleine-K?nig wrote:
> > > On Tue, Feb 02, 2010 at 09:07:47AM +0000, Colin Tuckley wrote:
> > > > > -----Original Message-----
> > > > > From: Uwe Kleine-K?nig [mailto:u.kleine-koenig at pengutronix.de]
> > > >
> > > > > What do you mean saying "kernel image"? zImage, Image, vmlinux,
> > > > > arch/arm/boot/compressed/vmlinux?
> > > >
> > > > It's actually a uImage (compressed image with u-boot 64 byte header).
> > > >
> > > > > So where do you place your zImage, what is zreladdr, how big is your
> > > > > RAM?
> > > >
> > > > It gets loaded by u-boot TFTP into RAM at the physical address of
> > > > memory at 0x70000000 and we have either 512MB or 1GB of RAM
> > > > depending on which system it is.
> > > >
> > > > zreladdr is 0x70008000
> > > That should be fine.
> > >
> > > What is the output on your machine? If you see "done", can you try
> > > defining DEBUG in arch/arm/boot/compressed/head.S?
> >
> > I don't think we were seeing any "done". Just "Uncompressing Linux ...".
> >
> > I need to get back to a bigger kernel image and I'll then try to
> > increase the stack size in the compressed head.S.
> Can you try the patch below and report the output in the failing case?
>
> I tried to get STAND_ALONE_DEBUG running, but the code suffered bit rot
> and is far away from working.
>
> And I think it makes sense to make sure it's not a toolchain problem.
> So can you send me a config and I give you back an uImage compiled with
> my toolchain? And maybe the other way round, too?
ping.
If we choose to revert e7db7b4270 we should do so before 2.6.33.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-02-19 14:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 17:03 Uncompressing broken with commit e7db7b4270 Catalin Marinas
2010-01-29 14:46 ` Uwe Kleine-König
2010-01-29 15:04 ` Albin Tonnerre
2010-01-29 15:14 ` Uwe Kleine-König
2010-01-29 15:29 ` Albin Tonnerre
2010-01-29 15:16 ` Russell King - ARM Linux
2010-01-29 16:12 ` Colin Tuckley
2010-01-29 21:13 ` Uwe Kleine-König
2010-02-02 9:01 ` Uwe Kleine-König
2010-02-02 9:07 ` Colin Tuckley
2010-02-02 9:55 ` Uwe Kleine-König
2010-02-02 10:19 ` Catalin Marinas
2010-02-03 9:41 ` Uwe Kleine-König
2010-02-19 14:21 ` Uwe Kleine-König [this message]
2010-02-19 15:27 ` Catalin Marinas
2010-02-01 22:56 ` Albin Tonnerre
2010-02-02 8:44 ` Uwe Kleine-König
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=20100219142135.GB6959@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).