[PATCH 4/5] [ARM] Auto calculate ZRELADDR and provide option for exceptions

[Eric Miao]

2010/6/10 Uwe Kleine-König <u.kleine-koenig at pengutronix.de>:
> Hello Eric,
>
>> > What do you think about requiring r4 to be set to physoffset as I did in
>> > my series?
>>
>> My only concern is to impose less restrictions on the boot loaders.
> While it remains optional without runtime physoffset it's OK if you ask
> me.
>
>> And zImage is only one of the possible headers we may have:
>>
>>  * vmlinux can actually directly booted into as long as it's placed at the
>>    right place
>>  * uImage, with zImage or vmlinux (raw or compressed) encapsulated
>>  * zImage
>>  * xipImage
>>  * bootpImage
> bootpimage is still used?  In a different thread I suggested to remove
> it.
> The others are just a wrapped vmlinux that needs to be aware anyhow.
> And the wrappers only need to pass r4 additionally to r2 and r3 through.
>
>> I'd really like to separate the guess work into two parts so they don't
>> have dependencies.
> But zreladdr is always physoffset + textoffset, isn't it?

I'm not completely sure about the u300 case.

> So you should
> use the same guess for both physoffset and zreladdr, no?

My understanding is that separating guess of phys_offset and zreladdr might
be a smoother migration path at this moment and yes it's a trade off.


> And if you do it properly, it should even be possible to reuse the same
> code for all locations.
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K.                           | Uwe Kleine-König            |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
>