nanogui: open("/dev/fb0") by two programs
Subject:
Re: [nanogui] open("/dev/fb0") by two programs
From:
Jordan Crouse ####@####.####
Date:
12 Jul 2001 14:49:07 -0000
Message-Id: <0107120849200P.08163@cosmic>
Bad is a relative term here. You're not going to core dump your kernel or
anything, but unless you are super careful, you will see synchronization
problems between the server and your application (which is then multiplied
when you toss a window manager into the mix). For example, say you have a
MPEG stream running on the framebuffer, and then you move the window for some
reason. The window may move, but the actual video image may not move with
it.
That's because the Nano-X server doesn't have any clue about the stream, so
it cannot manage it. Of course, you can always go fullscreen to avoid
these issues, but a 320x200 MPEG stream goes a tad slow sometimes.
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.
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: ####@####.####
