On 30/09/14 12:45, Dr. H. Nikolaus Schaller wrote:
Well, where does the DT blob come from? It must be device specific. You can either get the bootargs from the same place where the DT blob is, or you can use "bootargs" property in the DT blob itself to define device specific bootargs.
Yes, that is how it could work. But why have it duplicated at all? I.e. loading two device specific files into the kernel where one would suffice.
Well, add the bootargs to the board's .dts file, and so to the DT blob itself. Then there's just one device specific file to load.
If that's for some reason not possible, then you should read two device specific files, or manage the device specific bootargs in some other way.
That is the reason why I think we should reduce the boot args to a minimum (that ideally is completely device independent).
No, it _must_ be device independent =). Relying on the kernel to ignore bad bootargs which are actually meant for some other device is buggy.
You can say that it's inconvenient, but there's no way around it. Bootargs are device specific (except the obvious common ones), and any other use is just wrong.
Tomi