On Thursday, June 2, 2016 5:11:31 PM CEST Gerd Hoffmann wrote: > > > > > > Reference to ../../../arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts > > > > > directly in the Makefile? > > Actually tried that, and to my surprise this worked fine for both "make > dtbs" and "make dtbs_install". > > So we should just do that I guess ... Right. > > > Yes, in theory. No, in practice. As far I know the rpi3 is the only > > > 64bit soc where a almost identical 32bit version exists, so running > > > 32bit kernels on a 64bit processor actually happens in practice and I > > > expect this to continue. If you want create sdcard images which run on > > > any rpi variant this is pretty much the only reasonable way to do it. > > > > I think the Allwinner A64 and the Samsung s5p6818 are other examples > > for this, where the initial run of boards all run 32-bit kernels > > for much of the same reasons. If users want to run a 32-bit distro > > on rpi-3 and on e.g. orange-pi, I don't see why they wouldn't also run > > the same binary on A64. > > ... and others can join the party on a case-by-case basis. > > I still expect for the majority of arm64 boards it is not very useful, > so I don't think we should build all of them unconditionally. Well, they are still controlled by Kconfig symbols. Some of them are shared between arm and arm64 and you would just get all dtbs in that case, while other symbols are specific to one of the two. Just for fun, which machines do we actually get if we decide to just enter the arch/arm64/boot/dts/ directory in an allmodconfig build? Arnd -- 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
