From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Richard Wolf <rwolf@cardaccess.com.au>
Subject: Re: Driver for Sharp LH155BA
Date: Tue, 01 Aug 2006 09:18:19 +0800 [thread overview]
Message-ID: <44CEABDB.3040702@gmail.com> (raw)
In-Reply-To: <170385E48B041543AC99CCD09E325AD1952BB9@mail.rogermanagement.com.au>
Richard Wolf wrote:
>
> Presumably if I take the shadow buffer route then I could maintain _two_
> shadow buffers. This would allow me to detect whether the user accessible
> buffer had been changed and update the display only when necessary.
Yes, that will work too.
Tony
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-08-01 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 0:59 Driver for Sharp LH155BA Richard Wolf
2006-08-01 1:18 ` Antonino A. Daplas [this message]
2006-08-01 6:58 ` Markus Schorer
-- strict thread matches above, loose matches on Subject: below --
2006-08-02 1:00 Richard Wolf
2006-08-01 0:31 Richard Wolf
2006-08-01 0:35 ` Antonino A. Daplas
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=44CEABDB.3040702@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rwolf@cardaccess.com.au \
/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;
as well as URLs for NNTP newsgroup(s).