On Wed, Mar 22, 2023 at 04:52:34PM +0000, Daniel P. Berrangé wrote:
On Wed, Mar 22, 2023 at 11:37:10AM -0500, Andrea Bolognani wrote:
Note that the firmware descriptor format already supports u-boot as the firmware type. So in the long run ideally you'd only need to specify
<os firmware='uboot'>
and, assuming the uboot-images-riscv64 package is installed on the host, everything should just work.
And that would bring alignment with other architectures approach, which is preferrable to adding a special hack needed for riscv, because the latter is something that most mgmt apps will forget to use.
Absolutely. We still need support for manual firmware selection and direct kernel boot though.
Of course even better would be for riscv64 to use UEFI :-)
That should already be possible[1], but it's still unclear whether in the long run it will become the de facto standard. Either way, it might take a few more years to get to that point. [1] https://packages.fedoraproject.org/pkgs/edk2/edk2-riscv64/ -- Andrea Bolognani / Red Hat / Virtualization