Hi,
> > i.e. something like this:
> >
> > https://www.kraxel.org/cgit/qemu-firmware/
> >
> > (only seabios is there for now)
>
> So presumably we'd want a 'make install' target there too, to place
> the
> various ROMS in the location QEMU expects ?
Yes.
Or place them in $prefix/share/qemu-f
On Fri, Sep 01, 2017 at 04:11:44PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > I think it makes sense to create a separate project for the firmware
> > blobs. Move over the firmware binaries and source submodules to the
> > new project. This way updating both firmware sources and binaries
> > can
Hi,
> I think it makes sense to create a separate project for the firmware
> blobs. Move over the firmware binaries and source submodules to the
> new project. This way updating both firmware sources and binaries
> can
> be done with a single commit, like we handle this today, just in the
> ne
On 1 September 2017 at 10:24, Daniel P. Berrange wrote:
> I've always wondered why we need to specialcase those modules at all.
> Personally I'd just remove them entirely and let people install the
> -dev packages on their distro just like they do for any other build
> prerequisite of QEMU.
Two u
Hi,
> > Question is what to do with the non-firmware submodules (pixman,
> > dtc,
> > more?) then. I think they are not that big, so I doubt it is worth
> > the
> > hassle to create two tarball versions. And license-wise it isn't a
> > issue too.
>
> I've always wondered why we need to specia
On Fri, Sep 01, 2017 at 10:31:17AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > - The qemu release dists get ever larger as we add more ROMS.
> > > Adding
> > > EFI ROM builds for i386, x86_64, and aarch64 will make the dists
> > > larger still.
> >
> > I think these make sense. Should we ti
Hi,
> > - The qemu release dists get ever larger as we add more ROMS.
> > Adding
> > EFI ROM builds for i386, x86_64, and aarch64 will make the dists
> > larger still.
>
> I think these make sense. Should we tie this into the
> recent suggestion (by Gerd?) that we should put all the
> rom
On 08/31/2017 09:29 AM, Daniel P. Berrange wrote:
[...]> There are the following options I see
1. Keep existing dist, and add a new minimal one
qemu-X.Y.Z.tar.bz2 - qemu source + bundled ROMS + libs
qemu-minimal-X.Y.Z.tar.bz2 - qemu source only
Least impact for current
On 31 August 2017 at 13:29, Daniel P. Berrange wrote:
> A while back now I posted an RFC patch that changes qemu-X.Y.Z.tar.bz2
> archive to *not* have any ROMs or 3rd party libs bundled, and create a
> new dist qemu-bundled-X.Y.Z.tar.bz2 for the fully bundled dist:
>
> http://lists.gnu.org/archi
A while back now I posted an RFC patch that changes qemu-X.Y.Z.tar.bz2
archive to *not* have any ROMs or 3rd party libs bundled, and create a
new dist qemu-bundled-X.Y.Z.tar.bz2 for the fully bundled dist:
http://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03335.html
With 2.10 out of the w
10 matches
Mail list logo
