From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: gfxterm and vesa
Date: Sun, 13 May 2007 01:00:26 +0200 [thread overview]
Message-ID: <20070512230026.GA25257@aragorn> (raw)
In-Reply-To: <464485FB.2090406@nic.fi>
On Fri, May 11, 2007 at 06:04:27PM +0300, Vesa Jääskeläinen wrote:
>
> Video mode setup function tries to use all available video drivers to
> initialize video mode. It uses first it founds working. So if someone
> writes VGA driver then you can add it to queue and if VBE2+ is not
> available then it would try next driver, in this case it would be VGA
> driver.
>
> You can specify video mode to be 800x600 without color depth so it will
> use most colorful mode it finds. But if first adapter has 800x600x16 and
> second would have 800x600x32 then it would take first as there was valid
> mode.
>
> Other option would be to probe for modes and then select one. But this
> should be in script or in custom module code. Or gfxmode would be
> extended to allow multiple selections like 1024x768;800x600;640x480.
> Also there are starting to be lots of wide screen LCD's that should be
> somehow supported too. I think that Video API do not have any limitation
> on this regard.
Which do you think should be the default (at least in the short term)?
Note: the default gfxmode definition set by update-grub is defined in official
GRUB (see grub2/util/grub.d/00_header.in).
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-05-12 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070511155339.85f69598.jonny@csc.jp>
[not found] ` <87ps578rug.fsf@lab.ossystems.com.br>
2007-05-11 14:07 ` gfxterm and vesa Robert Millan
2007-05-11 15:04 ` Vesa Jääskeläinen
2007-05-12 23:00 ` Robert Millan [this message]
2007-05-15 20:23 ` Yoshinori K. Okuji
2007-05-16 15:37 ` Robert Millan
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=20070512230026.GA25257@aragorn \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.