Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= <u.kleine-koenig <at> pengutronix.de>
Subject: Re: [PATCH 0/5] Makefile.boot cleanup
Newsgroups: gmane.linux.ports.arm.kernel
Date: Friday 11th June 2010 04:55:07 UTC (over 7 years ago)
On Thu, Jun 10, 2010 at 02:44:53PM -0400, Nicolas Pitre wrote:
> On Thu, 3 Jun 2010, Uwe Kleine-König wrote:
> 
> > Hello Eric,
> > 
> > On Thu, Jun 03, 2010 at 03:36:48PM +0800, Eric Miao wrote:
> > > Several facts:
> > > 
> > > 1. ZRELADDR in most cases can be auto detected by maksing PC with
> > >    0xf000_0000 if the zImage is placed within the first 256MiB from
> > >    the memory start, which is a sane assumption except for:
> > > 
> > >    - when ARCH_MX1 or ARCH_SHARK is defined
> > >    - when ARCH_U300 is defined (U300 really is strange when defining
> > >      PHYS_OFFSET and ZRELADDR)
> > >    - or when ZBOOT_ROM is defined
> > If you guess ZRELADDR based on sp instead of pc it even should work if
> > ZBOOT_ROM is defined?!
> 
> If you're using ZBOOT_ROM that means you want to execute zImage directly 
> from ROM.  This is therefore a highly customized configuration.  In that 
> context, having a variable phys-offset doesn't make much sense to start 
> with.
Right, but then the kernel needs to know this fixed value for
phys-offset.  In the patches presented by Eric the person configuring
the kernel needs to know that value.  When guessing based on sp she
doesn't need to read addional docs when enabling ZBOOT_ROM.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
 
CD: 4ms