qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: changing ROM bundling in tar dists for releases
Date: Fri, 01 Sep 2017 19:45:16 +0200	[thread overview]
Message-ID: <1504287916.10150.21.camel@redhat.com> (raw)
In-Reply-To: <20170901151340.GQ31680@redhat.com>

  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-firmware, and add that directory to
the qemu default search path.

> So non-distro users would need to download & install the ROMs,
> and then download, build & install QEMU ?

Yes.

> How would you view ROM install working for devs working against GIT ?
> 
> eg when we update a ROM in the firmware directory, how do devs know
> to
> update their firmware.  Would the qemu-firmware.git be a submodule of
> qemu.git, so that a 'make install' would deploy roms for devs ?

Not sure yet how to handle that best.  I'd tend to not make it a
submodule.  Typically there are no lockstep updates for qemu and
firmware, in most cases new firmware is only required if you want use a
new feature which needs firmware support.  So I think we don't need a
tight coupling between qemu and firmware.  Just updating the firmware
checkout now and then (or even simply using the distro builds) should
work in the vast majority of cases.

cheers,
  Gerd

  reply	other threads:[~2017-09-01 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 12:29 [Qemu-devel] RFC: changing ROM bundling in tar dists for releases Daniel P. Berrange
2017-08-31 12:49 ` Peter Maydell
2017-09-01  8:31   ` Gerd Hoffmann
2017-09-01  9:24     ` Daniel P. Berrange
2017-09-01  9:49       ` Gerd Hoffmann
2017-09-01 11:00       ` Peter Maydell
2017-09-01 14:11     ` Gerd Hoffmann
2017-09-01 15:13       ` Daniel P. Berrange
2017-09-01 17:45         ` Gerd Hoffmann [this message]
2017-08-31 15:47 ` Philippe Mathieu-Daudé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1504287916.10150.21.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).