linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Correia Villa Real <lucasvr@gobolinux.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Screen Refresh
Date: Wed, 5 May 2004 10:47:00 -0300	[thread overview]
Message-ID: <200405051047.00127.lucasvr@gobolinux.org> (raw)

Hi,

I'm writing a device driver for a monochrome LCD display managed by a 
controller that will be plugged into the CPU through a SPI, that is, I cannot 
directly memory-map it's address, since the communication will be done via 
a serial interface.

I've seen good chunks of code tonight (fbcon.c, fbmem.c and fbcon_mfb.c), but 
an unique question still remains: I didn't see anywhere *how* the buffer is 
updated to the video card. As far I could see on others drivers that I've 
read, they are doing that by memory mapping the video card's memory, and 
hence any write done into the buffer will be automagically reflected on the 
screen.

On my case I probably won't be able to memory map it's video memory. So, is 
there a way to get notified (at driver level) when some write is going to 
happen? Or should I just install a timer and use some kind of 
double-buffering scheme to verify if changes happened?

Many thanks in advance,
Lucas


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

             reply	other threads:[~2004-05-05 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05 13:47 Lucas Correia Villa Real [this message]
2004-05-05 14:02 ` Screen Refresh Jan-Benedict Glaw
2004-05-05 15:46   ` Lucas Correia Villa Real
2004-05-15 13:58 ` [ PATCH-LINK ] fb accel capabilities - take 2 David Eger

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=200405051047.00127.lucasvr@gobolinux.org \
    --to=lucasvr@gobolinux.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).