nanogui: Running document -- RTEMS framebuffer interface specification


Previous by date: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification (fwd), Greg Haerr
Next by date: 4 Feb 2000 17:51:46 -0000 Trouble getting pre6, davidc
Previous in thread: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next in thread: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification, Erwin Rol

Subject: Re: Running document -- RTEMS framebuffer interface specification
From: "Greg Haerr" ####@####.####
Date: 4 Feb 2000 17:51:46 -0000
Message-Id: <024b01bf6f36$ee7dc440$15320cd0@gregh>

Rosimildo,
    As I think about this a little more, one important factor is
whether or not RTEMS wants to support graphics mode for
console operation.  This adds complexity.  If merely a framebuffer
is desired, it is quite a bit simpler, because all RTEMS has to manage
is the switch between text and graphics, video init, and the actual
framebuffer mapping.

To support a graphics console, there have to be quite a few more entry points,
and the framebuffer code has to support being accessible inside
the kernel, rather than just address-mapped video memory access to
applications.

Frank's PK supports a graphics console, and he has kept the
system quite simple.  Perhaps his code is a good place to start.

Greg


Previous by date: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification (fwd), Greg Haerr
Next by date: 4 Feb 2000 17:51:46 -0000 Trouble getting pre6, davidc
Previous in thread: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification, Greg Haerr
Next in thread: 4 Feb 2000 17:51:46 -0000 Re: Running document -- RTEMS framebuffer interface specification, Erwin Rol


Powered by ezmlm-browse 0.20.