--- Tomas Carnecky <[EMAIL PROTECTED]> wrote: > My idea is that every card creates a device node in /dev which can be > openend by anyone with appropriate rights. With each device is a > userspace library associated which has implemented the interface > functions (gl*). The interface between userspace library and device node > is not defined, each driver/library pair can create's own interface. > So it is possible to > 1) implement everything in userspace and use the device driver only to > access the framebuffer or > 2) use hardware acceleration using the device driver. > So it's possible that every driver developer can decide for himself what > to put into the userspace library and what into the kernel driver. > The only interface that is defined is opengl. > > (Actually, that's not just an idea, but my project. I've done quite a > lot of work so far, now I'm looking for some opengl implementations I > could use.)
You are rebulding mesa-solo. http://www.mesa3d.org/fbdev-dri.html ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
