[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#935386: marked as done (buster-pu: package raspi3-firmware/1.20190215-1+deb10u1)

Your message dated Sat, 07 Sep 2019 14:34:49 +0100
with message-id <[🔎] f49e2985d8466065c49c03185c24465a32228fb5.camel@adam-barratt.org.uk>
and subject line Closing bugs for fixes including in 10.1 point release
has caused the Debian Bug report #935386,
regarding buster-pu: package raspi3-firmware/1.20190215-1+deb10u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
935386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935386
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

Hi,

I'd like to request a raspi3-firmware update in buster to add some
hardware support. The buster kernel already had all required code to
handle Raspberry Pi CM 3 in addition to the regular Raspberry Pi 3 but
the former needs:
 - an updated linux kernel which ships an extra DTB;
 - an updated raspi3-firmware that deploys the extra DTB under
   /boot/firmware.

The kernel part was requested in:
 - https://bugs.debian.org/932157
 - https://salsa.debian.org/kernel-team/linux/merge_requests/155

and is available starting from 4.19.37-6. I wasn't sure how 4.19.y
updates would be handled in sid and in buster, but it seems the most
recent upload to buster (yesterday) didn't include those patches.

I'll double check that my cherry-picks on top of the buster branch
still do the trick, but it seems to me we should be able to move this
pu request forward without blocking on the linux bits.

The changelog reads:

,---
| raspi3-firmware (1.20190215-1+deb10u1) buster; urgency=medium
| 
|   * Add support for bcm2837-rpi-cm3-io3.dtb (as generated by the Linux
|     kernel build system) aka. bcm2710-rpi-cm3.dtb (as expected by the
|     bootloader), designed to work for:
|      - Raspberry Pi Compute Module 3 (CM3);
|      - Raspberry Pi Compute Module 3 Lite (CM3L);
|      - Raspberry Pi Compute Module IO Board V3.
|     With many thanks to Charles Fendt for the tests (#932158).
|   * The DTB addition in the linux source package is tracked in #932157.
| 
|  -- Cyril Brulebois <cyril@debamax.com>  Thu, 22 Aug 2019 09:15:16 +0200
`----

and the full source debdiff is attached.


(I've OK'd this pu request with Romain Perier, who is one of the
maintainers; all of them are in X-D-Cc anyway.)


Thanks for considering, thanks for your time.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

diff --git a/debian/changelog b/debian/changelog
index d79fda7..9ac783f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+raspi3-firmware (1.20190215-1+deb10u1) buster; urgency=medium
+
+  * Add support for bcm2837-rpi-cm3-io3.dtb (as generated by the Linux
+    kernel build system) aka. bcm2710-rpi-cm3.dtb (as expected by the
+    bootloader), designed to work for:
+     - Raspberry Pi Compute Module 3 (CM3);
+     - Raspberry Pi Compute Module 3 Lite (CM3L);
+     - Raspberry Pi Compute Module IO Board V3.
+    With many thanks to Charles Fendt for the tests (#932158).
+  * The DTB addition in the linux source package is tracked in #932157.
+
+ -- Cyril Brulebois <cyril@debamax.com>  Thu, 22 Aug 2019 09:15:16 +0200
+
 raspi3-firmware (1.20190215-1) unstable; urgency=medium
 
   [ Gunnar Wolf ]
diff --git a/debian/kernel/postinst.d/z50-raspi3-firmware b/debian/kernel/postinst.d/z50-raspi3-firmware
index d91c0b8..14b81bf 100755
--- a/debian/kernel/postinst.d/z50-raspi3-firmware
+++ b/debian/kernel/postinst.d/z50-raspi3-firmware
@@ -70,6 +70,7 @@ if [ "$KERNEL" = "auto" ]; then
   pi2b_dtb=${dtb_path}/bcm2836-rpi-2-b.dtb
   pi3b_dtb=${dtb_path}/bcm2837-rpi-3-b.dtb
   pi3bp_dtb=${dtb_path}/bcm2837-rpi-3-b-plus.dtb
+  picm3_dtb=${dtb_path}/bcm2837-rpi-cm3-io3.dtb
 
   [ -e "${pi0w_dtb}"  ] && cp "${pi0w_dtb}"  /boot/firmware/bcm2835-rpi-zero-w.dtb
   [ -e "${pi1ap_dtb}"  ] && cp "${pi1ap_dtb}" /boot/firmware/bcm2835-rpi-a-plus.dtb
@@ -77,6 +78,7 @@ if [ "$KERNEL" = "auto" ]; then
   [ -e "${pi2b_dtb}"  ] && cp "${pi2b_dtb}"  /boot/firmware/bcm2709-rpi-2-b.dtb
   [ -e "${pi3b_dtb}"  ] && cp "${pi3b_dtb}"  /boot/firmware/bcm2710-rpi-3-b.dtb
   [ -e "${pi3bp_dtb}" ] && cp "${pi3bp_dtb}" /boot/firmware/bcm2710-rpi-3-b-plus.dtb
+  [ -e "${picm3_dtb}" ] && cp "${picm3_dtb}" /boot/firmware/bcm2710-rpi-cm3.dtb
 
   latest_kernel_basename=$(basename "$latest_kernel")
   latest_initrd_basename=$(basename "$latest_initrd")

--- End Message ---
--- Begin Message --- 
Version: 10.1

Hi,

The fixes referenced by each of these bugs were included in today's
buster point release.

Regards,

Adam

--- End Message ---
Reply to: