From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Antonino Daplas <adaplas@pol.net>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: LCD scaling type
Date: 11 Jan 2003 10:47:49 +0100 [thread overview]
Message-ID: <1042278469.541.27.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <1042268184.932.165.camel@localhost.localdomain>
On Sat, 2003-01-11 at 07:58, Antonino Daplas wrote:
> On Sat, 2003-01-11 at 03:42, Benjamin Herrenschmidt wrote:
> I second to this. It's useful to have an extra field in
> fb_var_screeninfo for drivers to play around. It's like an extension
> field and its main use is to expose a hardware capability which is
> uncommon enough to warrant generic support. It's meaning will vary from
> driver to driver.
I don't fully agree here. While I agree a driver specific field might
be useful, I beleive the "flags" field should have defined meaning.
> I also have a couple of things that come to mind (like switching from
> truecolor to directcolor and vice versa without rebooting). I currently
> use var->nonstd which is probably not the the right thing to do.
For this too, defined flags would make sense as other driver might want
to implement the same capability, in which case we really want all of
them to do it the same way.
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-11 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 19:42 LCD scaling type Benjamin Herrenschmidt
2003-01-11 6:58 ` Antonino Daplas
2003-01-11 9:47 ` Benjamin Herrenschmidt [this message]
2003-01-11 10:16 ` Antonino Daplas
2003-01-11 11:08 ` Benjamin Herrenschmidt
2003-01-11 11:35 ` Antonino Daplas
2003-01-11 12:08 ` Benjamin Herrenschmidt
2003-01-11 12:42 ` Antonino Daplas
2003-01-11 13:29 ` Geert Uytterhoeven
2003-01-11 13:27 ` Antonino Daplas
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=1042278469.541.27.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.