On 07/24/2012 03:10 PM, Cole Robinson wrote:
> Hi all,
>
> QEMU release tarballs contain a handful of prebuilt roms that enable various
> features and emulation targets. We currently don't package any of these roms.
>
> For things like seabios, sgabios, vgabios, and ipxe, we can chuck out the
> prebuilt data and depend on natively built Fedora packages. However a handful
> of the roms require building on non-x86 (ppc, sparc32/64, s390). Being able to
> package the prebuilt roms would enable us to distribute working
> qemu-system-{ppc*,sparc*,s390*}
>
> Does this sound reasonable, and if so, what's the process for getting this
> approved? I'm looking at:
I really do wish we could come up with a clever way to build these on
the native platforms, but I also understand how difficult that is, and I
really don't want to stonewall on that.
Perhaps this merits a specific exception. How about something like this:
=== QEMU ROMS ===
Whenever possible, ROMS implementing BIOS or Firmware for QEMU system
targets must be built from source on the intended architecture. However,
in many situations, this is not practical or possible. As a special
exception, prebuilt binary ROMS implementing BIOS or Firmware for QEMU
system targets may be included in Fedora Packages, as long as the
corresponding source code is also included in the Source RPM package.
Thoughts?
> /usr/share/qemu/petalogix-ml605.dtb
> /usr/share/qemu/petalogix-s3adsp1800.dtb
> Usage : Needed for microblaze emulation
> Source : Hmm, actually I can't seem to find any canonical source :(
This one seems more troublesome than the others, but since .dtb files
seem to be just device trees without any real "code", we can safely
treat them as content.
~tom
==
Fedora Project
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging
