Your message dated Sun, 08 May 2022 17:34:14 +0000 with message-id <[email protected]> and subject line Bug#996937: fixed in raspi-firmware 1.20220331+ds-2 has caused the Debian Bug report #996937, regarding raspi-firmware: possibly disable cma= setting on Pi CM4 as well 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 [email protected] immediately.) -- 996937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996937 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: raspi-firmware Version: 1.20210303+ds-2 Severity: normal Hi, Looking at #980536, and if I'm reading between the lines correctly, the whole Pi 4 family should have no cma= setting, and we should be skipping it on the Compute Module 4 the same way we do on the Pi 4. The current check happens with: grep -q 'Raspberry Pi 4' /proc/device-tree/model If my understanding is correct, we should be additionally checking: grep -q 'Raspberry Pi Compute Module 4' /proc/device-tree/model This would avoid re-adding cma=$CMA (with CMA defaulting to 64M) on the CM4, which the image-specs build disabled initially, when producing the image with `make raspi_4_bullseye.img`. If the setting is confirmed to be extraneous, and is gotten rid of, it would reduce the differences between before/after first boot's cmdline.txt (see also [1]). 1. https://salsa.debian.org/raspi-team/image-specs/-/issues/57 I'm happy to propose a tested patch once I have a confirmation regarding the “should we do it” part. :) Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
--- End Message ---
--- Begin Message ---Source: raspi-firmware Source-Version: 1.20220331+ds-2 Done: Cyril Brulebois <[email protected]> We believe that the bug you reported is fixed in the latest version of raspi-firmware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cyril Brulebois <[email protected]> (supplier of updated raspi-firmware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 08 May 2022 19:14:25 +0200 Source: raspi-firmware Architecture: source Version: 1.20220331+ds-2 Distribution: unstable Urgency: medium Maintainer: pkg-raspi <[email protected]> Changed-By: Cyril Brulebois <[email protected]> Closes: 996937 Changes: raspi-firmware (1.20220331+ds-2) unstable; urgency=medium . * Factorize Pi 4 detection, used for GPU_FREQ and CMA settings. Also discard confusing error messages when neither /sys/firmware/devicetree nor /proc/device-tree exist, which is the case when building images (e.g. with image-specs). * Add support for Compute Module 4 devices: they are in the Pi 4 family as well, just like the Pi 4 B and Pi 400 models, need the same tweaks for the CMA setting, and might require adjusting GPU_FREQ to ensure the serial console is usable (Closes: #996937). Checksums-Sha1: 4139d7dbfc118cf8ac74e8d3bb194e9e4cd324eb 2230 raspi-firmware_1.20220331+ds-2.dsc e0fe7f65c8eea1b2294d6f172f929dde7f74e379 378784 raspi-firmware_1.20220331+ds-2.debian.tar.xz 44e31d6773426e952ff073a9ed48c7638ab879f3 6311 raspi-firmware_1.20220331+ds-2_source.buildinfo Checksums-Sha256: cbd0446678a8829d0734cb3f8de6f6cc957d1ce247ba55e5d7573eb7b664f5de 2230 raspi-firmware_1.20220331+ds-2.dsc aa69cca86134e7bb71630988bafbd83a9b5f6b0b9a24fd024c0d08651be8cd9e 378784 raspi-firmware_1.20220331+ds-2.debian.tar.xz fe18f972d9acd24d4a5ddde9dbe06811b19529ea930bb58ed6c89f9d0984c377 6311 raspi-firmware_1.20220331+ds-2_source.buildinfo Files: 90325b6b8c8d1b5acbaa715ce2db49a8 2230 non-free/misc optional raspi-firmware_1.20220331+ds-2.dsc 367e4e479e36ce41ee17af9f18883614 378784 non-free/misc optional raspi-firmware_1.20220331+ds-2.debian.tar.xz 8dbce33c4156d38baff717495d4d493e 6311 non-free/misc optional raspi-firmware_1.20220331+ds-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmJ3+yYQHGtpYmlAZGVi aWFuLm9yZwAKCRD/kUrwwrNVIOoTEAC8MPwCRk+vHdorKysJ5Ur4U9dOry9G+qGr 3oA5vtWvU6Y3KjcYNhF1Fj6VET30vBuicFmVx4ZrU5edykCF3DQO8rBQqhgu2oUt 2gkZCWdpCiL1jT0rs+UV95pIVIfq/CH808adm1kcMTkbVYvr4+OuaMTCINHR7bco kQB6v90EMuFF5lZqlUid+NTytorDEZiRVfaMsMnsoWEe34Ss7IlHCj97eN2W6BrS BUh84ThwzykoA1WbbxTHvkcxUL9aBW3ZO8Vev6Li+kiL72JrvNLS1DatH2cxvPmK NTzNXyT3Bju01ghHRWAD+tnNoeyUsDrX8fHsF05M1iZ6DIDKvny8JsTWZvjDKkeW bc09N/oD65r397hjA7VSRsETEQ+0W0+0OC5aQoprIpVqsrtgto3rptej4S5oxkoR DIlS+658Kc89zboUb8TMVy7x5Qnbl9vk49Yn23t6iBpZBepXrfDBu+5QXxC8R9B8 goyhMnUTZdk15HQvKvqtp5CHd5UdrlrmBPsPqw6lGx91UMDdnjeFNcwwzd0yoGff nJwmO0bHzG1YFAS223i6nO0QgH41r4AxDEmV2qV30BqzSjsTmxiilHS5hc/m6kaG HaRDTr7MLZtpCzSrgb31wANBwhccCjMSBEiTQNlWqxrNBZqpiRdCF34Ie4exSDoo kVgXQMOJQg== =qBEO -----END PGP SIGNATURE-----
--- End Message ---
