From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Alexander van Heukelum" <heukelum@fastmail.fm>
Cc: "Randy Dunlap" <rdunlap@xenotime.net>,
akpm@osdl.org, "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
linux-kernel@vger.kernel.org, Valdis.Kletnieks@vt.edu
Subject: Re: [PATCH 2.6.18 V7] drivers: add lcd display support
Date: Sun, 1 Oct 2006 19:52:35 +0200 [thread overview]
Message-ID: <653402b90610011052o24574dd5o4cb911f118e8adfd@mail.gmail.com> (raw)
In-Reply-To: <1159723673.14141.272274719@webmail.messagingengine.com>
On 10/1/06, Alexander van Heukelum <heukelum@fastmail.fm> wrote:
> I think there is a problem with the name anyhow. Would you use the
> LCD(d)isplay driver for an OLED screen?
>
> How about auxiliary display or AUXdisplay?
>
> Alexander
>
Mi first guess was drivers/display/, to put driver about
extra-displays, not only LCDs.
But people thought it can confuse users, so I chose to add "LCD" to be
more specific.
And no, it is not an organic screen. It is for a cfag12864b LCD
(Liquid Crystal Display):
http://www.crystalfontz.com/products/12864b/index.html
next prev parent reply other threads:[~2006-10-01 17:52 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 [this message]
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
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=653402b90610011052o24574dd5o4cb911f118e8adfd@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=heukelum@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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®