I have my Rock 5B booting Fedora 40 Beta on NVMe, using EDK2 on an SD card. I would like to flash the EDK2 image to SPI, but this requires access to /dev/mtdblock* devices. There appear to be none.
Could this be related to the ACPI vs DTB setting in the EDK2? Fedora 40 Beta will not boot in DTB mode, and possibly this is required for automatically creating /dev/mtdblock* devices.
I have my Rock 5B booting Fedora 40 Beta on NVMe, using EDK2 on an SD card. I would like to flash the EDK2 image to SPI, but this requires access to /dev/mtdblock* devices. There appear to be none.
Could this be related to the ACPI vs DTB setting in the EDK2?
It could be that, it could be also that edk2 doesn't expose the mtd devices as EDK2 treats them as owned by the firmware but then I don't know if edk2 for that platform would support something like EFI capsule updates.
Fedora 40 Beta will not boot in DTB mode, and possibly this is required for automatically creating /dev/mtdblock* devices.
I am purely looking at supporting the Rock5B with a U-Boot firmware stack so that's where I am testing, the problem with ACPI on this platform is that the vast majority of the drivers don't currently support ACPI so even if the mtd is in the ACPI tables the drivers may not support it.
Hi there,
on my system I've written the EDK2 image to the SPI via a second boot based on a Armbian Image.
Greetings
Andreas
PS: yes the availibility of /dev/mtdblock* would be fine. Much better is a UBoot image that comes direct with fedora like other ARM-Systems (Pinebook Pro).
Am 08.04.24 um 18:34 schrieb Peter Robinson:
I have my Rock 5B booting Fedora 40 Beta on NVMe, using EDK2 on an SD card. I would like to flash the EDK2 image to SPI, but this requires access to /dev/mtdblock* devices. There appear to be none.
Could this be related to the ACPI vs DTB setting in the EDK2?
It could be that, it could be also that edk2 doesn't expose the mtd devices as EDK2 treats them as owned by the firmware but then I don't know if edk2 for that platform would support something like EFI capsule updates.
Fedora 40 Beta will not boot in DTB mode, and possibly this is required for automatically creating /dev/mtdblock* devices.
I am purely looking at supporting the Rock5B with a U-Boot firmware stack so that's where I am testing, the problem with ACPI on this platform is that the vast majority of the drivers don't currently support ACPI so even if the mtd is in the ACPI tables the drivers may not support it. -- _______________________________________________ arm mailing list --arm@lists.fedoraproject.org To unsubscribe send an email toarm-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue