--- Ian Romanick <[EMAIL PROTECTED]> wrote:
Daniel Vogel wrote:
To clarify: I meant what has to be done to make
DRI (direct rendering
*infrastructure*) attractive for IHVs. I didn't
mean to imply what has to be
done to get NVIDIA or ATI to release open source
drivers and whatnot.
The uncanny thing is that this is almost EXACTLY my job description. :)
Would making a version of DRI that can run standalone be interesting? Then X Windows would load on top of the standalone DRI.
A few reasons: 1) Provides a much more constrained platform for the IHV to work on. Simpler to build and debug. 2) Would isolate IHV changes from the rest of X 3) Could be used as a game platform 4) Could be used in embedded systems without X 5) Could be used in projects like DirectFB or alternative OS's. 6) Provides a platform for building and alternative windowing system (that's what I am interested in).
A standalone DRI might allow all platform specific code to be removed from X in the long run.
Interesting you mention it. This is what Brian & I've done in the Mesa embedded branch -- layered the radeon dri driver on top of fbdev. I can also build regular DRI drivers from a minimal tree & sane set of makefiles.
Keith
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
