From: Anthony Liguori <anthony@codemonkey.ws>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT c34ebfd] Bring pcbios, seabios, and vgabios into the tree as git submodules. Right now,
Date: Sun, 06 Dec 2009 20:52:11 -0600 [thread overview]
Message-ID: <4B1C6DDB.7020301@codemonkey.ws> (raw)
In-Reply-To: <20091207021412.GE3670@valinux.co.jp>
Isaku Yamahata wrote:
> On Wed, Sep 30, 2009 at 08:02:08AM -0500, Anthony Liguori wrote:
>
>> Hi Isaku,
>>
>> Isaku Yamahata wrote:
>>
>>> Is there any documentation available about where those git repo are and
>>> how to compile?
>>>
>>> Fortunately I was able to find the repo
>>> in git.qemu.org by digging out the ML archive.
>>> However there should be some kind of description
>>> in pc-bios/README or somewhere else.
>>>
>>>
>> Good point, I'll work on that.
>>
>
> What happened to this?
> At this moment, there is no document which describes the official
> procedure to compile BIOSes.
> I suppose this kind of document is suitable for 0.12.0 release.
>
There's really nothing that clever about it.
$ git clone git://git.qemu.org/qemu.git
$ cd qemu
$ git submodule update --init
$ cd roms/seabios
$ make
$ cp out/bios.bin ../../pc-bios/bios.bin
The last three steps could be totally automated by the build system.
That's what I'd like to see.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-07 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909041515.n84FFwDS025473@d01av02.pok.ibm.com>
2009-09-08 7:21 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT c34ebfd] Bring pcbios, seabios, and vgabios into the tree as git submodules. Right now, Gerd Hoffmann
2009-09-08 13:08 ` Anthony Liguori
2009-09-30 2:33 ` Isaku Yamahata
2009-09-30 13:02 ` Anthony Liguori
2009-12-07 2:14 ` Isaku Yamahata
2009-12-07 2:52 ` Anthony Liguori [this message]
2009-12-07 3:19 ` Isaku Yamahata
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=4B1C6DDB.7020301@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.