[U-Boot-Users] bootargs

[asnua at eircom.net]

George,Wolfgang,
Well done. I modified my configuration file to enable CONFIG_CMDLINE_TAG and I can now pass command line arguments to the kernel. Yipee!!
I also checked the location of the BOOT_PARAMS phys addr and they were the same at 0x30000100.

I've also noticed that the error I was reporting earlier
in the week : 
"Warning: bad configuration page, trying to continue"
has DISAPPEARED. 
All this excitement in one day!!

One thing (there's always one more) ... does U-boot support writing to Intel Strata Flash?

Thanks again,
Dave



"George G. Davis" <davis_g at comcast.net> wrote:

<  
<  On Wed, Mar 10, 2004 at 06:33:09PM +0000, asnua at eircom.net wrote

"George G. Davis" <davis_g at comcast.net> wrote:

<  
<  On Wed, Mar 10, 2004 at 06:33:09PM +0000, asnua at eircom.net wrote:
<  > Hi
<  > Does CONFIG_BOOTARGS and or CONFIG_CMDLINE_TAG have to be set before the env variable 'bootargs' gets passed to the kernel? 
<  > 
<  
<  You must enable (define) CONFIG_CMDLINE_TAG. OTOH, defining CONFIG_BOOTARGS
<  is optional. If you do define CONFIG_BOOTARGS, it sets the default env
<  bootargs if same is not present in saved flash env already. Else if you
<  undef CONFIG_BOOTARGS, then you can always do `setenv bootargs ...` to
<  set it and `saveenv` to save it.
<  
<  HTH!
<  
<  --
<  Regards,
<  George
<  P.S. Make sure you've specified the correct BOOT_PARAMS phys addr for your
<  machine, i.e. make sure your machine boot_params agree between u-boot and
<  linux:
<  
<  	grep -i boot_params ../u-boot/board/*/*.c ../linux/arch/arm/mach-*/*.c
<  
<