On Tuesday 28 April 2009 09:45:38 Wolfgang Denk wrote:
Dear Mike Frysinger,
In message 200904280854.53669.vapier@gentoo.org you wrote:
You mean in the code? Well, if you're using a separate section for it (like the ppcenv section) this should be straightforward using the `=FILLEXP' output section attribute for the linker.
hmm, a quick grep shows that almost no one has a dedicated section. the
Everybody who uses CONFIG_SYS_USE_PPCENV or CONFIG_NAND_U_BOOT has:
-> find * -name 'u-boot*.lds' | xargs fgrep -l .ppcenv | wc -l 50
not really ... look at the linker scripts and you'll see most do: .text { ... common/env_embedded.o (.ppcenv) ...
that's why i didnt use the CONFIG_SYS_USE_PPCENV to figure out how many people had a dedicated section
majority of people (Blackfin boards included) insert it into the middle of their .text section. this is the use case i was thinking of when i said "no way" because i hadnt seen anyone using a dedicated section before.
But that would be easy to change - see how it's done on ppc.
can you name a board ? the ones i saw placed the env sector after things, they didnt split the .text section. otherwise we'd have to do like: .text.pre.env { ... custom filler ... } .ppcenv { common/env_embedded.o (.ppcenv) } .text { ... glob remaining .text } -mike