nanogui: Images resolution


Previous by date: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Rosimildo daSilva
Next by date: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Chris Johns
Previous in thread: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Rosimildo daSilva
Next in thread: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Chris Johns

Subject: RE: Images resolution
From: Alex Holden ####@####.####
Date: 28 Jan 2000 20:20:05 -0000
Message-Id: <Pine.LNX.4.04.10001282003350.2852-100000@hyperspace.linuxhacker.org>

On Fri, 28 Jan 2000, Rosimildo daSilva wrote:
> Thanks for your straight answer. This was the type of answer
> that i was looking for. I trust your knowledge of graphics
> stuff. I guess FB is the right answer for RTEMS in the long
> run.

I wouldn't bother trying to hack the Linux Framebuffer code directly into
RTEMS if I were you, but the general Framebuffer as a mmapable file
concept is a good idea. If you don't want to support mmap() yet, then just
have a driver independant device file you can do ioctl()s on to handle
locking and find out and set things like the resolution and colour depth,
and read the address at which you can find the hardware framebuffer.

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------


Previous by date: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Rosimildo daSilva
Next by date: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Chris Johns
Previous in thread: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Rosimildo daSilva
Next in thread: 28 Jan 2000 20:20:05 -0000 Re: Images resolution, Chris Johns


Powered by ezmlm-browse 0.20.