From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: G??bor Stefanik <netrolller.3d@gmail.com>,
Ted Ts'o <tytso@mit.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 17:00:38 -0800 [thread overview]
Message-ID: <20101122010038.GA7688@kroah.com> (raw)
In-Reply-To: <AANLkTikVdm5bnXhGeg9rYsacWJsf_2s6A+b3iKJQeisD@mail.gmail.com>
On Sun, Nov 21, 2010 at 01:50:30PM -0800, Luis R. Rodriguez 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've actually have been told GPL drivers for windows are possible with
> some hard work. I have yet to investigate further on what that "hard
> work" means. But yes, that is a good example.
The "hard work" means you can not use the Windows DDK at all. People
have worked to reimplement the header files needed for this into mingw,
but it really restricts you and forces you to write "native" drivers for
Windows, not being able to take advantage of their driver model code at
all.
Oracle did a bunch of work for this in the past to port some of their
Linux kernel work to Windows, ask Andy Grover if you have questions
about it.
hope this helps,
greg k-h
next prev parent reply other threads:[~2010-11-22 1:12 UTC|newest]
Thread overview: 31+ 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 [this message]
2010-11-21 23:35 ` Ted Ts'o
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=20101122010038.GA7688@kroah.com \
--to=greg@kroah.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=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=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;
as well as URLs for NNTP newsgroup(s).