From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: vgabios plans ( Re: [PATCH 1/5] Makefile cleanup)
Date: Thu, 20 May 2010 08:04:50 -0500 [thread overview]
Message-ID: <4BF53372.3070401@codemonkey.ws> (raw)
In-Reply-To: <4BF5319C.2030108@redhat.com>
On 05/20/2010 07:57 AM, Gerd Hoffmann wrote:
> On 05/07/10 12:09, Gerd Hoffmann wrote:
>> Use a single rule for building bios binaries.
>> Use target specific variables to set compile flags.
>>
>> This makes it more obvious what the differences between the versions
>> are. It also makes it easier to add new bios binaries with slightly
>> different settings.
>
> Hmm. No response for weeks from vgabios folks on this patch series.
> How to go forward best with vgabios bits? Just upgrade
> http://git.qemu.org/vgabios.git/ to 0.6c, then apply patches there?
Yeah, I think the long term goal should be to move to SeaBIOS's vgabios
fork but for now, I guess we'll have to do it.
Regards,
Anthony Liguori
> cheers,
> Gerd
next prev parent reply other threads:[~2010-05-20 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 10:09 [Qemu-devel] [PATCH 1/5] Makefile cleanup Gerd Hoffmann
2010-05-07 10:09 ` [Qemu-devel] [PATCH 2/5] Add defines for PCI IDs Gerd Hoffmann
2010-05-07 15:32 ` Blue Swirl
2010-05-10 7:51 ` Gerd Hoffmann
2010-05-07 10:09 ` [Qemu-devel] [PATCH 3/5] Add qemu stdvga pci bios Gerd Hoffmann
2010-05-07 10:09 ` [Qemu-devel] [PATCH 4/5] update pci_get_lfb_addr for vmware vga Gerd Hoffmann
2010-05-07 10:09 ` [Qemu-devel] [PATCH 5/5] Add qemu vmware vga pci bios Gerd Hoffmann
2010-05-07 14:38 ` [Qemu-devel] [PATCH 1/5] Makefile cleanup Isaku Yamahata
2010-05-20 12:57 ` [Qemu-devel] vgabios plans ( Re: [PATCH 1/5] Makefile cleanup) Gerd Hoffmann
2010-05-20 13:04 ` Anthony Liguori [this message]
2010-05-21 13:29 ` [Qemu-devel] " Gerd Hoffmann
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=4BF53372.3070401@codemonkey.ws \
--to=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).