From: Alex Bennee <kernel-hacker@bennee.com>
To: Antonino Daplas <adaplas@pol.net>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Advice sought on approach.
Date: 05 Mar 2003 14:40:01 +0000 [thread overview]
Message-ID: <1046875200.10894.216.camel@cambridge.braddahead> (raw)
In-Reply-To: <1046870757.1229.94.camel@localhost.localdomain>
On Wed, 2003-03-05 at 13:26, Antonino Daplas wrote:
> On Wed, 2003-03-05 at 20:37, Alex Bennee wrote:
> > Having read the fb-dev docs on www.linux-fbdev.org I'm a little confused
> > as to what actually puts data into the framebuffer. Most of the
> > framebuffer drivers just seem to deal with resolution and colourmap
> > settings. Is this a case of having to re-implement the fbcon drivers as
> > well to get what I want?
> The pixels placed to the framebuffer are all done in the fbcon-cfb*.c
> modules (if you use the generic functions). This is for standard
> character drawing. The logo is drawn indepently (fbcon_show_logo in
> fbcon.c). User applications write directly to the framebuffer via the
> mmap() function.
I think I understand now. When the fb_set_disp function is called I fill
in the display struction with the console display operations. I've got
two choices now:
1. Create a new fbcon_cfb16 file which notes the changed areas before
calling the generic function.
2. Patch the current fbcon_cfb16 (with a CONFIG option) to add the
change tracking facility in a more generic way.
I guess the question is is it worth doing 2 as a potential upstream
patch? Or is this sort of thing so specialised I should just keep it all
packed in my own fb driver?
I guess I can't easily implement user access via mmap without uploading
the entire screen, which I'm not intending to do anyway because all I
really need is the console support - at least for now.
> > Are there any examples of drivers that have a similar architecture that
> > would be worth looking at? I've had a look at the vfb.c code but again
> > that seems too simplistic compared to what I'll need.
>
> Search the archives for SED1335. The author implemented a shadowed
> virtual framebuffer using system memory. The contents of the virtual
> framebuffer are written to the data port periodically via a timer
> function.
I couldn't find anything in the mail archives but after some careful
googling I found this site (posted for reference):
ftp://ssv-embedded.de/ssv/products/trm916/sample/x86/linux/fbdev which
seems to be the one your refering to.
Thanks for the pointer, seeing the code made things a lot clearer :-)
--
Alex, homepage: http://www.bennee.com/~alex/
Bennett's Laws of Horticulture:
(1) Houses are for people to live in.
(2) Gardens are for plants to live in.
(3) There is no such thing as a houseplant.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
next prev parent reply other threads:[~2003-03-05 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 12:37 Advice sought on approach Alex Bennee
2003-03-05 13:26 ` Antonino Daplas
2003-03-05 14:40 ` Alex Bennee [this message]
2003-03-05 14:44 ` Geert Uytterhoeven
2003-03-05 15:36 ` Antonino 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=1046875200.10894.216.camel@cambridge.braddahead \
--to=kernel-hacker@bennee.com \
--cc=adaplas@pol.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).