-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for booting from a "superfloppy" disk #120
Comments
Yes, it's MBR only, maybe GPT in future, but that's low priority. Adding support for niche features even if it was supported on earlier models increases code complexity and test burden so I'm marking this as not-going-to-fix |
Indeed, GPT support would be better. In fact I was using superfloppy to workaround the lack of native GPT support. |
Thanks that’s useful to know |
Since we are adding GPT and 0xef partition support we may as well add SuperFloppy whilst we are editing that bit of code. |
* Resolve: USB boot fails if the GPT contains no basic data or EFI partitions #130 * Resolve: Fix default BOOT_ORDER in mass storage beta #129 * Resolve: Add support for booting from a "superfloppy" disk #120 * Resolve: USB MSD timeout message - incorrect units #131 * Resolve: Recognize efi partition (0xef) as a valid boot #126 * The HDMI diagnostics screen now displays the most significant bytes of the SHA-256 of the config.txt file.
This should be fixed by e87bc4d The binaries are available in this release which can be flashed using the Raspberry Pi Imager |
Fix is now available via rpi-eeprom apt package |
The boot ROM itself can boot just fine from a superfloppy disk (i've tested this with the recovery.bin image), but if there's no recovery image on the disk, it loads the EEPROM bootloader which can only boot from MBR-partitioned disks.
This worked fine on the Pi 3 as the bootcode was loaded by the boot ROM directly from the SD card.
The text was updated successfully, but these errors were encountered: