linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Schoenebeck <cuse@users.sourceforge.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: basic FB development questions
Date: Wed, 23 Apr 2008 00:50:30 +0200	[thread overview]
Message-ID: <200804230050.31349.cuse@users.sourceforge.net> (raw)

Hi!

I'm currently writing a Linux FB driver for an USB LCD. I've written Linux 
drivers before, but not a FB driver yet, so I hope you can help me with some 
basic FB development questions.

First of all, AFAIK most FB drivers are based upon memory mapped IO, right? 
But in my case the graphics are forwarded via calls of Linux's USB subsystem. 
Which FB approach would suggest in this case? Something like the virtual 
framebuffer driver with some kind of static allocated buffer? If yes, what 
kind of function would I have to implement to trigger the screen sync between 
that modified buffer and the hardware (that is sending the buffer's data via 
USB to the device)? Or should I implement mmap? I mean: I know everything 
about the USB side to recognize the device and sending data etc., I just 
don't know how to establish a FB callback or something to "flush" the 
suggested graphics buffer.

In the "fb_var_screeninfo" struct there are the following members which I'm 
not sure about their precise purpose:

	* "pixclock": is that the average speed (in ps) with which one pixel of the
	  screen is changed?

	* "left_margin", "right_margin", "upper_margin", "lower_margin":
	  I'm confused about these members, I first thought that would be some kind
	  of reference margin (in pixels), but the header file says those are timing
	  values?

	* "hsync_len", "vsync_len":
	  what's that exactly and is it a timing or pixel value?

If there are basic docs about FB terms etc, please let me know!

Thanks for any help!

CU
Christian

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

             reply	other threads:[~2008-04-22 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 22:50 Christian Schoenebeck [this message]
2008-04-23  9:01 ` basic FB development questions Geert Uytterhoeven
2008-04-23 11:41   ` Christian Schoenebeck

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=200804230050.31349.cuse@users.sourceforge.net \
    --to=cuse@users.sourceforge.net \
    --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).