Skip to contentSkip to conversation

Framebuffer with banked memory

DISCUSSION alain volmat 3 participants 4 messages Oct 31, 2002 1 message not in the archive Framebuffer layer

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 7 lines

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.

Quoted 1 line

PS: What's your hardware?

Well actually it's a custom chip.

Alain

--- Antonino Daplas <[email protected]> a écrit : > On

Quoted 33 lines · alain volmat
Quoted 9 lines

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

Quoted 2 lines

framebuffer drivers ?? If so, what is the common solution to do that ??

None in the current drivers.

Quoted 2 lines

In fact the problem remains in the case of mmap

(which

Quoted 2 lines

is the most common ;( of course), since the memory seams to be accessed directly by pointer, there

might

Quoted 2 lines

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

Quoted 1 line

do that before the actual write at the end (even

if it

Quoted 1 line

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.

Quoted 10 lines

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

#2 lore raw
Quoted 10 lines · alain volmat

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

#3 lore raw
Quoted 12 lines · alain volmat
Quoted 10 lines

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.

Quoted 2 lines

I've seen a post by James sometimes ago about adding fb_write and fb_read to info->fbops.

Correct. The next set of fbdev changes will include this plus I added fb_sync!!! Iknow this will make you happy:-)

-------------------------------------------------------
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

#4 lore raw
Quoted 12 lines · James Simmons
Quoted 12 lines · alain volmat
Quoted 10 lines

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.

Quoted 6 lines
Quoted 2 lines

I've seen a post by James sometimes ago about adding fb_write and fb_read to info->fbops.

Correct. The next set of fbdev changes will include this plus I added fb_sync!!! Iknow this will make you happy:-)

Indeed :-), not just me, but others too, I guess. Selective hardware syncs will maximize the graphics instruction pipeline.

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