popcornmix

> Doesn't this change mean that uname -m is returning the wrong value? libc etc are still 32 bit so any build that attempts to detect the architecture using uname...

@XECDesign are arm64 kernel headers available on 32-bit RPiOS through apt?

Until that package is available it may be possible to use [rpi-source](https://github.com/RPi-Distro/rpi-source)

@oilcan-productions "fails" doesn't help much. Describe exactly what you are doing, what should happen, what currently happens, and if setting `arm_64bit=0` avoids the issue.

The recommended way forward would be to use the kms driver, lite image (or boot to console) and the use DRM to drive each display. [kmstest](https://github.com/tomba/kmsxx/blob/master/utils/kmstest.cpp), [modetest](https://github.com/grate-driver/libdrm/blob/master/tests/modetest/modetest.c) and [drmu](https://github.com/jc-kynesim/drmu) may...

The current apt firmware is: ``` pi@pi5:~ $ apt policy raspi-firmware raspi-firmware: Installed: 1:1.20240306+ds-1+rpt1 Candidate: 1:1.20240306+ds-1+rpt1 Version table: *** 1:1.20240306+ds-1+rpt1 500 500 http://buildbot.pitowers.org:3143 bookworm/main arm64 Packages 500 http://buildbot.pitowers.org:3143 bookworm/main armhf...

So the plan is stable branch of raspberrypi/firmware gets tagged. The github action builds a release tarball that gets used by the raspi-firmware apt package in RPiOS (and can be...

That's what we've been told is the limit of the PLL by Broadcom. I've got a todo item to investigate what happens when this is exceeded, but it's not high...

[rpi-eeprom-recovery.zip](https://github.com/raspberrypi/firmware/files/14604820/rpi-eeprom-recovery.zip) I've removed the 3GHz limit, and attached a zip file (you can flash it to an sdcard with rpi-imager) you can test. Make sure you have no critical (unbacked...

Yes - use a spare card.