LKML Archive on
help / color / mirror / Atom feed
From: Matthias Andree <>
	"Surendra I." <>
Subject: Re: protecting source code in 2.6
Date: Fri, 21 May 2004 10:29:49 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 20 May 2004, Jinu M. wrote:

> The device interface module is proprietary source and we don't intend
> to distribute it with source code on GPL license.

Why is there a reason to lock down the source of the actual driver?

Can we assume the hardware is so cheap that all the smartness is in the
software? Why would anyone buy the hardware then? What performance could
we expect?

What kind of device is yours that users would not have an alternative to
buy something with open-source driver that has the same function?

Plus, are you committing to:

- compile and re-compile (after kernel changes) your module over and
  over again, to keep it working?

- provide the module for any platform that accepts the hardware
  (ix86, AMD64, PowerPC, sparc, sparc64, ...)

- guarantee the users of your hardware a support period, say, three years
  at least, during which you will continue to provide updated binary
  modules, if need be, for particular distributions?

- support and pre-filter all bug reports, whether the problem originates
  in your closed source driver

- why are _you_ trying to profit from open source without contributing

- the next item I cannot conceive right now but someone will bring up?

I wonder why anyone would be motivated to help, for free, with a
closed-source driver.

The situation for you will likely change completely should you decide to
open-source the driver - vendors who have chosen that path have usually
received support, often their drivers have ultimately become part of the
kernel, so the users won't have to go search for the driver themselves,
hassling with nonstandard installation procedures and all that, and your
visibility in hardware data bases may help the sales of your hardware.

Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95

  parent reply	other threads:[~2004-05-21 23:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 13:18 Jinu M.
2004-05-20 13:44 ` John Bradford
2004-05-20 14:05 ` Bartlomiej Zolnierkiewicz
2004-05-20 15:43 ` Richard B. Johnson
2004-05-21  8:29 ` Matthias Andree [this message]
2004-05-21 16:05 ` Rik van Riel
2004-05-21 19:49 ` Bill Davidsen
2004-05-20 13:21 Jinu M.
2004-05-20 14:08 ` Sam Ravnborg
2004-05-20 14:08 ` Giuliano Pochini
     [not found] <>
     [not found] ` <>
2004-05-22 14:54   ` Vincent C Jones
2004-05-22 23:24     ` Benjamin Herrenschmidt
2004-05-23  0:56       ` Vincent C Jones

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:

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

  git send-email \ \ \ \ \
    --subject='Re: protecting source code in 2.6' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).