On Sun, 05 Sep 2004 15:15:25 +0100, Alan Cox <[EMAIL PROTECTED]> wrote: > On Sul, 2004-09-05 at 16:05, Jon Smirl wrote: > > > If DRI stays the way it is currently licensed no problems arise anyway > > > (beyond proprietary people reusing DRI code, which given the license is > > > presumably the intent) > > > > > If I copy GPL pieces of fbdev in to the DRM drivers it will pollute > > the BSD license and turn it into GPL. > > There is no reason to do that. The fb layer of Linux and BSD is very > different and both provide fb drawing functionality.
Then how am I going to merge fbdev and DRM so that we don't have two drivers fighting over the same hardware? I was planning on adding pieces of the existing fbdev code to DRM in order to implement printk from the kernel. It seems silly for me to rewrite 10,000 lines of code just to make it BSD licensed when BSD isn't even going to use the code. What is wrong with marking each CVS commit with BSD/GPL license? Then having the BSD people pick off the relevant code. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
