From: Michael Tokarev <mjt@tls.msk.ru>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>, QEMU Devel list <qemu-devel@nongnu.org>
Subject: Re: extended vga modes?
Date: Mon, 08 Mar 2010 14:07:43 +0300 [thread overview]
Message-ID: <4B94DA7F.3010705@msgid.tls.msk.ru> (raw)
In-Reply-To: <4B94D7A6.4040008@redhat.com>
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?
There were another patch mentioned recently when I asked for
bios sources origin a few days ago which probably should be
applied as well...
[]
>> Should vgabios in qemu include that patch?
>> See also: https://bugzilla.redhat.com/show_bug.cgi?id=501545
>
> Looks like Fedora was using the upstream vgabios for a while, not the
> version in qemu-kvm.git.
Yes they are still using upstream but they also
applied the patches missing in there.
Thank you for the prompt response. Now I think all
confusion is cleared.
/mjt
next prev parent reply other threads:[~2010-03-08 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 10:20 extended vga modes? Michael Tokarev
2010-03-08 10:55 ` Avi Kivity
2010-03-08 11:07 ` Michael Tokarev [this message]
2010-03-08 11:11 ` Avi Kivity
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=4B94DA7F.3010705@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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