I've been down the branch path before. I have many thousands of lines of
changes. If I do all of them on a branch sometime in the future people might
decide to merge them. When that happens everyone will say there is too much code
and it is too complex to understand, break it up into small patches again. Then
I'll have to spend three months breaking things back into chunks. These will
then get nit picked to death and each one will take a month to get into the
trunk. A year from now I might have the functions merged. To avoid merge issues
I will have to continuously monitor the trunk and track each check in there and
apply it by hand to the branch.
Next is the whole can of worms over FB vs DRM vs a third base driver. Of course
this will take a year or more to sort out if ever gets changed. There will be
months of arguments over where mode setting and memory management should go.
Sooner or latter I would hope that people will see the insanity of having
multiple device drivers trying to control the same piece of hardware.
My objective is not to build the perfect FB/DRM device driver. So I'm going to
take simpler route and zip up my DRM changes and save them somewhere.
I can extract the code from Xfree for doing everything I need from user space
and I can add this code into the mesa linux-solo project without a lot of hassle.
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
-------------------------------------------------------
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
