On 5/16/08, Dieter <[EMAIL PROTECTED]> wrote: > > > > Written submissions should be in OpenDoc or PDF format > > > > > > Something wrong with plain text? > > > > Well, you do want to include diagrams, charts, graphs, and pretty > > colors, don't you? :) > > > Catch-22. You need the drivers for the graphics card to develop > the pretty colored diagrams. > > > > > > proposals and the work carried out shall be licensed with GPL or > compatible > > > > license, and suitable for submission to the OGD source repository. > > > > > > > > > The drivers need to have licenses that the various OS projects > > > will accept. Unfortunately some OSes refuse to include GPLed code > > > in the kernel. :-( > > > > Yeah. I urge people to use the following license scheme: > > > > - GPL for all hardware designs > > - GPL for microcode > > - GPL for stand-alone applications > > - MIT for BIOS, kernel drivers, and graphics drivers > > > I thought the BIOS would be a separate lump-o-code and not linked > with other code? So could be GPL?
Maybe. If it's GPL, and Traversal has full rights, then we could make some extra money from licensing it to those who want to combine it with customizations. Whatever we do here, we want to be sure that there are no issues with porting to different platforms. > > The kernel drivers need to have licenses compatible with their OS. MIT with conversion option? > I'm not sure what you mean by "graphics drivers"? X11 drivers, for UNIX. Windows divides the driver into a low-level miniport driver and high-level drivers for GDI and DirectX. > > > If someone closes up some code from one of our > > drivers, it does nothing but expand the support for our hardware. > > > Closed code is always bad, because you can't fix the bugs they added. > Unfortunately we are stuck with allowing it until someone does GPLBSD. Closed drivers aren't our problem, because we'll have Free drivers for whatever we need. But let's not prevent, say, NASA from incorporating our hardware into some system that they need full control over. > Which gives another reason for keeping the kernel driver as small as > possible (within reason) and having most of the code in userland. > In addition to keeping bloat out of the kernel, the userland code > can be GPL and shared across OSes. X11, maybe, but not all platforms use X11. > Hmmm, the diagram could use green for GPL, blue for BSD, magenta > for MIT, ... > > _______________________________________________ > Open-graphics mailing list > [email protected] > http://lists.duskglow.com/mailman/listinfo/open-graphics > List service provided by Duskglow Consulting, LLC (www.duskglow.com) > -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
