Control: title -1 way to set kernel command line parameters in u-boot On 2015-05-26, Rick Thomas wrote: > If I wish to boot into, e.g. single user mode on my arm device, I find that > there is no way to set the kernel command parameter "single" other than > by mucking with bootargs_console in ways its creator did not intend.
It should be fine to edit bootcmd or bootargs_console or whatever for on the fly changes. > The problem is more general, of course, than just booting into single-user > mode. For example, there is currently no clean way to set _any_ kernel > parameter > either permanently or for a one-shot test. > > It would be useful to have a u-boot environment parameter that will > optionally be > passed to the kernel at boot. > > Possibly, change the (sheeva plug -- wheezy) > bootcmd=setenv bootargs $(bootargs_console); run bootcmd_mmc; bootm > 0x00800000 0x01100000 > to > bootcmd=setenv bootargs $(bootargs_console) $(cmdline); run bootcmd_mmc; > bootm 0x00800000 0x01100000 > and put my kernel command line args in "cmdline" I don't really see how this could be implemented in u-boot-tools... We could patch each and every board to respect additional u-boot environment variables, but that doesn't really seem like a maintainable approach... It seems like the easier thing to do is to use flash-kernel and /etc/default/flash-kernel or even a customized boot script. With boards that support config_distro_bootcmd, you can create an "extlinux.conf" file with menu options to select between, though it doesn't allow configuration of anything at boot time. live well, vagrant
signature.asc
Description: PGP signature
