NACK, If you want to test something with the alternative device trees then you can modify a single line while doing so.
Apart from that there are other alternative device trees for the other models, so why only adding the pi-zero one? I guess because that's the one you're using for testing... BTW, there's another way of using those alternative device trees without adding them to config.txt: using --283x when generating the kernel image: https://github.com/raspberrypi/linux/blob/rpi-4.9.y/scripts/mkknlimg#L47 El 31/03/2017 a las 22:42, Rafał Miłecki escribió: > From: Rafał Miłecki <ra...@milecki.pl> > > This allows easier testing/developing/debugging of upstream DTS file. > Foundation's start.elf doesn't use it on its own so this won't cause any > regressions. Testing this DTB requires using U-Boot or adding > device_tree entry to the config.txt. > > Signed-off-by: Rafał Miłecki <ra...@milecki.pl> > --- > target/linux/brcm2708/image/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/target/linux/brcm2708/image/Makefile > b/target/linux/brcm2708/image/Makefile > index 7909c6d814..9c048f5e33 100644 > --- a/target/linux/brcm2708/image/Makefile > +++ b/target/linux/brcm2708/image/Makefile > @@ -56,7 +56,7 @@ endef > > define Device/rpi > DEVICE_TITLE := Raspberry Pi B/B+/CM/Zero/ZeroW > - DEVICE_DTS := bcm2708-rpi-b bcm2708-rpi-b-plus bcm2708-rpi-cm > bcm2708-rpi-0-w > + DEVICE_DTS := bcm2708-rpi-b bcm2708-rpi-b-plus bcm2708-rpi-cm > bcm2708-rpi-0-w bcm2835-rpi-zero > endef > ifeq ($(SUBTARGET),bcm2708) > TARGET_DEVICES += rpi > _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
