From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification
Date: Sun, 23 Aug 2009 12:32:54 +0200 [thread overview]
Message-ID: <20090823103254.GD4130@thorin> (raw)
In-Reply-To: <d7ead6de0908210557x2c15ed3dm725e36fec5d28943@mail.gmail.com>
On Fri, Aug 21, 2009 at 02:57:45PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Mon, Aug 17, 2009 at 3:49 PM, Robert Millan<rmh@aybabtu.com> wrote:
> >
> >
> > Please could you include a description on what this does?
> >
> when gfxmode=auto the driver is allowed to pick best mode in its
> opinion among the modes appropriate for the task. This is needed
> because
> 1) drivers may be limited to only few modes and it may happen that
> none of supported modes is in usual list of modes to be checked.
> 2) driver may know more about connected peripherics and e.g. prefer
> 1280x800 if it's native resolution of flat panel.
Ah, I see. Yeah, we really should contemplate into detecting native
resolutions.
But is there any reason we don't want this behaviour when gfxmode was
not set? If we can avoid an additional keyword, what we do fits better
with what the user would expect.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-23 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 18:51 [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification Vladimir 'phcoder' Serbinenko
2009-08-17 13:49 ` Robert Millan
2009-08-21 12:57 ` Vladimir 'phcoder' Serbinenko
2009-08-23 10:32 ` Robert Millan [this message]
2009-08-23 11:01 ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:42 ` Robert Millan
2009-08-23 22:49 ` Vladimir 'phcoder' Serbinenko
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=20090823103254.GD4130@thorin \
--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.