All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios <seabios@seabios.org>, Gerd Hoffmann <kraxel@redhat.com>,
	Qemu Development List <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] seavgabios resolutions, win8
Date: Fri, 29 Nov 2013 23:05:37 +0400	[thread overview]
Message-ID: <5298E581.9040305@msgid.tls.msk.ru> (raw)
In-Reply-To: <20131129185747.GA10465@morn.localdomain>

29.11.2013 22:57, Kevin O'Connor wrote:
> On Fri, Nov 29, 2013 at 06:58:59PM +0400, Michael Tokarev wrote:
>> I tried switching from plex/bochs vgabios to seavgabios,
>> and made this switch for qemu-1.7 package in debian, at
>> least to see how it goes.
>>
>> And almost immediately got a complain that with new qemu
>> (which uses seavgabios not vgabios), windows VMs don't
>> support 1920x1080 resolutions anymore.
> 
> Where do you get your "lgpl vgabios" from?  The standard QEMU repo (
> git://git.qemu.org/vgabios.git ) doesn't have these modes either.

http://cvs.savannah.gnu.org/viewvc/vgabios/vbetables-gen.c?revision=1.6&root=vgabios&view=markup

It is the "upstream" vgabios repository (v. 0.7a).  Modes 0x19[012].

qemu version is based on upstream version 0.6c.

The original complain comes from one of debian users, and in debian
we always used upstream version.

The patch which added some of these modes:

http://cvs.savannah.gnu.org/viewvc/vgabios/vbetables-gen.c?root=vgabios&r1=1.5&r2=1.6

I'm preparing a patch to add remaining bits from there.

Thanks,

/mjt

      reply	other threads:[~2013-11-29 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 14:58 [Qemu-devel] seavgabios resolutions, win8 Michael Tokarev
2013-11-29 15:23 ` Gerd Hoffmann
2013-11-29 15:59   ` Michael Tokarev
2013-11-29 16:17     ` Michael Tokarev
2013-11-29 18:48     ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2013-11-29 18:57 ` [Qemu-devel] " Kevin O'Connor
2013-11-29 19:05   ` Michael Tokarev [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=5298E581.9040305@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=Qemu-devel@nongnu.org \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=seabios@seabios.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 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.