mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Allo! Allo!" <lachinois@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel module ethics.
Date: Wed, 27 Feb 2002 16:11:38 -0500	[thread overview]
Message-ID: <F82zxvoEaZWNaBJjvmZ00001183@hotmail.com> (raw)

Hi,

The company for whom I work wants to make a linux driver for some of its 
hardware. On my side I would like the driver to be completely open sourced, 
and from a customer point of view, its a big plus (a real PITA to maintain 
closed sourced drivers). On the other hand, the company wants a clear way to 
make "profit" from the work while still catering to it's customers whish to 
recompile the driver for just about any kernel version.

Here is what they propose... I do not know if what they are proposing is 
"going too far" regarding kernel module ethics, but I thought I'd ask the 
question here and see what other people think.

The hardware needs a firmware to run. Since this firmware is under NDA, the 
first compromise is to write the main part of the driver GPL but keep the 
firmware of the card in binary format. The driver can then load the firmware 
separately and this should not infringe on the GPL and I'm quite ok with 
this requirement. Now the problem is that any of our competitor's cards will 
work with the same closed sourced firmware and GPL engine. In pure 
capitalist thinking, the company finds this particularly troublesome...

The other compromise is to write a closed source part that would not permit 
the driver to work with another card supporting the same chipset. Is this 
kind of practice generally accepted or is it frowned upon? The motive of the 
company is quite clear. If people want to "improve" the driver, they can 
only improve it for their hardware, not the competitors. There is also a big 
marketing sales pitch that goes like "we support linux, the others 
don&#8217;t..."

It's like if Nvidia did not have linux drivers and ASUS wanted to ship a 
card with a linux driver that only works with asus cards even though there 
is one from leadtek with the exact same chipset (assuming that ASUS cannot 
change the internals of the card).

Is the second compromise just "going too far"? Is this better than simply 
having a 100% closed source driver?

Thanks!
Daniel Shane



_________________________________________________________________
MSN Photos est le moyen le plus simple de partager, modifier et imprimer vos 
photos préférées. http://photos.msn.fr/Support/WorldWide.aspx


             reply	other threads:[~2002-02-27 21:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 21:11 Allo! Allo! [this message]
2002-02-27 21:33 ` Cyrille Chepelov
2002-02-27 22:23 ` Richard B. Johnson
2002-02-28  0:51   ` Erik Mouw
2002-02-28  1:03     ` Karl
2002-02-28  2:03       ` Erik Mouw
2002-02-28  2:13       ` Larry McVoy
2002-02-28  1:38         ` Karl
2002-03-04 14:07         ` Rogier Wolff
2002-02-28  2:37       ` John Jasen
2002-02-28  1:20   ` Rik van Riel
2002-02-28  3:59   ` Richard Thrapp
2002-02-28 17:52     ` Jeff V. Merkey
2002-03-01  0:22     ` Alan Cox
2002-02-27 22:37 ` Greg KH
2002-02-28  9:42 ` Helge Hafting
2002-02-28 16:04   ` Mark H. Wood
2002-02-28 18:31     ` David Lang
2002-02-28 13:55 ` Reid Hekman
2002-02-27 21:57 Jesper Juhl
2002-02-28 12:05 Alexander Sandler
2002-03-01  0:53 ` Erik Mouw

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=F82zxvoEaZWNaBJjvmZ00001183@hotmail.com \
    --to=lachinois@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®