[U-Boot-Users] bootargs env variable and CONFIG_CMDLINE in .config
Can someone please enlighten me on the relationship between u-boot's env variable "bootargs" which gets passed to the linux kernel, and the CONFIG_CMDLINE kernel configuration setting in .config? Which one takes precedence if CONFIG_CMDLINE_BOOL is set and CONFIG_CMDLINE has a string in it?
I'm running an ebony system with u-boot, booting a MontaVista 3.0 kernel. I have modified MV's version of ebony.c to copy the bootargs env info to "cmd_line", and this info is displayed when the kernel boots up, but I don't think the kernel is really using this.
If I'm using bootargs from u-boot, do I have to disable CONFIG_CMDLINE_BOOL in the kernel .config?
Thanks.
Erik
In message BA0E4392AD99D040885C414D992C24BE036150BE@us-bv-m11 you wrote:
Can someone please enlighten me on the relationship between u-boot's env variable "bootargs" which gets passed to the linux kernel, and the CONFIG_CMDLINE kernel configuration setting in .config? Which one takes precedence if CONFIG_CMDLINE_BOOL is set and CONFIG_CMDLINE has a string in it?
When using U-Boot, the Linux bootloader stuff is not used at all, so all related kernel config options (including CONFIG_CMDLINE) will be unused / ignored.
I'm running an ebony system with u-boot, booting a MontaVista 3.0 kernel. I have modified MV's version of ebony.c to copy the bootargs
You probably have to ask MV. I don't knwo what they do in their version of the kernel tree. Normally, all the bootstrap loader stuff is not required when using U-Boot.
It was one of the major design goals to get rid of stuff like compiled-in command lines when I started the PPCBoot project.
Best regards,
Wolfgang Denk
participants (2)
-
erik.teose＠exgate.tek.com -
Wolfgang Denk