From: Paulo Marques <pmarques@grupopie.com>
To: Franck <vagabon.xyz@gmail.com>
Cc: Miguel Ojeda <maxextreme@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support
Date: Tue, 31 Oct 2006 14:54:45 +0000 [thread overview]
Message-ID: <454763B5.1050204@grupopie.com> (raw)
In-Reply-To: <45470513.4070507@innova-card.com>
Franck Bui-Huu wrote:
> Paulo Marques wrote:
>> Franck Bui-Huu wrote:
>>> An application might want to display quickly a set of images, not for
>>> doing animations but rather displaying 'fake' greyscale images.
>>
>> To do "fake" greyscale you would need to synchronize with the actual
>> refresh of the controller or you will have very ugly aliasing artifacts.
>>
>> Since there is no hardware interface to know when the controller is
>> refreshing, I don't think this is one viable usage scenario.
>
> eh ?? Did you read my email before ? That was the point I was trying
> to raise... and starting the refresh stuff _only_ when the device is
> mmaped seems to me a good trade off.
I think we are violently agreeing about the optimal way of doing things.
But maybe I didn't explain my point about the "fake" greyscale in the
best way, though.
There are two distinct "refresh"'s involved here: one is when the driver
writes its software buffer into the display internal memory using the
parallel port interface.
The other is when the actual display controller refresh that goes
through all the common lines, etc., using the values on its internal
memory to update the segment voltages.
The problem is that there is no way to know about the internal refresh
that the controller does. So if you update its memory very frequently to
try to produce a "fake" greyscale image, your updates will alias with
the refresh rate of the actual display controller and you will see all
sorts of strange effects on the display.
> Aynywas it seems that the discusion about the design is closed and
> won't lead to interesting things...
Only because we're mostly in agreement about what should be done ;)
But if you have other interesting things to suggest, I haven't seen
Miguel reject any suggestions by other developers, yet (very much on the
contrary, to be honest).
--
Paulo Marques
Software Development Department - Grupo PIE, S.A.
Phone: +351 252 290600, Fax: +351 252 290601
Web: www.grupopie.com
"The face of a child can say it all, especially the
mouth part of the face."
next prev parent reply other threads:[~2006-10-31 14:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 2:32 [PATCH 2.6.19-rc1 full] drivers: add LCD support Miguel Ojeda Sandonis
2006-10-13 12:43 ` Paulo Marques
2006-10-18 14:55 ` Franck Bui-Huu
2006-10-23 8:41 ` Franck Bui-Huu
2006-10-23 12:56 ` Miguel Ojeda
2006-10-23 15:35 ` Franck Bui-Huu
2006-10-23 16:21 ` Miguel Ojeda
2006-10-23 16:51 ` Franck Bui-Huu
2006-10-26 14:45 ` Miguel Ojeda
2006-10-27 20:08 ` Franck Bui-Huu
2006-10-27 20:38 ` Miguel Ojeda
2006-10-30 8:43 ` Franck Bui-Huu
2006-10-30 13:35 ` Miguel Ojeda
2006-10-23 16:05 ` Franck Bui-Huu
2006-10-23 16:08 ` Miguel Ojeda
2006-10-23 17:15 ` Franck Bui-Huu
2006-10-26 14:55 ` Miguel Ojeda
2006-10-27 20:03 ` Franck Bui-Huu
2006-10-27 20:25 ` Miguel Ojeda
2006-10-30 9:26 ` Franck Bui-Huu
2006-10-30 13:22 ` Paulo Marques
2006-10-30 14:11 ` Miguel Ojeda
2006-10-30 15:21 ` Paulo Marques
2006-10-30 17:32 ` Miguel Ojeda
2006-10-30 20:45 ` Paulo Marques
2006-10-31 8:10 ` Franck Bui-Huu
2006-10-31 14:12 ` Miguel Ojeda
2006-10-31 14:54 ` Paulo Marques [this message]
2006-10-30 13:47 ` 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=454763B5.1050204@grupopie.com \
--to=pmarques@grupopie.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxextreme@gmail.com \
--cc=vagabon.xyz@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