From: Randy Dunlap <rdunlap@xenotime.net>
To: "Miguel Ojeda" <maxextreme@gmail.com>
Cc: andrew.j.wade@gmail.com, akpm@osdl.org,
"Stefan Richter" <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 V7] drivers: add lcd display support
Date: Tue, 3 Oct 2006 08:29:50 -0700 [thread overview]
Message-ID: <20061003082950.25a0e898.rdunlap@xenotime.net> (raw)
In-Reply-To: <653402b90610030555h2536b04bs3603d95635b93ca7@mail.gmail.com>
On Tue, 3 Oct 2006 14:55:07 +0200 Miguel Ojeda wrote:
> On 10/3/06, Andrew James Wade <andrew.j.wade@gmail.com> wrote:
> >
> > I'm afraid not; it looks like my suggestion "LCD display" grates on
> > people's ears. Simply calling the device an "LCD" is probably the
> > best bet, and "LCD screen" would be better than "LCD monitor". Screens
> > can be any size, it's a fairly generic term.
> >
> > The class name and directory name should probably include the word
> > "display", but I don't know what the other part should be. What sort
> > of displays should be included in this category, and what sort
> > shouldn't?
> >
> > Andrew Wade
> >
>
> My first idea was call it "display", for small/medium screens of any
> kind (LCD, OLED, FED, NED... whatever). I named it "drivers/display/",
> so anyone who create a driver for a display or display controller can
> put it there (creating a separator for its own category at Kconfig),
> as there aren't so many of them for now.
>
> But people said "display" could be so generic and cause confusion with
> usual video drivers, so I renamed it to "drivers/lcddisplay/", as it
> is more expressive (however when someone will create a OLED driver
> will have to create a new folder...).
>
> I would like to put any kind of display driver there (LCD, OLED...)
> not just LCDs and name it "drivers/display". I think people won't
> confuse them with VESA... as there aren't drivers for "screens", just
> for video cards (logically). But some people don't agree.
I liked the "auxdisplay" suggestion, FWIW.
---
~Randy
next prev parent reply other threads:[~2006-10-03 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 23:24 Miguel Ojeda Sandonis
2006-10-01 12:53 ` Miguel Ojeda
2006-10-01 13:51 ` Stefan Richter
2006-10-01 14:25 ` Miguel Ojeda
2006-10-01 16:48 ` Stefan Richter
2006-10-01 17:58 ` Miguel Ojeda
2008-04-28 23:36 ` monitordelcd
2006-10-01 16:05 ` Valdis.Kletnieks
2006-10-01 16:17 ` Andreas Schwab
2006-10-01 17:33 ` Valdis.Kletnieks
2006-10-01 16:43 ` Randy Dunlap
2006-10-01 17:27 ` Alexander van Heukelum
2006-10-01 17:52 ` Miguel Ojeda
2006-10-01 18:25 ` Alexander van Heukelum
2006-10-01 16:53 ` Stefan Richter
2006-10-02 18:49 ` Andrew James Wade
2006-10-02 21:40 ` Miguel Ojeda
2006-10-03 0:06 ` Andrew James Wade
2006-10-03 12:55 ` Miguel Ojeda
2006-10-03 15:29 ` Randy Dunlap [this message]
2006-10-02 22:06 ` Alan Cox
2006-10-02 21:45 ` Miguel Ojeda
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=20061003082950.25a0e898.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=andrew.j.wade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®