From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Devel list <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: extended vga modes?
Date: Mon, 08 Mar 2010 13:11:29 +0200 [thread overview]
Message-ID: <4B94DB61.6020505@redhat.com> (raw)
In-Reply-To: <4B94DA7F.3010705@msgid.tls.msk.ru>
On 03/08/2010 01:07 PM, Michael Tokarev wrote:
> Avi Kivity wrote:
> []
>
>>> In short, when vgabios were dropped from qemu-kvm
>>> (for whatever yet unknown reason),
>>>
>> What do you mean? qemu-kvm still carries a local vgabios (see
>> kvm/vgabios in qemu-kvm.git).
>>
> Oh my. So we all overlooked it. I asked you several times
> about the bios sources, in 0.12 seabios were supposed to be
> in roms/seabios (which is still empty in the release), and
> I thought vgabios should be in roms/vgabios (which is empty
> too), and concluded it were dropped from qemu-kvm tarball.
> But you're right, and I by mistake take vgabios sources from
> upstream qemu when building Debian package, instead of using
> the old'good sources from kvm/vgabios. What a mess!... :(
>
> And it looks like that it's time to remove at least parts of
> this mess, don't you think? How about pushing the vgabios
> changes to qemu and moving it to the same place where it is
> in qemu? Does it make sense?
>
We can't push the changes to qemu since qemu.git doesn't have a vgabios
fork. We might push the changes upstream. Best of all if the seabios
thing repeats itself with vgabios so we have maintainable and maintained
vga firmware.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-08 11:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 10:20 [Qemu-devel] extended vga modes? Michael Tokarev
2010-03-08 10:55 ` [Qemu-devel] " Avi Kivity
2010-03-08 11:07 ` Michael Tokarev
2010-03-08 11:11 ` Avi Kivity [this message]
2010-03-10 10:21 ` Roy Tam
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=4B94DB61.6020505@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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).