> > It is a bit intrusive and I can't see an easy way to wrap it ... > > How have we dealt with these sorta major ones before? and at what point > should we just branch the DRM so 2.4 and 2.6 are separate tracks? (I might > start another e-mail in a minute...)
Okay I talked with Michael Danzer on IRC and I've checked in what I believe is the correct solution using stubs in drmP.h, it builds for me on 2.6 and 2.4, i can't test it on 2.4 at the moment, but it looks correct... our DRM is now synced with changes in 2.6 that we don't have, now to try and get a patch or maybe a bk repo going the other way... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
