nanogui: Running document -- RTEMS framebuffer interface specification


Previous by date: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next by date: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specificatio n, Greg Haerr
Previous in thread: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next in thread: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specificatio n, Greg Haerr

Subject: Re: Running document -- RTEMS framebuffer interface specification
From: "Frank W. Miller" ####@####.####
Date: 11 Feb 2000 16:35:34 -0000
Message-Id: <200002111523.KAA16056@macalpine.cornfed.com>

Hi guys,

First Ros, I've looked at everything you've done and it looks really
good.  I should be able to take what you've done and port it quite easily.

Was just thinking a bit now about the framebuffer concept in general.
So, in Linux, the video memory is mapped into the process address apce?  What
about protection?  The user process can clobber any part of the
frame buffer in addition to working with the part its responsible
for.  This might be ok if the application is being granted the entire
screen, like for  a game or something.  For a windowing system, its not
as appealing.  Roadrunner/pk is going to have the same problem as Linux.

Later,
FM

--
Frank W. Miller
Cornfed Systems Inc
www.cornfed.com

Previous by date: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next by date: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specificatio n, Greg Haerr
Previous in thread: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next in thread: 11 Feb 2000 16:35:34 -0000 Re: Running document -- RTEMS framebuffer interface specificatio n, Greg Haerr


Powered by ezmlm-browse 0.20.