> Date: Mon, 20 Apr 2020 22:18:06 +0100 > From: Stuart Henderson <[email protected]> > > On 2020/04/19 21:44, Mark Kettenis wrote: > > The Raspberry Pi 4 has an additional SD/MMC controller. This > > controller is almost completely standard and just needs one tiny > > quirk. So the diff is really simple. > > > > By default, if you use the EDK2-base UEFI firmware this controller > > isn't actually connected to anything. So you'll see > > > > sdmmc0: can't enable card > > > > in your dmesg. If you change the "Raspberry Pi Configuration" -> > > "SD/MMC Configuration" -> "uSD routing" setting in the "Device > > Manager" firmware configuration screen to "eMMC2 SDHCI". The uSD card > > will show up behind this controller and WiFi will show up on the other > > controller. Note that after you've made that configuration change and > > reset the machine, any further change you make won't stick. You can > > fix this by replacing the RPI_EFI.fd file on the MS-DOS partition of > > your uSD card. > > > > For now the SDHC controllers are only supported in device tree mode > > which can be enabled using the "Raspberry Pi Configuration" -> > > "Advanced Configuration" -> "Device Tree" option in the "Device > > Manager". > > bwfm(4) is working for me, but when in device tree mode (wherever the > uSD is routed) bse(4) is flaky - ethernet link doesn't come up at boot, > if I leave it for a little while with a ping running to the bse from > another machine I get the occasional packet through but that's all. > Do you see that too?
I don't see that, but I suspect this is because the device tree has phy-mode set to "rgmii" instead of "rgmii-rxid". A workaround is to take the bcm2711-rpi-4-b.dtb, fixup4.dat and start4.elf files from https://github.com/raspberrypi/firmware/tree/next/boot and put them on the MS-DOS partition of your uSD card.
