> 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
This is just open source, there are no short-cuts, if you feel your code would make it into the kernel, then I would be happy about putting it on the trunk, but I don't want to spend time sending patches to Linus that get repeatedly bounced because he doesn't like duplication fb functionality in drm modules... that is the major point to why your patches are not checked in .. if you feel that is unfair, then submit the patches to Linus also and if he agrees they are okay, I'll have no objections.. if you make the patches available, I'll probably check them into a branch anyways to avoid losing them.. > 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. This insanity is well known, a solution has not so far appeared that ppl agree on, this won't be it, this sort of work needs buy-in from the people who manage and maintain it, a bad design will cause more trouble in the long run... > 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. but that is what is needed, and hence why your changes can't just be thrown into the DRM, for Linux 2.7 it would be nice to design this stuff properly, and sort it all out and I hope you'll join in that when it opens... Please at least put your patches up on a publically accessible site (fd.o being the perfect one, I really want to see the overall effect and train of thought, and some parts are definitely mergeable, > 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. Are you going to get solo so it doesn't require an fb device? if so that is defintely something I for one would like to see.. solo has made my life a hell of a lot easier :-) 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
