nanogui: Nano-X and SDL
Subject:
Re: [nanogui] Nano-X and SDL
From:
Jordan Crouse ####@####.####
Date:
5 Jun 2002 17:34:52 -0000
Message-Id: <1023297695.10691.63.camel@cosmic>
As posted months ago on the Nano-x list, here is a quick patch for
SDL-1.2.3 that adds direct framebuffer access. It has issues, but at
least we get much better speed than we did before. I would recommend
this for a start.
Jordan
On Wed, 2002-06-05 at 10:16, Greg Haerr wrote:
> A while back, when porting SMPEG video to Microwindows,
> I used a working version of SDL (v113, now old, but
> still older than the then current release, but working) and
> wrote a complete low-level driver for SDL using the
> Nano-X API. It should support almost all the SDL
> capabilities. Support for hardware paging was not added.
> I added the capability for Microwindows to export a
> pointer to the framebuffer, so that SDL applications can
> write directly to the framebuffer.
>
> Take a look at the nano-X driver in SDL source to see what's
> missing, not much, I believe. Currently, Microwindows only
> supports one-window access to the framebuffer. This
> could be expanded if required. It should work full-screen;
> this would work by asking Microwindows to allocate a
> full screen window, and then direct-fb-accessing that window.
> (Microwindows returns the interior portion of the window
> as the framebuffer address, the mwin window manager still
> draws the border around the window as usual, if required)
>
> It would be nice to move the SDL 113 Microwindows driver
> into the latest SDL release, and have it supported by Sam,
> the SDL maintainer.
>
> Regards,
>
> Greg
>
>
>
> > -How does SDL use microwindows?
> >
> > -Can I allocate fullscreen, just a window or both to draw in?
> >
> > -Does it enable the application to write directly into the framebuffer?
> >
> > -What if I have 2 programs, running simultaneously, which want to write
> > into the framebuffer? Do they mess with eachother?
> >
> > -Who, why, when, has made the SDL 113 implementation? Is it going to be
> > updated / supported? Which features does it have / miss?
> >
> > Thanks.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
[Content type text/x-patch not shown. Download]
