[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification

From: Robert Millan
Subject: Re: [PATCH 2/2] "auto" keyword in gfxmode and gfxpayload specification
Date: Sun, 23 Aug 2009 12:32:54 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

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<address@hidden> 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

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."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]