Hi Peter,
Thanks for taking a look at these patches and taking them for a spin!
> Can you also provide details of which revisions of rpi devices you
> tested this on?
I've tested this on the 16gb v1.1 -- it's the only bcm2712 device I've got,
unfortunately.
The EEPROM bootloader reports:
4.07 BOOTMODE: 0x06 partition 0 build-ts BUILD_TIMESTAMP=1756339608
serial b36eabd9 boardrev e04171 stc 4076083
The board_revision from environment is set to:
U-Boot> printenv board_revision
board_revision=0xE04171
Which matches what I can see in the dtb:
U-Boot> fdt print /system
system {
linux,serial = <0xf849b6d5 0xb36eabd9>;
linux,revision = <0x00e04171>;
};
In Linux, /proc/cpuinfo reports:
Serial : f849b6d5b36eabd9
Model : Raspberry Pi 5 Model B Rev 1.1
Additionally, I can see that the EEPROM bootloader lists these dtbos, even
though I don't have them on my boot partition:
9.15 /overlays/overlay_map.dtb
9.16 /overlays/bcm2712d0.dtbo
I wonder what it lists for the c1 variant.
> I have an 8gb v1.0, and I thought I had a v1.1 2Gb but looking closer
> it looks like that's the old c1 SoC rev (I read their original
> announcement for the 2Gb variant as they were all 1.1, it appears
> not).
Do I understand correctly that the c1 reports as v1.1 as well, which causes
the bcm2712d0-rpi-5-b.dtb to match? If that's the case, I wonder how the
EEPROM
bootloader differentiates between c1 and d0, as both have the 0x17 type.
> I have ordered the new 1Gb variant so I have a revD I can test
> against.
Looking forward to hearing about that from you!
Best
FK
