public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Runar Ingebrigtsen <runar@mopo.no>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Help porting wireless InProComm IPN 2220 driver to 2.6
Date: Thu, 15 Sep 2005 12:23:37 +0100	[thread overview]
Message-ID: <6278d22205091504232ac3d8c3@mail.gmail.com> (raw)
In-Reply-To: <43295825.90205@domdv.de>

On 9/15/05, Andreas Steinmetz <ast@domdv.de> wrote:
> Daniel J Blueman wrote:
> > The file D-Link has made available contains either this or a
> > closed-source driver.
> 
> This is getting interesting. The tar archive contains a kernel source
> tree (looks like 2.4.26). This kernel source tree contains the directory:
> 
> linux-2.4.x/drivers/net/wireless/inpro2220
> 
> Within this directory there's the file IPN2220 which is a mips object
> file, so this is a binary only driver.
> 
> Now, even if this is built as a module the module "source" is imported
> in the kernel source tree, i.e. it is not separate from the kernel
> source. IMHO I do see this then as a GPL violation that goes beyond the
> Linus tolerated level.

This depends if the module uses any symbols exported from the kernel
with EXPORT_SYMBOL_GPL(), and clearly the module license - 'strings'
should be enough do check this is you don't have a MIPS platform to
hand.

See http://www.uwsg.iu.edu/hypermail/linux/kernel/0110.2/0369.html .
___
Daniel J Blueman

  reply	other threads:[~2005-09-15 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 10:44 Help porting wireless InProComm IPN 2220 driver to 2.6 Daniel J Blueman
2005-09-15 11:16 ` Andreas Steinmetz
2005-09-15 11:23   ` Daniel J Blueman [this message]
2005-09-15 11:45     ` Andreas Steinmetz
2005-09-15 12:36     ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 22:15 Runar Ingebrigtsen

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=6278d22205091504232ac3d8c3@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=ast@domdv.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=runar@mopo.no \
    /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