linux-kernel - Re: Challenges with doing hardware bring up with Linux first

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101121233544.GI23423@thunk.org>
Date:	Sun, 21 Nov 2010 18:35:44 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Gábor Stefanik <netrolller.3d@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	"John W. Linville" <linville@...driver.com>,
	Stephen Hemminger <shemminger@...tta.com>,
	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@...el.com>,
	Charles Marker <Charles.Marker@...eros.com>,
	Jouni Malinen <Jouni.Malinen@...eros.com>,
	Kevin Hayes <kevin@...eros.com>,
	Zhifeng Cai <zhifeng.cai@...eros.com>,
	Don Breslin <Don.Breslin@...eros.com>,
	Doug Dahlby <Doug.Dahlby@...eros.com>,
	Julia Lawall <julia@...u.dk>
Subject: Re: Challenges with doing hardware bring up with Linux first

On Sun, Nov 21, 2010 at 10:47:53PM +0100, Gábor Stefanik wrote:
> 
> By forcing the driver to be GPL, you automatically exclude Windows
> from the list of platforms supported by such a cross-OS driver, as the
> Windows NDIS headers are AFAIK under a GPL-incompatible license, so no
> GPL driver can be written for Windows.

I said GPL "with exceptions".  The exceptions would allow linking with
the necessary glue code (also licensed under GPL "with exceptions")
that allow linkage with legacy operating systems --- including
Windows.

OK, the BSD's won't like it.  Tough.  If someone were to make all of
this code available under those terms, they can either decide to suck
it up and use the code, or use the fact that the hardware dependent
portion of the driver is GPL'ed, which means it won't be supplied in
object-file only form, ala Nvidia, but in source code form, so that if
the BSD's want to use the GPL'ed source code as hardware documentation
so they can write their own docmentation, at least they have the
option/freedom to do so.

That at least would be my recommendation of what anyone doing these
Linux 802.11 compatible stack and shim code for legacy operating
systems do.  If we're going to do the work, we might as well set up
the licensing to force companies to do the right thing --- because if
we don't force companies to do the right thing, in all likelihood
there will be a race to the bottom where they won't.  And even if you
think companies will be altruistic, why not make sure the license is
such that the non-altruistic companies, or the clueless companies are
forced by their lawyers to do the right thing?

Even if Broadcom has reformed (and I don't competely believe it yet),
why should we be completely confident that they won't backslide?

      	      	     	    	   	 - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/