On Mon, 2016-01-25 at 13:55 -0700, Stephen Warren wrote: > On 01/25/2016 01:39 PM, Lubomir Rintel wrote: > > U-Boot falls back to "bcm2835-rpi-other.dtb" for boards of unknown > > identification. Let's do a bare minimum for them so that they at leat > > boot. > > > > Signed-off-by: Lubomir Rintel <lkundrak@xxxxx> > > --- > > arch/arm/boot/dts/Makefile | 1 + > > arch/arm/boot/dts/bcm2835-rpi-other.dts | 7 +++++++ > > This DT shouldn't ever be used, except when a new unidentified board > appears. In that case, I believe the correct solution is to add support > for that new board to U-Boot and the kernel, rather than add fall-backs. > Prior to that being done, a user can always copy whichever DT they want > into filename bcm2835-rpi-other.dts for temporary testing/development, > if they have reason to believe their new model is compatible with > something else. In general, I don't think we have any reason to believe > that even this new minimal DT is guaranteed to be compatible with any > possible future hardware, so it seems a little risky to ship this file > in anticipation. Fair enough. It just frustrates me a bit that the chance of mainline working on a new or even older RPi board is not as good as I'd like to. I guess I could perhaps get a bit better at quickly submitting the device tree instead of cheap hacks then. By the way, I've seen you add an entry for the Zero board to U-Boot and was thinking that you perhaps had a device tree for it? Do you plan to include that one into mainline Linux, or do you keep your dts elsewhere? Should I go ahead and submit one? Also, the Model B entries in U-Boot version table seems incorrect to me (sent a separate message to U-Boot list, but it got caught in moderation now). I'm wondering what's the authoritative source for the version information? Did you get the version numbers from the actual hardware or is some documentation available? Thanks, Lubo -- 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
