All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	Charles Marker <Charles.Marker@atheros.com>,
	Jouni Malinen <Jouni.Malinen@atheros.com>,
	Kevin Hayes <kevin@atheros.com>,
	Zhifeng Cai <zhifeng.cai@atheros.com>,
	Don Breslin <Don.Breslin@atheros.com>,
	Doug Dahlby <Doug.Dahlby@atheros.com>,
	Julia Lawall <julia@diku.dk>
Subject: Re: Challenges with doing hardware bring up with Linux first
Date: Sun, 21 Nov 2010 18:35:44 -0500	[thread overview]
Message-ID: <20101121233544.GI23423@thunk.org> (raw)
In-Reply-To: <AANLkTinEm1mLAtPZdEp2sHRfKPeV6qYP8f9Dbbr92_JD@mail.gmail.com>

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

  parent reply	other threads:[~2010-11-21 23:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:46 Challenges with doing hardware bring up with Linux first Luis R. Rodriguez
2010-11-18 11:11 ` Theodore Tso
2010-11-18 16:46   ` Luis R. Rodriguez
2010-11-21 13:02     ` Ted Ts'o
2010-11-21 17:29       ` Greg KH
2010-11-21 19:51         ` Luis R. Rodriguez
2010-11-21 20:31           ` Alan Cox
2010-11-21 21:44             ` Ted Ts'o
2010-11-21 21:47               ` Gábor Stefanik
2010-11-21 21:50                 ` Luis R. Rodriguez
2010-11-22  1:00                   ` Greg KH
2010-11-21 23:35                 ` Ted Ts'o [this message]
2010-12-29 21:35                 ` Enrico Weigelt
2010-11-21 21:49               ` Luis R. Rodriguez
2010-12-03 14:13               ` Pavel Machek
2010-11-21 21:47             ` Luis R. Rodriguez
2010-11-21 22:12               ` Luis R. Rodriguez
2010-11-18 11:34 ` Alan Cox
2010-11-18 16:51   ` Luis R. Rodriguez
2010-11-30 19:26     ` Pavel Machek
2010-11-30 19:30       ` Luis R. Rodriguez
2010-11-30 19:41         ` Luis R. Rodriguez
2010-11-30 20:00         ` Pavel Machek
2010-11-30 20:09           ` Luis R. Rodriguez
2010-11-30 20:13           ` david
2010-12-01 16:02             ` Bradley M. Kuhn
2010-11-18 16:45 ` Greg KH
2010-11-18 16:53   ` Luis R. Rodriguez
2010-11-18 17:23     ` Stephen Hemminger
2010-11-21  0:32     ` Adrian Chadd
2010-11-21  5:53       ` Luis R. Rodriguez
2010-11-21  7:11         ` Adrian Chadd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101121233544.GI23423@thunk.org \
    --to=tytso@mit.edu \
    --cc=Charles.Marker@atheros.com \
    --cc=Don.Breslin@atheros.com \
    --cc=Doug.Dahlby@atheros.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=julia@diku.dk \
    --cc=kevin@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=netrolller.3d@gmail.com \
    --cc=shemminger@vyatta.com \
    --cc=zhifeng.cai@atheros.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.