On Mon, Nov 13, 2017 at 9:05 PM, Daniel Gimpelevich <daniel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 2017-11-13 at 10:34 -0600, Rob Herring wrote: >> This is a kernel problem. What's the use case where you want the DT to >> override the kernel? >> >> One way you could handle this is make bootargs be multiple strings. >> Well 2 specifically, the first string is prepended and the 2nd is >> appended. That complicates how you'd implement /append-property/ >> though as you'd probably want to support both string cat and 2 >> strings. Though the latter works more generically without knowing the >> data type. > > Let's say the bootloader tells the kernel that the command line is "foo > bar" and that "baz" is in the dtb. Currently, there are kernel > configuration options to control whether this means the kernel's command > line will be "baz" or "baz foo bar" instead, but there is no way to turn > it into "foo bar baz" without either creating new kernel configuration > options or this patch. Implementing it via this patch would allow a > theoretical distro to use a generic kernel across different devices that > need the arguments from their bootloader manipulated in different ways. I understand you can't apply random strings in any order you like. I'm questioning the need to do that and what are the concrete example(s) where you need that ability. I'd generally expect that only board specific options are in the dtb, and a distro will add it's own options common for all and the specific arch into the bootloader config files. And generally, the last thing loaded gets the last say in what is set. > Ideally, the MIPS-specific kernel configuration options for how to treat > the dtb's bootargs with respect to the bootloader's bootargs should go > away in favor of an analogous device tree property "bootargs-prepend" > for this reason. The kernel configuration options to supply a hard-coded > default command line if the bootloader does not supply one, and to > override what the bootloader and dtb supply, would remain. This would > separate the need for an alternate or "recovery" kernel to supply its > own bootargs to override the dtb from the need to have device-specific > bootargs in the dtb override a legacy bootloader, where the manner its > bootargs are overridden may be device-specific. What h/w specific options would be needed for recovery kernel? That's getting into putting not just Linux specifics into the dtb, but distro specifics there. While yes, the dts files often already have bootargs filled with Linux options, the intention is really that the bootloader fills in bootargs. And if you have multiple kernels or OSs, then the bootloader provides the mechanism to choose and boot with the right options. I think the kernel (being last) should fully decide what to do: append, prepend, and/or override. There was some work a while back to support more flexible command line handling and be arch neutral, but it never got merged. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
