Re: DRI and Silicon Motion
Just so. Unless otherwise specified, cat_fish's code would be considered a work for hire, and copyright would belong to the employer. :-) Thank you all for your concern in this matter, but it is clearly covered in my proposal that the work will remain open source and be re-submitted to XFree (and to the DRI project as well, since it appears that is a separate code tree). My primary concern at this time is providing an accurate estimate up front for how much work this will be. Thank you all for your advice and help. If this thing gets approved, I will most certianly be back with more questions. Noel. -- A precariously balanced mixture of myopic optimism and rampant paranoia. _ Need more e-mail storage? Get 10MB with Hotmail Extra Storage. http://join.msn.com/?PAGE=features/es ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
Cheshire Cat Fish wrote: Mesa support/conformance is a requirement. The resulting SMI drivers would remain open source, and part of the Xfree/DRI/Linux distribution. That is the plan at least. That's good news. :) There are way too many variables to be able to accurately answer that question (see my answer to your first question). :) But it sounds like at best I can only re-use the very lowest level of drawing code (the part that talks to the hardware_ from the Windows 2000 driver. Everything above that will be different. That's a fair assessment. This is starting to sound like a couple of months work. At least. I don't know how much time per week you're planning to put into this, but, working full time, it would probably take a month or so for someone familiar with DRI internals to get something working using existing driver code good documentation. To get it working *well* would require more time. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
On Thu, 04 Sep 2003 09:49:53 -0700, Cheshire Cat Fish wrote: Licensing issues are not a problem. SMI has approached me asking for this to be done, so I will have full access to all their source code to use to complete this task. I would caution that your conclusion (licensing is not a problem) does not necessarily follow from your premise (SMI asked for it). When I did the Savage driver under contract to S3, I made sure that my contract specifically noted that the resulting code would be submitted to XFree86.org for open source release. That way, there was no crisis of expectations later on. I have also had some clients ask for custom modifications that they did NOT want sent back to XFree86. You just need to be sure of what they want. -- - Tim Roberts, [EMAIL PROTECTED] Providenza Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
TR I would caution that your conclusion (licensing is not a problem) does not necessarily follow from your premise (SMI asked for it). Just so. Unless otherwise specified, cat_fish's code would be considered a work for hire, and copyright would belong to the employer. = -- Craig Groeschel ladder91 at yahoo dot com AT '00 Tread lightly. Leave no trace. Never forget. Fuel is a resource; people aren't. Dennis Bakke When replying, please do not quote my entire message. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
DRI and Silicon Motion
I am investigating supporting DRI and OpenGL for the Silicon Motion driver. I'm new to both of those, so some of these may be newbie sounding questions. 1) I have the OpenGL code from the Windows 2000 Silicon Motion driver. Can this code be mostly used as is? Or will the Linux code be entirely different? 2) In the DRI Users Guide, section 3.2-Graphics Hardware, Silicon Motion is not listed as currently being supported. Is this still the case? Is anyone working on this? Or am I starting from scratch? 3) How big of a task am I looking at here? Since I alrady have the Win2k OGL code to base my work on, it seems to me it shouldn't be too hard to drop that code in and hook it up to DRI. A few weeks maybe? Or am I missing something fundamental? Thanks, Noel. -- A precariously balanced mixture of myopic optimism and rampant paranoia. _ MSN 8: Get 6 months for $9.95/month http://join.msn.com/?page=dept/dialup ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DRI and Silicon Motion
Cheshire Cat Fish wrote: I am investigating supporting DRI and OpenGL for the Silicon Motion driver. I'm new to both of those, so some of these may be newbie sounding questions. 1) I have the OpenGL code from the Windows 2000 Silicon Motion driver. Can this code be mostly used as is? Or will the Linux code be entirely different? Depending on licensing issues attached to the code you have and how you want to distribute it, you may be able to use a lot or a little. All of the existing open-source drivers are based on Mesa, and the whole build process for 3D drivers in XFree86 is built on that. I suspect, but am in no position to say for sure, that any contributed drivers would have to conform to that. Porting the existing driver to use Mesa would probably be a lot of work, but it shouldn't be insurmountable. If you want to basically use your existing code as-is, you can port it to just interface with the XFree86 libGL.so. That would be a much smaller task, but it would leave you on your own (pretty much) to support and distribute the driver. I don't think it would get included in an XFree86 release. There's also the issue of the license that may be attached to the existing code, but as I'm neither a lawyer or an official XFree86 maintainer I'm in no position to comment. 2) In the DRI Users Guide, section 3.2-Graphics Hardware, Silicon Motion is not listed as currently being supported. Is this still the case? Is anyone working on this? Or am I starting from scratch? This hardware is not supported and I know of nobody that is working on it. 3) How big of a task am I looking at here? Since I alrady have the Win2k OGL code to base my work on, it seems to me it shouldn't be too hard to drop that code in and hook it up to DRI. A few weeks maybe? Or am I missing something fundamental? There are way too many variables to be able to accurately answer that question (see my answer to your first question). :) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
