| Message ID | 20190103110036.14604-1-flatmax@flatmax.org |
|---|---|
| State | Accepted |
| Headers | show |
| Series | [1/1] Fix rasberry Pi 64bit firmware overlay inclusion | expand |
Hello Max, On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: > This patch enables the inclusion of the Pi's overlays. Previously > the overlays were not included in the genimage configuration. > This patch ensures overlays are included in the sdcard (when > enabled) by defaulting to the inclusion of an empty > output/images/rpi-firmware/overlays directory in genimage cfg. > > The Pi's overlays are built with the following config > variables: > BR2_PACKAGE_RPI_FIRMWARE=y > BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y > BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y > BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y > BR2_LINUX_KERNEL_IMAGE_NAME="Image" > BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" > > After building, the dtbo files are present in the > output/images/rpi-firmware/overlays directory but not added > to the sdcard because they are missing from the genimage cfg > file. Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig use case (mind the buildroot minimalistic defconfig approach) in contrast to the raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... Adding a (maybe) empty overlays directory to the sdcard image would violate the minimalistic approach... Regards, Peter [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] > > Signed-off-by: Matt Flax <flatmax@flatmax.org> > --- > board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + > package/rpi-firmware/rpi-firmware.mk | 4 ++++ > 2 files changed, 5 insertions(+) > > diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg > index 0d0ca750a7..af1d17cde7 100644 > --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg > +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg > @@ -9,6 +9,7 @@ image boot.vfat { > "rpi-firmware/config.txt", > "rpi-firmware/fixup.dat", > "rpi-firmware/start.elf", > + "rpi-firmware/overlays", > "Image" > } > } > diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk > index bb54904ae6..0df7b17cbd 100644 > --- a/package/rpi-firmware/rpi-firmware.mk > +++ b/package/rpi-firmware/rpi-firmware.mk > @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ > done > endef > +else > +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; > +endef > endif > > ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y)
On 5/1/19 6:50 am, Peter Seiderer wrote: > Hello Max, > > On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: > >> This patch enables the inclusion of the Pi's overlays. Previously >> the overlays were not included in the genimage configuration. >> This patch ensures overlays are included in the sdcard (when >> enabled) by defaulting to the inclusion of an empty >> output/images/rpi-firmware/overlays directory in genimage cfg. >> >> The Pi's overlays are built with the following config >> variables: >> BR2_PACKAGE_RPI_FIRMWARE=y >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y >> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y >> BR2_LINUX_KERNEL_IMAGE_NAME="Image" >> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" >> >> After building, the dtbo files are present in the >> output/images/rpi-firmware/overlays directory but not added >> to the sdcard because they are missing from the genimage cfg >> file. > Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not > containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig > use case (mind the buildroot minimalistic defconfig approach) in contrast to the > raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... > > Adding a (maybe) empty overlays directory to the sdcard image would violate > the minimalistic approach... With or without this patch, I see no viable way to update the device tree. Is there a method ? What is a Raspberry Pi without a method to support the addons and hats ? Do you have a method for supporting any of the various addons/hats which would normally work with an overlay line added to /boot/config.txt ? Matt > Regards, > Peter > > [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] > >> Signed-off-by: Matt Flax <flatmax@flatmax.org> >> --- >> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + >> package/rpi-firmware/rpi-firmware.mk | 4 ++++ >> 2 files changed, 5 insertions(+) >> >> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg >> index 0d0ca750a7..af1d17cde7 100644 >> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg >> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg >> @@ -9,6 +9,7 @@ image boot.vfat { >> "rpi-firmware/config.txt", >> "rpi-firmware/fixup.dat", >> "rpi-firmware/start.elf", >> + "rpi-firmware/overlays", >> "Image" >> } >> } >> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk >> index bb54904ae6..0df7b17cbd 100644 >> --- a/package/rpi-firmware/rpi-firmware.mk >> +++ b/package/rpi-firmware/rpi-firmware.mk >> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ >> done >> endef >> +else >> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; >> +endef >> endif >> >> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
Hello Matt, On Sat, 5 Jan 2019 10:08:04 +1100, Matt Flax <flatmax@flatmax.org> wrote: > On 5/1/19 6:50 am, Peter Seiderer wrote: > > Hello Max, > > > > On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: > > > >> This patch enables the inclusion of the Pi's overlays. Previously > >> the overlays were not included in the genimage configuration. > >> This patch ensures overlays are included in the sdcard (when > >> enabled) by defaulting to the inclusion of an empty > >> output/images/rpi-firmware/overlays directory in genimage cfg. > >> > >> The Pi's overlays are built with the following config > >> variables: > >> BR2_PACKAGE_RPI_FIRMWARE=y > >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y > >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y > >> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y > >> BR2_LINUX_KERNEL_IMAGE_NAME="Image" > >> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" > >> > >> After building, the dtbo files are present in the > >> output/images/rpi-firmware/overlays directory but not added > >> to the sdcard because they are missing from the genimage cfg > >> file. > > Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not > > containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig > > use case (mind the buildroot minimalistic defconfig approach) in contrast to the > > raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... > > > > Adding a (maybe) empty overlays directory to the sdcard image would violate > > the minimalistic approach... > > > With or without this patch, I see no viable way to update the device > tree. Is there a method ? See e.g. configs/raspberrypi3_defconfig for a specialized case: BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" > > What is a Raspberry Pi without a method to support the addons and hats ? A minimalistic starting point for a minimal system, each add-on/hat would surely need additional packages/software, each customized system needs a customized configuration.... > > Do you have a method for supporting any of the various addons/hats which > would normally work with an overlay line added to /boot/config.txt ? > Or take a look at '[RFC] raspberrypi: post-image.sh arguments as config.txt properties ' [1] for a more general approach... Regards, Peter [1] https://patchwork.ozlabs.org/patch/1007728/ > Matt > > > > Regards, > > Peter > > > > [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] > > > >> Signed-off-by: Matt Flax <flatmax@flatmax.org> > >> --- > >> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + > >> package/rpi-firmware/rpi-firmware.mk | 4 ++++ > >> 2 files changed, 5 insertions(+) > >> > >> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg > >> index 0d0ca750a7..af1d17cde7 100644 > >> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg > >> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg > >> @@ -9,6 +9,7 @@ image boot.vfat { > >> "rpi-firmware/config.txt", > >> "rpi-firmware/fixup.dat", > >> "rpi-firmware/start.elf", > >> + "rpi-firmware/overlays", > >> "Image" > >> } > >> } > >> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk > >> index bb54904ae6..0df7b17cbd 100644 > >> --- a/package/rpi-firmware/rpi-firmware.mk > >> +++ b/package/rpi-firmware/rpi-firmware.mk > >> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > >> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ > >> done > >> endef > >> +else > >> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > >> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; > >> +endef > >> endif > >> > >> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) > > _______________________________________________ > > buildroot mailing list > > buildroot@busybox.net > > http://lists.busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
On 6/1/19 2:17 am, Peter Seiderer wrote: > Hello Matt, > > On Sat, 5 Jan 2019 10:08:04 +1100, Matt Flax <flatmax@flatmax.org> wrote: > >> On 5/1/19 6:50 am, Peter Seiderer wrote: >>> Hello Max, >>> >>> On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: >>> >>>> This patch enables the inclusion of the Pi's overlays. Previously >>>> the overlays were not included in the genimage configuration. >>>> This patch ensures overlays are included in the sdcard (when >>>> enabled) by defaulting to the inclusion of an empty >>>> output/images/rpi-firmware/overlays directory in genimage cfg. >>>> >>>> The Pi's overlays are built with the following config >>>> variables: >>>> BR2_PACKAGE_RPI_FIRMWARE=y >>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y >>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y >>>> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y >>>> BR2_LINUX_KERNEL_IMAGE_NAME="Image" >>>> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" >>>> >>>> After building, the dtbo files are present in the >>>> output/images/rpi-firmware/overlays directory but not added >>>> to the sdcard because they are missing from the genimage cfg >>>> file. >>> Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not >>> containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig >>> use case (mind the buildroot minimalistic defconfig approach) in contrast to the >>> raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... >>> >>> Adding a (maybe) empty overlays directory to the sdcard image would violate >>> the minimalistic approach... >> >> With or without this patch, I see no viable way to update the device >> tree. Is there a method ? > See e.g. configs/raspberrypi3_defconfig for a specialized case: > > BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" > >> What is a Raspberry Pi without a method to support the addons and hats ? > A minimalistic starting point for a minimal system, each add-on/hat > would surely need additional packages/software, each customized system > needs a customized configuration.... > >> Do you have a method for supporting any of the various addons/hats which >> would normally work with an overlay line added to /boot/config.txt ? >> > Or take a look at '[RFC] raspberrypi: post-image.sh arguments as config.txt properties ' [1] > for a more general approach... > > Regards, > Peter > > [1] https://patchwork.ozlabs.org/patch/1007728/ Thanks for the pointer. It is pretty clear that support for the RPi requires a lot more work and blocking revisions doesn't really help. Despite adding post_script_args, there simply isn't any way to include overlays in the current setup. For example : If I add the variable BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" It will put the following into boot/config.txt : dtoverlay=pi3-miniuart-bt But - now here is the clincher - THERE IS NO WAY TO GET OVERLAYS INTO THE BOOT PARTITION ! Can you please be more helpful ? I see specifically the following problems : 1] Can you suggest a better method to include overlays in the sdcard during a build process ? 2] For a 64 bit system, does overlay loading even work ? I tried to load an overlay by putting dtoverlay into config.txt but it seemed to not even be aware of its presence ! 3] Because of 2] is there a particular place to put overlays rather then boot/overlays ? thanks Matt >> Matt >> >> >>> Regards, >>> Peter >>> >>> [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] >>> >>>> Signed-off-by: Matt Flax <flatmax@flatmax.org> >>>> --- >>>> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + >>>> package/rpi-firmware/rpi-firmware.mk | 4 ++++ >>>> 2 files changed, 5 insertions(+) >>>> >>>> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>> index 0d0ca750a7..af1d17cde7 100644 >>>> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>> @@ -9,6 +9,7 @@ image boot.vfat { >>>> "rpi-firmware/config.txt", >>>> "rpi-firmware/fixup.dat", >>>> "rpi-firmware/start.elf", >>>> + "rpi-firmware/overlays", >>>> "Image" >>>> } >>>> } >>>> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk >>>> index bb54904ae6..0df7b17cbd 100644 >>>> --- a/package/rpi-firmware/rpi-firmware.mk >>>> +++ b/package/rpi-firmware/rpi-firmware.mk >>>> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >>>> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ >>>> done >>>> endef >>>> +else >>>> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >>>> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; >>>> +endef >>>> endif >>>> >>>> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) >>> _______________________________________________ >>> buildroot mailing list >>> buildroot@busybox.net >>> http://lists.busybox.net/mailman/listinfo/buildroot >> _______________________________________________ >> buildroot mailing list >> buildroot@busybox.net >> http://lists.busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
Hello Matt, On Sun, 6 Jan 2019 12:11:44 +1100, Matt Flax <flatmax@flatmax.org> wrote: > On 6/1/19 2:17 am, Peter Seiderer wrote: > > Hello Matt, > > > > On Sat, 5 Jan 2019 10:08:04 +1100, Matt Flax <flatmax@flatmax.org> wrote: > > > >> On 5/1/19 6:50 am, Peter Seiderer wrote: > >>> Hello Max, > >>> > >>> On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: > >>> > >>>> This patch enables the inclusion of the Pi's overlays. Previously > >>>> the overlays were not included in the genimage configuration. > >>>> This patch ensures overlays are included in the sdcard (when > >>>> enabled) by defaulting to the inclusion of an empty > >>>> output/images/rpi-firmware/overlays directory in genimage cfg. > >>>> > >>>> The Pi's overlays are built with the following config > >>>> variables: > >>>> BR2_PACKAGE_RPI_FIRMWARE=y > >>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y > >>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y > >>>> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y > >>>> BR2_LINUX_KERNEL_IMAGE_NAME="Image" > >>>> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" > >>>> > >>>> After building, the dtbo files are present in the > >>>> output/images/rpi-firmware/overlays directory but not added > >>>> to the sdcard because they are missing from the genimage cfg > >>>> file. > >>> Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not > >>> containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig > >>> use case (mind the buildroot minimalistic defconfig approach) in contrast to the > >>> raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... > >>> > >>> Adding a (maybe) empty overlays directory to the sdcard image would violate > >>> the minimalistic approach... > >> > >> With or without this patch, I see no viable way to update the device > >> tree. Is there a method ? > > See e.g. configs/raspberrypi3_defconfig for a specialized case: > > > > BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" > > > >> What is a Raspberry Pi without a method to support the addons and hats ? > > A minimalistic starting point for a minimal system, each add-on/hat > > would surely need additional packages/software, each customized system > > needs a customized configuration.... > > > >> Do you have a method for supporting any of the various addons/hats which > >> would normally work with an overlay line added to /boot/config.txt ? > >> > > Or take a look at '[RFC] raspberrypi: post-image.sh arguments as config.txt properties ' [1] > > for a more general approach... > > > > Regards, > > Peter > > > > [1] https://patchwork.ozlabs.org/patch/1007728/ > > > Thanks for the pointer. It is pretty clear that support for the RPi > requires a lot more work and blocking revisions doesn't really help. Don`t know what your mean by 'blocking revisions'? > Despite adding post_script_args, there simply isn't any way to include > overlays in the current setup. Your initial suggested patch shows the way to do it: - enable BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y - use a customized genimage config file with overlay directory enabled - use a customized genimage config file pointing to a customized config.txt file > > For example : > > If I add the variable > BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" > > It will put the following into boot/config.txt : > > dtoverlay=pi3-miniuart-bt > > But - now here is the clincher - THERE IS NO WAY TO GET OVERLAYS INTO > THE BOOT PARTITION ! > > Can you please be more helpful ? I see specifically the following problems : > > 1] Can you suggest a better method to include overlays in the sdcard > during a build process ? See above... > > 2] For a 64 bit system, does overlay loading even work ? I tried to load > an overlay by putting dtoverlay into config.txt but it seemed to not > even be aware of its presence ! Should work the same way as 32 bit, but did not test it recently...how do you determine 'not even be aware of its presence'? > > 3] Because of 2] is there a particular place to put overlays rather then > boot/overlays ? Not a buildroot specific question, more for a raspberry forum..., but according to [2] the right place for the overlays is the boot partition overlays directory... Regards, Peter [2] https://www.raspberrypi.org/documentation/configuration/device-tree.md > > > thanks > > Matt > > > > > >> Matt > >> > >> > >>> Regards, > >>> Peter > >>> > >>> [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] > >>> > >>>> Signed-off-by: Matt Flax <flatmax@flatmax.org> > >>>> --- > >>>> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + > >>>> package/rpi-firmware/rpi-firmware.mk | 4 ++++ > >>>> 2 files changed, 5 insertions(+) > >>>> > >>>> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg > >>>> index 0d0ca750a7..af1d17cde7 100644 > >>>> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg > >>>> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg > >>>> @@ -9,6 +9,7 @@ image boot.vfat { > >>>> "rpi-firmware/config.txt", > >>>> "rpi-firmware/fixup.dat", > >>>> "rpi-firmware/start.elf", > >>>> + "rpi-firmware/overlays", > >>>> "Image" > >>>> } > >>>> } > >>>> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk > >>>> index bb54904ae6..0df7b17cbd 100644 > >>>> --- a/package/rpi-firmware/rpi-firmware.mk > >>>> +++ b/package/rpi-firmware/rpi-firmware.mk > >>>> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > >>>> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ > >>>> done > >>>> endef > >>>> +else > >>>> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > >>>> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; > >>>> +endef > >>>> endif > >>>> > >>>> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) > >>> _______________________________________________ > >>> buildroot mailing list > >>> buildroot@busybox.net > >>> http://lists.busybox.net/mailman/listinfo/buildroot > >> _______________________________________________ > >> buildroot mailing list > >> buildroot@busybox.net > >> http://lists.busybox.net/mailman/listinfo/buildroot > > _______________________________________________ > > buildroot mailing list > > buildroot@busybox.net > > http://lists.busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
On 7/1/19 5:31 am, Peter Seiderer wrote: > Hello Matt, > > On Sun, 6 Jan 2019 12:11:44 +1100, Matt Flax <flatmax@flatmax.org> wrote: > >> On 6/1/19 2:17 am, Peter Seiderer wrote: >>> Hello Matt, >>> >>> On Sat, 5 Jan 2019 10:08:04 +1100, Matt Flax <flatmax@flatmax.org> wrote: >>> >>>> On 5/1/19 6:50 am, Peter Seiderer wrote: >>>>> Hello Max, >>>>> >>>>> On Thu, 3 Jan 2019 22:00:36 +1100, Matt Flax <flatmax@flatmax.org> wrote: >>>>> >>>>>> This patch enables the inclusion of the Pi's overlays. Previously >>>>>> the overlays were not included in the genimage configuration. >>>>>> This patch ensures overlays are included in the sdcard (when >>>>>> enabled) by defaulting to the inclusion of an empty >>>>>> output/images/rpi-firmware/overlays directory in genimage cfg. >>>>>> >>>>>> The Pi's overlays are built with the following config >>>>>> variables: >>>>>> BR2_PACKAGE_RPI_FIRMWARE=y >>>>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y >>>>>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y >>>>>> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y >>>>>> BR2_LINUX_KERNEL_IMAGE_NAME="Image" >>>>>> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" >>>>>> >>>>>> After building, the dtbo files are present in the >>>>>> output/images/rpi-firmware/overlays directory but not added >>>>>> to the sdcard because they are missing from the genimage cfg >>>>>> file. >>>>> Thanks for suggested patch, the reasoning for genimage-raspberrypi3-64.cfg not >>>>> containing a overlays entry is it is not needed for the raspberrypi3_64_defconfig >>>>> use case (mind the buildroot minimalistic defconfig approach) in contrast to the >>>>> raspberrypi3_defconfig where the overlay is needed for the pi3-miniuart-bt one... >>>>> >>>>> Adding a (maybe) empty overlays directory to the sdcard image would violate >>>>> the minimalistic approach... >>>> With or without this patch, I see no viable way to update the device >>>> tree. Is there a method ? >>> See e.g. configs/raspberrypi3_defconfig for a specialized case: >>> >>> BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" >>> >>>> What is a Raspberry Pi without a method to support the addons and hats ? >>> A minimalistic starting point for a minimal system, each add-on/hat >>> would surely need additional packages/software, each customized system >>> needs a customized configuration.... >>> >>>> Do you have a method for supporting any of the various addons/hats which >>>> would normally work with an overlay line added to /boot/config.txt ? >>>> >>> Or take a look at '[RFC] raspberrypi: post-image.sh arguments as config.txt properties ' [1] >>> for a more general approach... >>> >>> Regards, >>> Peter >>> >>> [1] https://patchwork.ozlabs.org/patch/1007728/ >> >> Thanks for the pointer. It is pretty clear that support for the RPi >> requires a lot more work and blocking revisions doesn't really help. > Don`t know what your mean by 'blocking revisions'? > >> Despite adding post_script_args, there simply isn't any way to include >> overlays in the current setup. > Your initial suggested patch shows the way to do it: > > - enable BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y > - use a customized genimage config file with overlay directory enabled > - use a customized genimage config file pointing to a customized config.txt file Yes - exactly, you can't install overlays with stock buildroot period. The system here is completely dysfunctional as far as the Raspberry Pi is concerned. There has to be a balance between your desired minimalism and functionality. Are you aware that the start.elf binary in the boot partition EXPECTS the overlays directory to be present ? It has functions which search this directory. You previously stated : "Adding a (maybe) empty overlays directory to the sdcard image would violate the minimalistic approach..." The trade off for this "minimalistic approach", is to have a dysfunctional buildroot system. It is dysfunctional because parts of the Pi's software can never execute successfully, i.e. start.elf. To correctly honor your "minimalistic approach" the start.elf binary should be correctly modified and minimised. I personally am in favour of being able to create functionally working versions of Pi boot partitions - which is why my patch includes the possibly empty overlays directory on the boot partition - as the file start.elf expects. As my "initial suggested patch shows the way to do it" why not support it ? > >> For example : >> >> If I add the variable >> BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay" >> >> It will put the following into boot/config.txt : >> >> dtoverlay=pi3-miniuart-bt >> >> But - now here is the clincher - THERE IS NO WAY TO GET OVERLAYS INTO >> THE BOOT PARTITION ! >> >> Can you please be more helpful ? I see specifically the following problems : >> >> 1] Can you suggest a better method to include overlays in the sdcard >> during a build process ? > See above... > >> 2] For a 64 bit system, does overlay loading even work ? I tried to load >> an overlay by putting dtoverlay into config.txt but it seemed to not >> even be aware of its presence ! > Should work the same way as 32 bit, but did not test it recently...how > do you determine 'not even be aware of its presence'? > >> 3] Because of 2] is there a particular place to put overlays rather then >> boot/overlays ? > Not a buildroot specific question, more for a raspberry forum..., but > according to [2] the right place for the overlays is the boot partition > overlays directory... > > Regards, > Peter > > [2] https://www.raspberrypi.org/documentation/configuration/device-tree.md > >> >> thanks >> >> Matt >> >> >> >> >>>> Matt >>>> >>>> >>>>> Regards, >>>>> Peter >>>>> >>>>> [Skipped CC to 'Matt Flax <flatmax@flatmax.org>' - mail server answers with 'mailbox unavailable'] >>>>> >>>>>> Signed-off-by: Matt Flax <flatmax@flatmax.org> >>>>>> --- >>>>>> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + >>>>>> package/rpi-firmware/rpi-firmware.mk | 4 ++++ >>>>>> 2 files changed, 5 insertions(+) >>>>>> >>>>>> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>>>> index 0d0ca750a7..af1d17cde7 100644 >>>>>> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>>>> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg >>>>>> @@ -9,6 +9,7 @@ image boot.vfat { >>>>>> "rpi-firmware/config.txt", >>>>>> "rpi-firmware/fixup.dat", >>>>>> "rpi-firmware/start.elf", >>>>>> + "rpi-firmware/overlays", >>>>>> "Image" >>>>>> } >>>>>> } >>>>>> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk >>>>>> index bb54904ae6..0df7b17cbd 100644 >>>>>> --- a/package/rpi-firmware/rpi-firmware.mk >>>>>> +++ b/package/rpi-firmware/rpi-firmware.mk >>>>>> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >>>>>> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ >>>>>> done >>>>>> endef >>>>>> +else >>>>>> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >>>>>> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; >>>>>> +endef >>>>>> endif >>>>>> >>>>>> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) >>>>> _______________________________________________ >>>>> buildroot mailing list >>>>> buildroot@busybox.net >>>>> http://lists.busybox.net/mailman/listinfo/buildroot >>>> _______________________________________________ >>>> buildroot mailing list >>>> buildroot@busybox.net >>>> http://lists.busybox.net/mailman/listinfo/buildroot >>> _______________________________________________ >>> buildroot mailing list >>> buildroot@busybox.net >>> http://lists.busybox.net/mailman/listinfo/buildroot >> _______________________________________________ >> buildroot mailing list >> buildroot@busybox.net >> http://lists.busybox.net/mailman/listinfo/buildroot > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
Matt, All, On 2019-01-03 22:00 +1100, Matt Flax spake thusly: > This patch enables the inclusion of the Pi's overlays. Previously > the overlays were not included in the genimage configuration. > This patch ensures overlays are included in the sdcard (when > enabled) by defaulting to the inclusion of an empty > output/images/rpi-firmware/overlays directory in genimage cfg. > > The Pi's overlays are built with the following config > variables: > BR2_PACKAGE_RPI_FIRMWARE=y > BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y > BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y > BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y > BR2_LINUX_KERNEL_IMAGE_NAME="Image" > BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" > > After building, the dtbo files are present in the > output/images/rpi-firmware/overlays directory but not added > to the sdcard because they are missing from the genimage cfg > file. > > Signed-off-by: Matt Flax <flatmax@flatmax.org> After a quick discussion on IRC woth Thomas, we find that this patch is indeed acceptable. However, I have a minor comment about it, see below... > --- > board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + > package/rpi-firmware/rpi-firmware.mk | 4 ++++ > 2 files changed, 5 insertions(+) > > diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg > index 0d0ca750a7..af1d17cde7 100644 > --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg > +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg > @@ -9,6 +9,7 @@ image boot.vfat { > "rpi-firmware/config.txt", > "rpi-firmware/fixup.dat", > "rpi-firmware/start.elf", > + "rpi-firmware/overlays", > "Image" > } > } > diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk > index bb54904ae6..0df7b17cbd 100644 > --- a/package/rpi-firmware/rpi-firmware.mk > +++ b/package/rpi-firmware/rpi-firmware.mk > @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ > done > endef > +else > +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS > + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; No need for the '|| exit 1' part in this case. It is important to use it ion the loop, above, because it is a shell loop, so an error in the commands would not be noticed. Here however, this is a single command, so it will return in error if it fils and make will notice. Barring that, which can be fixed when applying: Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> > +endef > endif > > ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) > -- > 2.19.1 > > _______________________________________________ > buildroot mailing list > buildroot@busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot
On 13/04/2019 23:06, Yann E. MORIN wrote: > Matt, All, > > On 2019-01-03 22:00 +1100, Matt Flax spake thusly: >> This patch enables the inclusion of the Pi's overlays. Previously >> the overlays were not included in the genimage configuration. >> This patch ensures overlays are included in the sdcard (when >> enabled) by defaulting to the inclusion of an empty >> output/images/rpi-firmware/overlays directory in genimage cfg. >> >> The Pi's overlays are built with the following config >> variables: >> BR2_PACKAGE_RPI_FIRMWARE=y >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y >> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y >> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y >> BR2_LINUX_KERNEL_IMAGE_NAME="Image" >> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" >> >> After building, the dtbo files are present in the >> output/images/rpi-firmware/overlays directory but not added >> to the sdcard because they are missing from the genimage cfg >> file. >> >> Signed-off-by: Matt Flax <flatmax@flatmax.org> > > After a quick discussion on IRC woth Thomas, we find that this patch is > indeed acceptable. > > However, I have a minor comment about it, see below... > >> --- >> board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + >> package/rpi-firmware/rpi-firmware.mk | 4 ++++ >> 2 files changed, 5 insertions(+) >> >> diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg >> index 0d0ca750a7..af1d17cde7 100644 >> --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg >> +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg >> @@ -9,6 +9,7 @@ image boot.vfat { >> "rpi-firmware/config.txt", >> "rpi-firmware/fixup.dat", >> "rpi-firmware/start.elf", >> + "rpi-firmware/overlays", >> "Image" >> } >> } >> diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk >> index bb54904ae6..0df7b17cbd 100644 >> --- a/package/rpi-firmware/rpi-firmware.mk >> +++ b/package/rpi-firmware/rpi-firmware.mk >> @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >> $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ >> done >> endef >> +else >> +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS >> + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; > > No need for the '|| exit 1' part in this case. Also it was indented too much, and the trailing semicolon was not needed. Also, I've added a brief comment explaining why we create this empty directory. Peter, we discussed this on IRC and we feel that one empty directory doesn't violate the minimalistic principle too much, because it does make life a lot easier when you start from the existing defconfig. So, I've applied to master with the changes mentioned above. Regards, Arnout > > It is important to use it ion the loop, above, because it is a shell > loop, so an error in the commands would not be noticed. Here however, > this is a single command, so it will return in error if it fils and make > will notice. > > Barring that, which can be fixed when applying: > > Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> > >> +endef >> endif >> >> ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y) >> -- >> 2.19.1 >> >> _______________________________________________ >> buildroot mailing list >> buildroot@busybox.net >> http://lists.busybox.net/mailman/listinfo/buildroot >
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes: Hi, > On 13/04/2019 23:06, Yann E. MORIN wrote: >> Matt, All, >> >> On 2019-01-03 22:00 +1100, Matt Flax spake thusly: >>> This patch enables the inclusion of the Pi's overlays. Previously >>> the overlays were not included in the genimage configuration. >>> This patch ensures overlays are included in the sdcard (when >>> enabled) by defaulting to the inclusion of an empty >>> output/images/rpi-firmware/overlays directory in genimage cfg. >>> >>> The Pi's overlays are built with the following config >>> variables: >>> BR2_PACKAGE_RPI_FIRMWARE=y >>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y >>> BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y >>> BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y >>> BR2_LINUX_KERNEL_IMAGE_NAME="Image" >>> BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" >>> >>> After building, the dtbo files are present in the >>> output/images/rpi-firmware/overlays directory but not added >>> to the sdcard because they are missing from the genimage cfg >>> file. >>> >>> Signed-off-by: Matt Flax <flatmax@flatmax.org> >> > Also, I've added a brief comment explaining why we create this empty directory. > Peter, we discussed this on IRC and we feel that one empty directory doesn't > violate the minimalistic principle too much, because it does make life a lot > easier when you start from the existing defconfig. > So, I've applied to master with the changes mentioned above. Committed to 2019.02.x, thanks.
diff --git a/board/raspberrypi/genimage-raspberrypi3-64.cfg b/board/raspberrypi/genimage-raspberrypi3-64.cfg index 0d0ca750a7..af1d17cde7 100644 --- a/board/raspberrypi/genimage-raspberrypi3-64.cfg +++ b/board/raspberrypi/genimage-raspberrypi3-64.cfg @@ -9,6 +9,7 @@ image boot.vfat { "rpi-firmware/config.txt", "rpi-firmware/fixup.dat", "rpi-firmware/start.elf", + "rpi-firmware/overlays", "Image" } } diff --git a/package/rpi-firmware/rpi-firmware.mk b/package/rpi-firmware/rpi-firmware.mk index bb54904ae6..0df7b17cbd 100644 --- a/package/rpi-firmware/rpi-firmware.mk +++ b/package/rpi-firmware/rpi-firmware.mk @@ -24,6 +24,10 @@ define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS $(INSTALL) -D -m 0644 $${ovldtb} $(BINARIES_DIR)/rpi-firmware/overlays/$${ovldtb##*/} || exit 1; \ done endef +else +define RPI_FIRMWARE_INSTALL_DTB_OVERLAYS + $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays || exit 1; +endef endif ifeq ($(BR2_PACKAGE_RPI_FIRMWARE_INSTALL_VCDBG),y)
This patch enables the inclusion of the Pi's overlays. Previously the overlays were not included in the genimage configuration. This patch ensures overlays are included in the sdcard (when enabled) by defaulting to the inclusion of an empty output/images/rpi-firmware/overlays directory in genimage cfg. The Pi's overlays are built with the following config variables: BR2_PACKAGE_RPI_FIRMWARE=y BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTBS=y BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS=y BR2_LINUX_KERNEL_IMAGE_TARGET_CUSTOM=y BR2_LINUX_KERNEL_IMAGE_NAME="Image" BR2_LINUX_KERNEL_IMAGE_TARGET_NAME="Image modules dtbs" After building, the dtbo files are present in the output/images/rpi-firmware/overlays directory but not added to the sdcard because they are missing from the genimage cfg file. Signed-off-by: Matt Flax <flatmax@flatmax.org> --- board/raspberrypi/genimage-raspberrypi3-64.cfg | 1 + package/rpi-firmware/rpi-firmware.mk | 4 ++++ 2 files changed, 5 insertions(+)