From: Matt A. <ma...@ei...> - 2007-07-31 17:41:22
|
Hi All, Is there anyone out there that knows how to configure the bootargs variable through the menuconfig system when generating the file system? From the Linux menuconfig there is a "Boot Options" submenu that contains a configuration item called "Default kernel command string" that seems to be tied to the configuration variable CONFIG_CMDLINE. The default for this is CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2. Which seems to be the same value that the bootargs variable has when the Gumstx is first flashed. However I've noticed that even if I change this value and rebuild, the bootargs variable still has the default after flashing. So, I'm wondering if this is the right place to make this change? Can anyone suggest another means to influence the initial value of the bootargs variable? Thanks, Matt -- View this message in context: http://www.nabble.com/Configuring-bootargs-from-menuconfig-tf4194382.html#a11928456 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Craig H. <cr...@gu...> - 2007-07-31 17:47:39
|
On Jul 31, 2007, at 10:41 AM, Matt Aprea wrote: > Is there anyone out there that knows how to configure the bootargs > variable > through the menuconfig system when generating the file system? From > the > Linux menuconfig there is a "Boot Options" submenu that contains a > configuration item called "Default kernel command string" that > seems to be > tied to the configuration variable CONFIG_CMDLINE. The default for > this is > CONFIG_CMDLINE="console=ttyS0,115200n8 root=1f01 rootfstype=jffs2. > Which > seems to be the same value that the bootargs variable has when the > Gumstx is > first flashed. However I've noticed that even if I change this > value and > rebuild, the bootargs variable still has the default after > flashing. So, I'm > wondering if this is the right place to make this change? Can > anyone suggest > another means to influence the initial value of the bootargs variable? That option in linux affects how the kernel boots if no arg is passed on the kernel command line -- u-boot will always pass one though if its bootargs variable is set. To change this arg at compile-time, you'll need to do it in u-boot, not in the kernel. To do that, you'll need to edit the file buildroot/build_arm_nofpu/u-boot-*/include/configs/gumstix.h Look for the line #define CONFIG_BOOTARGS ... and change that definition, then re-build u-boot. You can change it in the file target/arm/u-boot/verdex/base.patch or target/arm/u-boot/basix-connex/base.patch instead and then rm -rf build_arm_nofpu/u-boot* then rebuild if you want it to be done automatically. C |
From: Matt A. <ma...@ei...> - 2007-08-02 16:02:43
|
Hi Craig, Thanks for the response. I've tried both of these approaches, but neither of them seems to work. You can see from the results of a grep on the string "console=3DttyS0,115200n8 root=3D1f01" below, that my changes have been propagated to several files. However when I reflash the gumstix with the new image, I still get the old bootargs "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 = reboot=3Dcold,hard" rather than the new "console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active". Any other suggestions? -Matt build_arm_nofpu/staging_dir/include/linux/autoconf.h:#define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/staging_dir/arm-linux-uclibcgnueabi/sys-include/linux/au toconf.h:#define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard = video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/staging_dir/arm-linux/sys-include/linux/autoconf.h:#defi ne CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/linux-2.6.20gum/include/linux/autoconf.h:#define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/linux-2.6.20gum/include/config/auto.conf:CONFIG_CMDLINE=3D= "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 = reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/linux-2.6.20gum/.config:CONFIG_CMDLINE=3D"console=3DttyS0= ,11 5200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/u-boot-1.1.4/include/configs/gumstix.h:#define CONFIG_BOOTARGS "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard = video=3Dpxafb:mode:416x622-16,active" build_arm_nofpu/u-boot-1.1.4/.pc/compact-flash.patch/include/configs/gum stix.h:#define CONFIG_BOOTARGS "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode: 416x622-16,active" target/arm/u-boot/.svn/text-base/base.patch.svn-base:+#define CONFIG_BOOTARGS "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard = video=3Dpxafb:mode:416x622-16,active" target/arm/u-boot/base.patch:+#define CONFIG_BOOTARGS "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 = reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" target/device/Gumstix/basix-connex/.svn/text-base/linux.config.svn-base: CONFIG_CMDLINE=3D"console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" target/device/Gumstix/basix-connex/.svn/text-base/orig_linux.config.svn- base:CONFIG_CMDLINE=3D"console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2" target/device/Gumstix/basix-connex/linux.config:CONFIG_CMDLINE=3D"console= =3D ttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" target/device/Gumstix/basix-connex/linux.config.orig:CONFIG_CMDLINE=3D"co= n sole=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2" toolchain_build_arm_nofpu/linux/include/linux/autoconf.h:#define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" toolchain_build_arm_nofpu/linux/include/config/auto.conf:CONFIG_CMDLINE=3D= "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 = reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" toolchain_build_arm_nofpu/linux/.config:CONFIG_CMDLINE=3D"console=3DttyS0= ,11 5200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" toolchain_build_arm_nofpu/uClibc/include/linux/autoconf.h:#define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" toolchain_build_arm_nofpu/uClibc_dev/usr/include/linux/autoconf.h:#defin e CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2 reboot=3Dcold,hard video=3Dpxafb:mode:416x622-16,active" toolchain_build_arm_nofpu/uClibc_dev/usr/include/linux/autoconf.h_orig:# define CONFIG_CMDLINE "console=3DttyS0,115200n8 root=3D1f01 rootfstype=3Djffs2" >=20 > > Is there anyone out there that knows how to configure the bootargs=20 > > variable through the menuconfig system when generating the file=20 > > system? From the Linux menuconfig there is a "Boot Options" submenu=20 > > that contains a configuration item called "Default kernel command=20 > > string" that seems to be tied to the configuration variable=20 > > CONFIG_CMDLINE. The default for this is > > CONFIG_CMDLINE=3D"console=3DttyS0,115200n8 root=3D1f01 = rootfstype=3Djffs2. =20 > > Which > > seems to be the same value that the bootargs variable has when the=20 > > Gumstx is first flashed. However I've noticed that even if I change=20 > > this value and rebuild, the bootargs variable still has the default=20 > > after flashing. So, I'm wondering if this is the right=20 > place to make=20 > > this change? Can anyone suggest another means to influence=20 > the initial=20 > > value of the bootargs variable? >=20 > That option in linux affects how the kernel boots if no arg=20 > is passed on the kernel command line -- u-boot will always=20 > pass one though if its bootargs variable is set. To change=20 > this arg at compile-time, you'll need to do it in u-boot, not=20 > in the kernel. To do that, you'll need to edit the file >=20 > buildroot/build_arm_nofpu/u-boot-*/include/configs/gumstix.h >=20 > Look for the line >=20 > #define CONFIG_BOOTARGS ... >=20 > and change that definition, then re-build u-boot. You can=20 > change it in the file >=20 > target/arm/u-boot/verdex/base.patch > or > target/arm/u-boot/basix-connex/base.patch >=20 > instead and then rm -rf build_arm_nofpu/u-boot* then rebuild=20 > if you want it to be done automatically. |
From: Craig H. <cr...@gu...> - 2007-08-02 17:21:18
|
On Aug 2, 2007, at 9:02 AM, Matt Aprea wrote: > However when I reflash the > gumstix with the new image, Did you install the new u-boot? That part is kind of import when the change is in u-boot. C |