From: David F. <dav...@ya...> - 2005-03-18 18:28:45
|
> Doesn't u-boot pass in stuff using tags? You > should be able to add an > additional tag. I haven't looked at the > gumstix, but on our board > (which uses a super-simple bootloader) uses the > block of memory at > 0xC000000 to pass tag information. On the arm, > the kernel loads at > 0xC0008000 and 0xC0004000 is used for the > top-level MMU table. > > I think that 0xC000000 becomes the zero page > eventually. > > Looking at arch/arm/mach-pxa/gumstix.c it would > appear that the boot > params are at 0xA0000100 (physical address > because the 0xC0000000 > stuff hasn't been setup yet). I'll have to look at that, do you mean the u-boot environment space or the kernel parameters? > So you could probably do something really > hokey, like store a flag at It may work locally, but I don't expect anyone would like this. > 0xA0003FFC, which wouldn't involve messing with > tags, or you could > have u-boot pass in an additional tag with the > silent information, and I guess ideally it should be one bit to test, otherwise parsing the u-boot environment for "silent". David. |