From: Antonino Daplas <adaplas@pol.net>
To: alain volmat <avolmat@yahoo.fr>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer with banked memory
Date: 31 Oct 2002 19:04:32 +0800 [thread overview]
Message-ID: <1036062186.638.23.camel@daplas> (raw)
In-Reply-To: <20021031040228.12091.qmail@web14205.mail.yahoo.com>
On Thu, 2002-10-31 at 12:02, alain volmat wrote:
>
> What about adding fb_write / fb_read function in the
> framebuffer (device dependant) driver. The same way as
> for fb_mmap. I saw that at the beginning of fb_mmap in
> fbmem.c, there is a test to see if the device driver
> contains its own fb_mmap function, if so the device
> driver fb_mmap will be used instead of the "generic"
> fb_mmap. What about doing the same thing for fb_write
> / fb_read.
>
I've seen a post by James sometimes ago about adding fb_write and
fb_read to info->fbops.
Tony
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
next prev parent reply other threads:[~2002-10-31 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1036024422.643.24.camel@daplas>
2002-10-31 4:02 ` Framebuffer with banked memory alain volmat
2002-10-31 11:04 ` Antonino Daplas [this message]
2002-10-31 21:44 ` James Simmons
2002-10-31 21:16 ` Antonino Daplas
2002-10-31 21:18 Sottek, Matthew J
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 21:09 Sottek, Matthew J
2002-10-31 21:48 ` James Simmons
2002-10-30 10:49 alain volmat
2002-10-31 0: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=1036062186.638.23.camel@daplas \
--to=adaplas@pol.net \
--cc=avolmat@yahoo.fr \
--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).