From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: vgabios and other guest related firmware
Date: Wed, 2 Jan 2008 03:30:39 -0600 [thread overview]
Message-ID: <20080102093039.GC8605@tapir> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCBB773B-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, Jan 02, 2008 at 04:14:53PM +0800, Zhang, Xiantao wrote:
> Carlo Marcelo Arenas Belon wrote:
> >
> > I'll let the specifics to all the portability interested parties (I
> > mostly use PC) but would suspect something similar to the work done
> > for the code should be most likely what is needed :
> >
> > firmware -- x86 -- bios
> > | |- vgabios
> > |- ia64
>
> Good idea!
this was meant to be for the source files of the firmware that is needed
for each guest architecture, just like is being done now for x86 (both i386
and x86_64) with bios and vgabios.
for ia64 it will most likely include the opensource EFI firmware imported
and plus any needed patches to make it work perfectly with kvm.
> We also need to upload the ia64 firmware for kvm, and make it
> available for users use. At least, we need to provide the binary.
beware that actually providing the binary without sources might be a problem
for some distributions (like debian and derivatives like ubuntu).
most likely getting the sources and a makefile which could be used to build
the binary and copy it to the qemu/pc-bios/ directory, at release time or when
the sources had been changed and it needs to be rebuilt, and for convenience
so it can be distributed with the release tar.gz will be preferred.
for hints on how to get that look at the Makefiles in the bios or vgabios top
level directories and the top level Makefile
> BTW, current ia64 binary has 2M size, is it OK to upload it to
> kvm-source tree ?
if you are talking about the binary only, EFI BIOS from Intel, then it could
be problematic (because of the free software guidelines of some distributions)
and of course will need to have also some sort of README file clearly
specifying that the license allows for re-distribution and can be used at least
together with kvm (like the ELPIN vga bios was licensed for BOCHS)
IMHO is probably better to use only the GPL version with sources and
distribute that with kvm source packages and let the users or distributions
to manage the distribution/installation of BLOBs otherwise as that keeps the
lawyers from distracting us from the interesting technical issues.
Carlo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-02 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 4:44 vgabios and other guest related firmware Carlo Marcelo Arenas Belon
2008-01-02 8:14 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCBB773B-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-02 9:30 ` Carlo Marcelo Arenas Belon [this message]
2008-01-02 9:36 ` Avi Kivity
[not found] ` <477B5B2F.7080304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-02 9:46 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCBB77B5-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-02 9:52 ` Avi Kivity
[not found] ` <477B5EC8.4060101-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-02 9:57 ` Zhang, Xiantao
2008-01-02 10:29 ` Carlo Marcelo Arenas Belon
2008-01-02 9:54 ` Zhang, Xiantao
2008-01-02 9:29 ` Avi Kivity
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=20080102093039.GC8605@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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