On Fre, 2002-11-01 at 19:42, Billy Biggs wrote: > > Some folks in the DRI world are doing a standard device API. There > are also a million different kernel module hacks that export vsync > interrupts existing now, look at any of the video applications right > now: we have like 4 different mga kernel modules for hardware overlay > surfaces with vsync interrupts, now svgalib has their own kernel > callback driver, DRI has theirs presumably for page flipping at some > point, etc.
I think it might be a good idea to write a small abstraction library which can use the various means (DRM, svgalib, ...) that already provide this. > I think the main reason for the lack of a standard effort is the > varying requirements of the projects proposing these solutions. The > mplayer folks (and some xine/etc authors) want some kernel solution > that's independent of X and DRI and fbcon, since they want to support > different levels of exlusive or direct access. Some other projects, > such as DirectFB, only care about this in the context of fbcon itself. > And then the DRI folks only care about X, and so solutions from that > arena may not work outside of a running X server. As you can see in http://dri.sourceforge.net/IRC-logs/20020121.txt (and/or maybe some following logs), it is a long term goal of the DRI project to support other environments, but so far I'm not aware of any real effort from outside the project except maybe fbdri. You don't absolutely need an X server to use the DRM, although you probably need to act pretty much like an X server at this point. :) -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
