nanogui: More...Porting to a custom video device
Subject:
Re: [nanogui] More...Porting to a custom video device
From:
"Greg Haerr" ####@####.####
Date:
24 May 2001 02:04:37 -0000
Message-Id: <060d01c0e3f4$7188f3e0$3aba46a6@xmission.com>
: What do you think about configuring MicroWindows to write to a virtual frame
buffer (kernel option). Then, if we understand the data structure of the
resulting image, we should be able to read pixel data from the virtual frame
buffer and send it on out to our custom display hardware.
: Do you know of any problems setting up MicroWindows for use with a virtual
frame buffer?
Microwindows regularly writes to a memory-mapped area that is usually
the real framebuffer, but of course could just be malloc'd memory. The
data structures supported are 1,2,4,8,16,24 and 32bpp. Writing to
a virtual framebuffer is exactly how "offscreen pixmaps" are supported.
It would very easy to modify microwin/src/drivers/scr_fb.c and change
it to malloc() memory for the "physical" framebuffer.
Regards,
Greg
