FYI - the qemu spec for these file-format is here
https://gitlab.com/qemu-project/qemu/-/blob/v6.0.0/docs/interop/firmware.json

The only big case for it so far has been uefi which used to be a stressful 
manual file copy and selection which now can be done trivially by specifying a 
few features. Via those it will negotiate and find the right firmware file to 
load.
Some background on that in:
  https://bugzilla.redhat.com/show_bug.cgi?id=1728652

It also helps distro packaging which tends to not use all firmware from
qemu source but e.g. an extra edk2. This way it can provide the paths
which happen to be distro specific.

So to make sure I get it right, @xnox you want it to map
   qemu-system-riscv64 -machine virt
to realize "oh wait I have a fw file for that" and thereby instruct it to load 
our opensbi/uboot/edk2 from the right places - is that what you ask for?

If the above understanding of your request is true, then (so far) the
right place has been the source for these firmware images. E.g.
opensbi/uboot in this case - those source packages are the ones knowing
which variants they place and at which path.

But TBH I've not seen this in use/discussion for uboot/riscv64 yet so far. 
There might be some code (in contrast to just a few descriptive json files) 
needed to fully work for this use case. If you think that is the case I'd 
recommend to file upstream bugs at 
https://gitlab.com/qemu-project/qemu/-/issues / 
https://gitlab.com/libvirt/libvirt/-/issues and link them from here).
That way we'd have upstream "in the boat" from day #1

** Bug watch added: Red Hat Bugzilla #1728652
   https://bugzilla.redhat.com/show_bug.cgi?id=1728652

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904802

Title:
  please provide firmware file for riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1904802/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to