Hi all,

A few days ago I sent the message below asking about framebuffer device
documentation and explaining my specific situation. Nobody aswered and I
wonder why. If those are not questions for this list, can someone please
redirect me to the right forum?

Thanks in advance.

Cheers,

Jorge.

Jorge Marques Pelizzoni escreveu:

Hi, all!

I am considering implementing a frame buffer device for a mobile platform
(LPC2400 on uCLinux) that, as far as I can tell, seems to lack one. Well,
I am a newbie to all things frame buffer-related (though familiar with
kernel/device module implementation) and would most appreciate it if you
could answer the following questions:

1 - are there documents specifying frame buffer devices and how
applications are expected to handle them (in short, their API)?

2 - my CPU cannot address "real" VRAM directly, all control being carried
out by means of a parallel interface. I gathered that an fb user is
expected to write to (virtual) VRAM directly via a pointer provided by the
driver and never notifies the driver of changes. Have you seen such a
set-up before and do you think these requirements can be reconciled? The
only way round this I can currently see is making the driver periodically
check the virtual VRAM for changes and transmit only changed parts. All in
all, a costly operation, as everything must be carried out by the same
CPU. Could whatever is used to implement mmap be called into play (without
whatever is used to implement msync)?

Thank you very much in advance.

Cheers,

Jorge M. Pelizzoni.

Jorge M. Pelizzoni
ICMC - Universidade de São Paulo

call me at http://www.jaxtr.com/jpeliz


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/