nanogui: Running document -- RTEMS framebuffer interface specification


Previous by date: 11 Feb 2000 05:39:26 -0000 X11 sources - map, Greg Haerr
Next by date: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva
Previous in thread: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva
Next in thread: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva

Subject: Re: Running document -- RTEMS framebuffer interface specification
From: "Greg Haerr" ####@####.####
Date: 11 Feb 2000 05:39:26 -0000
Message-Id: <003b01bf7450$ba211840$15320cd0@gregh>

: I have compiled the code of our interface, and wrote a "skeleton"
: driver for RTEMS ( it actually compiles ) along with the MicroWindows
: glue ( Micro FrameBuffer ) discussed in the past few weeks.
: Before I finalize the tests, and package it as a "patch", I would
: appreacite any feedback. I have added the sources as links in the
: document on the link below.

I have looked over all your source and it looks great.  You will
of course have to link in ega_hwinit and ega_hwterm into the kernel...

Your code also assumes that there is the same address space between
kernel and user modes for the framebuffer.  I don't know if that's the best
idea or not.  But I guess you will always pass this address in
fbinfo.smem_start?

Greg


Previous by date: 11 Feb 2000 05:39:26 -0000 X11 sources - map, Greg Haerr
Next by date: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva
Previous in thread: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva
Next in thread: 11 Feb 2000 05:39:26 -0000 Re: Running document -- RTEMS framebuffer interface specification, Rosimildo daSilva


Powered by ezmlm-browse 0.20.