From: "alain volmat" <avolmat@yahoo.fr>
To: Antonino Daplas <adaplas@pol.net>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Framebuffer with banked memory
Date: Thu, 31 Oct 2002 05:02:28 +0100 (CET) [thread overview]
Message-ID: <20021031040228.12091.qmail@web14205.mail.yahoo.com> (raw)
In-Reply-To: <1036024422.643.24.camel@daplas>
> The safest solution is to create custom fb_write?
> and fb_read? routines.
> Maybe James will add these hooks for hardware like
> yours.
> Then disallow mmap's except probably for the MMIO
> regions.
>
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.
> PS: What's your hardware?
Well actually it's a custom chip.
Alain
--- Antonino Daplas <adaplas@pol.net> a écrit : > On
Wed, 2002-10-30 at 18:49, alain volmat wrote:
> > Hi,
> >
> > As I said the video card I am now writing a
> > framebuffer for, doesn't have linear memory, which
> > means that I can only access a small part of the
> > memory at a time and then set offset registers in
> > order to access another part of the memory.
> >
> > I would like to know if there is such case in
> current
> > framebuffer drivers ?? If so, what is the common
> > solution to do that ??
> None in the current drivers.
>
> >
> > In fact the problem remains in the case of mmap
> (which
> > is the most common ;( of course), since the memory
> > seams to be accessed directly by pointer, there
> might
> > be no wait to detect if we need to set or not an
> > offset. In case of fb_read fb_write, it is
> possible to
> > do that before the actual write at the end (even
> if it
> > is not sooo beautiful ... ).
> The safest solution is to create custom fb_write?
> and fb_read? routines.
> Maybe James will add these hooks for hardware like
> yours.
> Then disallow mmap's except probably for the MMIO
> regions.
>
> Creating a bank-switching mechanism, besides
> entailing a lot of work, is
> not entirely safe.
>
> Tony
>
> PS: What's your hardware?
>
>
>
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
-------------------------------------------------------
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 parent reply other threads:[~2002-10-31 4:02 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 ` alain volmat [this message]
2002-10-31 11:04 ` Framebuffer with banked memory Antonino Daplas
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=20021031040228.12091.qmail@web14205.mail.yahoo.com \
--to=avolmat@yahoo.fr \
--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).