> Thanks for the suggestions. I'll experiment with my setup when I get > home today and report back. I'm not sure at this moment if it didn't > detect the SD card or if the device names somehow changed. Or if it's > really just the armstub thingy.
No problem. Incidentally, I wouldn't be surprised if it didn't detect the SD card. The MMC interface changed quite a bit with the Pi4; it's a new device, new clock, etc. In fact the bulk of the Pi4 patches for u-boot were concerned with the MMC device. The new Pi4 compatible kernel for eoan was only released a few days ago, so I'd recommend running an upgrade on a Pi3 first if you haven't upgraded in the last 2 or 3 days, just to make sure you've got that kernel version. > Thanks for the headsup. I was planning to use u-boot again in the near > future, anyways. The reason I stopped using it was that there were > several changes of the DTB address about a year ago and there was a > mismatch between the inofficial raspi2-pi3 PPA (0x200) and the default > packages (0x0200000-something) and my config.txt (always had the wrong > one). That broke things on my Raspberrys a few times so I switched to > the u-boot-less config to not have to bother about DTB memory addresses > anymore. Ahh, the device-tree address mess! I've been steadily cleaning up bits of this but there's still a bit more to do. All the classic bootscripts for eoan should be using 0x3000000 for the device-tree address, however I think it's still hard-coded in the u-boot script when it should be using the value passed by the firmware (I only recently discovered our u-boot builds were entirely ignoring the device-tree passed by the firmware; that's now fixed, but they're still using a hard-coded address at the moment). We should start porting most of this back to bionic (and disco I assume) after the eoan release, so pi4 compatibility will be coming to those releases in due course. > Do you know if booting via u-boot makes the whole 4GB RAM accessible to > the system or is there still a limit of 1GB? Good question - not something I'd tested (my main concern has been getting the thing booting and ensuring that we don't break any existing platforms at the same time!), but I've just tested it and currently it looks like only the first 1Gb is currently accessible. I'd *guess* that's a limitation due to u-boot, but I'll try and find time to test the kernel alone to confirm that. Obviously it's something we'll want to sort out fairly quickly but I suspect it'll have to be post-release at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
