> 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. > > Resolving this is going to be difficult: X developers don't ever seem > to want to consider compatibilty with driver layers that aren't X, for > one. > -- > Billy Biggs
And exactly because things have become messy like that, one should use a method that is as simple as possible, but powerful enough. A function returning milliseconds to next vblank has no unnecessary complexity, and is still powerful enough for all purposes. [EMAIL PROTECTED] _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
