From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: seabios <seabios@seabios.org>,
Qemu Development List <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] seavgabios resolutions, win8
Date: Fri, 29 Nov 2013 16:23:43 +0100 [thread overview]
Message-ID: <1385738623.23450.35.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <5298ABB3.80501@msgid.tls.msk.ru>
Hi,
> + { 0x18d, { MM_DIRECT, 1920, 1080, 16, 8, 16, SEG_GRAPH } },
> + { 0x18e, { MM_DIRECT, 1920, 1080, 24, 8, 16, SEG_GRAPH } },
> + { 0x18f, { MM_DIRECT, 1920, 1080, 32, 8, 16, SEG_GRAPH } },
> I'm not sure I understand how list of modes is maintained/used in
> seavgabios. The above patch at least allows one of the very common
> modes to be selected in windows clients.
Just get-send-email a proper patch to the seabios list.
> And while at it, there's another bugreport against vgabios package in
> Debian, see http://bugs.debian.org/685097 . It looks like windows8
> isn't happy with vgabios-provided modes and does not let to change
> resolution at all, sticking at 1024x768. That bugreport points to
> a patchset, http://lists.xen.org/archives/html/xen-devel/2012-05/msg00260.html
> (this is just one patch from it), which has been applied to xen copy
> of vgabios to solve exactly this issue with win8, and reportedly it
> works there. It looks like something similar should be done in
> seavgabios too, since with it, win8 guest is also stuck at the same
> resolution.
Hmm, last time I tried resolution switching in win8 worked just fine
with seavgabios. Can you double-check?
cheers,
Gerd
next prev parent reply other threads:[~2013-11-29 15:24 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 [this message]
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
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=1385738623.23450.35.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=mjt@tls.msk.ru \
--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 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).