On 02/03/09 12:31 +0100, ext Juha Yrjola wrote: > On Mon, Mar 02, 2009 at 10:27:50AM +0200, Lauri Leukkunen wrote: > > > > STI console is enabled based on runtime decisions by the bootloader. The > > > kernel command line is unusable for us, because there is no way to append to > > > the line. We don't want to remove the possibility how having the user > > > create a custom kernel with a custom command line. > > > > *I* don't have a problem with having the bootloader always define the > > cmdline, you are the one against it :) > > If we did that, how would the kernel flashing process go? flasher needs to support updating the cmdline stored in the CAL, maybe with: flasher -b"cmdline" -f Then you just ignore whatever the kernel builtin cmdline is. So no need to change how the kernel is flashed. If a person is anyway modifying the cmdline, he might as well do it using the above mentioned command instead of hardcoding it into the kernel. This way he can experiment with different cmdlines without having to recompile and reflash the kernel. Maybe a -b"default" -f could be used to put back the default (perhaps also found from the CAL area?). This would require for the default cmdline to be written to CAL at manufacturing time, or be carried by the bootloader binary itself. Either way would be ok to me. /lauri -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
