Makefile.boot cleanup
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 5 patches 0 repliesNew
1 of 5 patches is in this archive. The cover letter announces 5.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 4/5 | Auto calculate ZRELADDR and provide option for exceptions | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Makefile.boot cleanup
Quoted 15 lines · Nicolas Pitre
Quoted 13 lines · Uwe Kleine-K?nig
Hello Eric,
Quoted 10 lines · Eric Miao
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_MX1orARCH_SHARKis defined
- whenARCH_U300is defined (U300 really is strange when definingPHYS_OFFSETand ZRELADDR)
- or whenZBOOT_ROMis defined
Quoted 7 lines
Quoted 2 lines
If you guess ZRELADDR based on sp instead of pc it even should work if
ZBOOT_ROMis defined?!If you're using
ZBOOT_ROMthat 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
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |