That's fine with me. we can revert back to xfree86 CVS for the trunk and I can move to a branch. I wouldn't have put it on the trunk if I had know the mode stuff was cause so much trouble, but then again, it's been working fine for me and those who initially tested it, so I need to more testers to find the bugs :)
if we move to a branch, perhaps we could add it to the snapshots? Alex --- Keith Whitwell <[EMAIL PROTECTED]> wrote: > Michel Dänzer wrote: > > On Tue, 2003-10-14 at 21:58, Alex Deucher wrote: > > > >>The reason mergedfb is enabled by default is to emulate the clone > >>behavior in the old driver. perhaps this should be changed in the > >>future? > >> > >>In the mean time, I may switch back to validating the modes on > crtc2 > >>before crtc1. that was the way I had it initially and the way it > was > >>for clone mode. > > > > > > So you are no longer actually emulating the former clone mode. > Reverting > > that sounds like a very good idea. Experimental changes should > probably > > be done on a branch. > > > > I have to say I agree with Michel here. In hindsight, this work > should have > been done on a branch to start with -- the trunk isn't the place to > be > debugging new code. > > I'm not sure how much work is left in this, but I'm coming to share > the > opinion that it is still worthwhile to move it to a branch until the > glitches > are ironed out. > > Keith > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
