From: Isaku Yamahata <yamahata@valinux.co.jp>
To: Anthony Liguori <anthony@codemonkey.ws>
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: Mon, 7 Dec 2009 12:19:28 +0900 [thread overview]
Message-ID: <20091207031928.GG3670@valinux.co.jp> (raw)
In-Reply-To: <4B1C6DDB.7020301@codemonkey.ws>
On Sun, Dec 06, 2009 at 08:52:11PM -0600, Anthony Liguori wrote:
> 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.
So the repository will be moved from nongnu to git.qemu.org
even for qemu itself?
Anyway here's the patch.
>From 60c5325a84776beb0dd20581396126a0e068e707 Mon Sep 17 00:00:00 2001
From: Isaku Yamahata <yamahata@valinux.co.jp>
Date: Mon, 7 Dec 2009 12:15:25 +0900
Subject: [PATCH] pc-bios: update README to describe compile BIOSes.
Add the procedure to compile BIOSes.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
---
pc-bios/README | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/pc-bios/README b/pc-bios/README
index 3f2c978..9bf2532 100644
--- a/pc-bios/README
+++ b/pc-bios/README
@@ -26,3 +26,16 @@
virtio 1af4:1000
http://rom-o-matic.net/
+
+- To compile PC related BIOSes
+ git.qemu.org holds the repositories for BIOSes sources.
+ So you can compile BIOSes by following steps.
+
+ $ 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.
--
1.6.5.4
prev parent reply other threads:[~2009-12-07 3:19 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
2009-12-07 3:19 ` Isaku Yamahata [this message]
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=20091207031928.GG3670@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--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).