Index:
[thread]
[date]
[subject]
[author]
From: becka@rz.uni-duesseldorf.de
To : mailing list GGI <ggi-develop@eskimo.com>
Date: Wed, 10 Mar 1999 19:58:15 +0100 (MET)
Resending
> Hi !
> > Yeah, but there's not much point in rewriting every graphics driver
> > twice. For those who don't know, XFree86 4.0 uses driver modules,
> > which means all of the hardware code is nicely encapsulated now.
> Are they ? Last time I looked at XAA (or have they replaced it ?)
> it didn't care about initialization in the modules (the server did),
> only accel. KGI drivers are kind of "the other way round". They
> primarily care about initialization and mode setup, then about accel.
> > Also, this means XGGI could be replaced by an XFree86 driver module
> > which is just a layer to GGI.
>
> Yes. I'd say that would be nice. Volunteers, please !
>
> > And if you do that, you could do the
> > reverse, making a XFree86 driver interface to GGI, which means any
> > XFree86 4.0 driver could be used as a hardware accelerator for GGI
> > directly.
>
> Yes. If the drivers are suitable we will surely do that.
>
> > However, the move to driver modules makes GGI and XFree86 a lot more
> > alike, so driver "swapping" via thin interface layers may be a very
> > real possibility, which would hopefully lead to some kind of
> > consolidation.
>
> YES. We always offered that to the XFree people. In person to some of them.
>
> > If anyone here is interested in looking at the 4.0 driver specs, I'll
> > see if I can get you the documentation.
>
> Would be good. I really hope they finally put _ALL_ the card info into the
> driver module.
>
> CU, ANdy
>
> --
> = Andreas Beck | Email : <andreas.beck@ggi-project.org> =
Index:
[thread]
[date]
[subject]
[author]