mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: "Ted Ts'o" <tytso@mit.edu>, 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 22:47:53 +0100	[thread overview]
Message-ID: <AANLkTinEm1mLAtPZdEp2sHRfKPeV6qYP8f9Dbbr92_JD@mail.gmail.com> (raw)
In-Reply-To: <20101121214407.GH23423@thunk.org>

On Sun, Nov 21, 2010 at 10:44 PM, Ted Ts'o <tytso@mit.edu> wrote:
> On Sun, Nov 21, 2010 at 08:31:24PM +0000, Alan Cox wrote:
>>
>> Which we know in practice they won't. They'll sit on fixes (often
>> security fixes) and tweak and add private copies of features. In turn the
>> Linux one could then only keep up by adding features itself - which would
>> have to be GPL to stop the same abuse continuing.
>>
>> It's a nice idea but the corporations exist to make money and adding
>> proprietary custom stack add-ons is clearly a good move on their part to
>> do that.
>
> Hence my recommendation that if someone is going to do the work to
> create a 802.11 layer that has shims that work on multiple operating
> systems, it be GPL with explicit exceptions to allow said layer to
> work on legacy operating systems like QNX, et. al.  That way it forces
> the hardware specific code to be released under the GPL --- if they
> want to take advantage of the "write onces, work on multiple operating
> systems" feature.
>
> If someone is going to go through all of this work to make it possible
> --- particularly if it's at a company such as Luis's employer, or any
> other wifi chipset provider --- why should it allow their competitors
> to do closed source drivers?  Better to structure the driver licensing
> such that (a) there is benefit for companies to make a Linux driver by
> using this common stack, and (b) but in exchange, it forces them to
> make a driver which is guaranteed to be usable by Linux by virtual of
> the fact that (1) the native interface is Linux's wireless stack, and
> (2) the license forces them to GPL their driver.

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.

>
>                                   - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

  reply	other threads:[~2010-11-21 21:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:46 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 [this message]
2010-11-21 21:50                 ` Luis R. Rodriguez
2010-11-22  1:00                   ` Greg KH
2010-11-21 23:35                 ` Ted Ts'o
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=AANLkTinEm1mLAtPZdEp2sHRfKPeV6qYP8f9Dbbr92_JD@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --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=shemminger@vyatta.com \
    --cc=tytso@mit.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®