[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0611150052180.13800@pentafluge.infradead.org>
Date: Wed, 15 Nov 2006 00:54:51 +0000 (GMT)
From: James Simmons <jsimmons@...radead.org>
To: Miguel Ojeda <maxextreme@...il.com>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@...ts.sourceforge.net>,
Luming Yu <Luming.yu@...el.com>,
Andrew Zabolotny <zap@...elink.ru>,
Jamey Hicks <jamey.hicks@...com>
Subject: Re: ACPI output/lcd/auxdisplay mess
> Well, we were aware of video/backlight/* (read below). Anyway,
> auxdisplay doesn't create a class; it did in first versions, but right
> now it behaves just like a framebuffer, no classes in the playground
> (maybe you read a old version?).
...
> However, auxdisplay means "auxiliary display device drivers", not _the
> display_. In such folder we can put every
> auxiliar-optional-secundary-rare display (not just LCDs, framebuffers,
> ...) who has special requirements (like parport wiring, fixed refresh
> rate, different properties...). Also, things like "set_contrast",
> "max_constrast", "set_power"... didn't seem very appropriate.
Is it a framebuffer device ? The framebuffer layer is abstracted to work
with such devices.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists