Re: LCC and blobs

2004-12-11 Thread Matthew Garrett
Brian Nelson [EMAIL PROTECTED] wrote: You are the only person I've seen express views similar to mine on debian-legal. All other participants argue for non-free-firmware-using drivers going in contrib. (cough) I'm still entirely unclear on the logic of moving drivers that require firmware

Portaudio license

2004-12-11 Thread Free Ekanayaka
|--== Bill Morgan writes: BM The license looks clean to me: BM http://www.portaudio.com/license.html BM The only real restriction is not to remove the copyright statement. BM Is that too much for DFSG? I think this question should be posted to debian-legal, thus I'm taking the

Re: LCC and blobs

2004-12-11 Thread Matthew Garrett
Matthew Garrett [EMAIL PROTECTED] wrote: This would make more sense if I sent it to the right list, really. Sorry about that. Brian Nelson [EMAIL PROTECTED] wrote: You are the only person I've seen express views similar to mine on debian-legal. All other participants argue for

Re: LCC and blobs

2004-12-11 Thread Thomas Bushnell BSG
Matthew Garrett [EMAIL PROTECTED] writes: Let's pretend that Debian actually has a significant amount of leverage on this sort of issue, and that vendors see their drivers appearing in contrib and want to do something about it. They /could/ open the firmware and provide a toolchain for it.

Re: LCC and blobs

2004-12-11 Thread Glenn Maynard
On Sat, Dec 11, 2004 at 02:23:16PM -0800, Brian Nelson wrote: While you have your pen and paper out, go ahead and write some hardware that a contrib device driver can use without needing firmware loadable by the kernel. Put the firmware on the device itself. That contrib driver is now

Re: LCC and blobs

2004-12-11 Thread Brian Nelson
On Sat, Dec 11, 2004 at 05:49:26PM -0500, Glenn Maynard wrote: On Sat, Dec 11, 2004 at 02:23:16PM -0800, Brian Nelson wrote: While you have your pen and paper out, go ahead and write some hardware that a contrib device driver can use without needing firmware loadable by the kernel. Put the

Re: LCC and blobs

2004-12-11 Thread Bruce Perens
Glenn, If you don't have a physical copy of the device, the driver doesn't work either. Very similarly to the way it would act if you don't have the firmware. The problem is that we have to distribute the firmware when it's a BLOB. Thanks Bruce Glenn Maynard wrote: If the driver has

Re: LCC and blobs

2004-12-11 Thread Glenn Maynard
On Sat, Dec 11, 2004 at 04:42:23PM -0800, Brian Nelson wrote: Fundamentally, I think it comes down to this: we have to draw the line somewhere, and that line has always been drawn at the software/hardware boundary. Neither the Linux kernel nor Debian have ever considered the freeness of

Re: LCC and blobs

2004-12-11 Thread Glenn Maynard
On Sat, Dec 11, 2004 at 04:48:29PM -0800, Bruce Perens wrote: If you don't have a physical copy of the device, the driver doesn't work either. Very similarly to the way it would act if you don't have the firmware. The problem is that /we /have to distribute the firmware when it's a BLOB.

Re: LCC and blobs

2004-12-11 Thread Goswin von Brederlow
Brian Nelson [EMAIL PROTECTED] writes: On Sat, Dec 11, 2004 at 05:49:26PM -0500, Glenn Maynard wrote: On Sat, Dec 11, 2004 at 02:23:16PM -0800, Brian Nelson wrote: While you have your pen and paper out, go ahead and write some hardware that a contrib device driver can use without needing

Re: LCC and blobs

2004-12-11 Thread Goswin von Brederlow
Bruce Perens [EMAIL PROTECTED] writes: Glenn, If you don't have a physical copy of the device, the driver doesn't work either. Very similarly to the way it would act if you don't have the firmware. The problem is that we have to distribute the

Re: LCC and blobs

2004-12-11 Thread Bruce Perens
Goswin von Brederlow wrote: Also why would anyone be forced to distribute the blob? The problem isn't that we have to distribute the blob. The problem is how free do we judge the driver to be. We judge that by the DFSG. The DFSG doesn't include any language about dependencies on non-free

Re: LCC and blobs

2004-12-11 Thread Goswin von Brederlow
Bruce Perens [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Apart from being ugly the above is perfectly legal and nothing speaks against adding it, _provided_ this is the source. I have actually seen GPL sources with such byte sequences in it for

ng-spice legal-license advice

2004-12-11 Thread Matt Flax
Hello, I have itp'd ngspice which MAY have legal issues stopping it from inclusion into debian ... This person contacted me (he is applying to become a maintainer) http://nm.debian.org/nmstatus.php?email=roktas%40omu.edu.tr This person says that license issues stop the inclusion of this

Re: ng-spice legal-license advice

2004-12-11 Thread Glenn Maynard
On Sun, Dec 12, 2004 at 02:42:48PM +1100, Matt Flax wrote: This person says that license issues stop the inclusion of this package with debian ... from the ng spice source ball I find the following licenses - many licenses as it is the combination of decades of different distrubutions and

Re: LCC and blobs

2004-12-11 Thread Brian Nelson
On Sat, Dec 11, 2004 at 08:02:28PM -0500, Glenn Maynard wrote: On Sat, Dec 11, 2004 at 04:42:23PM -0800, Brian Nelson wrote: Contrib exists for software dependencies. This is not a software dependency issue. There is no direct relationship between firmware and drivers. I don't see how