From: Pavel Machek <pavel@ucw.cz>
To: Miguel Ojeda <maxextreme@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 V9] drivers: add LCD support
Date: Tue, 10 Oct 2006 12:37:23 +0200 [thread overview]
Message-ID: <20061010103723.GC31598@elf.ucw.cz> (raw)
In-Reply-To: <653402b90610081545n51cdfbcej469990279f6d018c@mail.gmail.com>
Hi!
> >What is advantage of /dev/cfag12864bX over /dev/fbcfag12864b ?
> >
> >(And I guess you should invent better name... /dev/fbaux0?)
> >
> >
> >I do not think we need a Kconfig option, and I do not think we need
> >/dev/cfag12864bX . Just use /dev/fbaux0, always.
> >
>
> One is the pure device, the other one is the framebuffer device. I
> think having both is better than just one. There is no advantage, they
> are different.
No, having two different interfaces when one would be enough is
stupid.
Face it... you are writing driver for framebuffer. (Small, slow,
black&white, but still framebuffer).
> Maybe someone doesn't need any of the framebuffer advantages and just
> wants to write to it directly, for better performance, for example:
> The LCD needs to change 8 pixels (1 byte) every write, if you modify a
> single pixel at the framebuffer device you will write more times than
> you need for the same result (right? I'm not sure of this); the LCD
> is
Wrong, I think you only need to change 1bit, so framebuffer device
actually performs better.
> >I do not think it is suitable for -rc at this point, and it does not
> >have chance before 2.6.20-rc1, anyway.
>
> No? Why not? Time is not a problem, I would want to know why are you
> saying that.
Bad user<->kernel interface is good enough reason for the patch not to
be merged anywhere.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-10-10 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 0:29 [PATCH 2.6.19-rc1 V9] drivers: add LCD support Miguel Ojeda Sandonis
2006-10-08 18:24 ` Pavel Machek
2006-10-08 18:37 ` Miguel Ojeda
2006-10-08 19:12 ` Pavel Machek
[not found] ` <653402b90610081312m32fcf7ecx9929ae9dc4768c17@mail.gmail.com>
[not found] ` <20061008211550.GE4152@elf.ucw.cz>
2006-10-08 21:36 ` Miguel Ojeda
2006-10-08 22:07 ` Pavel Machek
2006-10-08 22:45 ` Miguel Ojeda
2006-10-09 13:33 ` Stefan Richter
2006-10-09 13:56 ` Miguel Ojeda
2006-10-10 10:37 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 16:26 Miguel Ojeda Sandonis
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=20061010103723.GC31598@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
/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