nanogui: open("/dev/fb0") by two programs
Subject:
Re: [nanogui] open("/dev/fb0") by two programs
From:
"Greg Haerr" ####@####.####
Date:
12 Jul 2001 16:58:57 -0000
Message-Id: <0c1301c10af5$3b3f1620$6817dbd0@censoft.com>
: The best solution is to have the graphics engine provide a memory window
so
: the client can write directly to the framebuffer. Hopefully a future
: version of Microwindows will have this ability.
It isn't bad to have the client open framebuffer at the same time
as the Nano-X server, providing it's managed properly. This is
the technique that I use in pre8 that allows super-fast MPEG
video drawing using the "client-side direct framebuffer mapping."
I have added some a new client library call, as well as enhanced
some structure members so that the client can know exactly what the
framebuffer looks like without writing a bunch of non-portable
code.
WRT window synchronization, I am working on a semaphore
technique that will allow direct client-side framebuffer programs
to receive events when the framebuffer is moved.
: It also looks like they are going to disallow multiple open's of the
:: same fb in 2.5. See the thread in linux-fbdev
: http://sourceforge.net/mail/?group_id=908
This is bad news. We need the dual-open capability in order to
make fast video work. Alan - what do you think about this,
is there another preferred method?
Regards,
Greg
:
: Jordan
:
: On Wednesday 11 July 2001 23:35, ####@####.#### mentioned:
: > Hello all,
: > Just a quick question, I am writing an mpeg player for nano-X, and
: > I want to be able to dump the video straight to the framebuffer. I was
just
: > wondering if it is bad to have the nano-X server have the framebuffer
: > device open at the same time as my application?
: >
: > Peter Hartshorn
: > ####@####.####
: >
: >
: > ---------------------------------------------------------------------
: > To unsubscribe, e-mail: ####@####.####
: > For additional commands, e-mail: ####@####.####
:
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: ####@####.####
: For additional commands, e-mail: ####@####.####
:
