From: Reid Hekman <reid.hekman@ndsu.nodak.edu>
To: lachinois@hotmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel module ethics.
Date: 28 Feb 2002 07:55:57 -0600 [thread overview]
Message-ID: <1014904559.11411.11.camel@zeus> (raw)
In-Reply-To: <3C7DFB9C.6A9F41F5@aitel.hist.no>
In-Reply-To: <F82zxvoEaZWNaBJjvmZ00001183@hotmail.com> <3C7DFB9C.6A9F41F5@aitel.hist.no>
On Thu, 2002-02-28 at 03:42, Helge Hafting wrote:
> How can a closed-source driver help you? Even such a driver may be
> pirated and used on the competitors card. But you choose to trust
> people in that situation. If you trust people that much you might
> as well release an open-source driver with a clause that it may only
> be used with _your_ company's cards. Or provide the _firmware_
> with a strict licence and trust they don't pirate that.
>
> The ideal way (for us customers) is if your company and the others with
> similiar hardware agree on sharing the development cost of a
> GPL driver. Nobody loose from paying for a driver the others can use.
> Capitalist competition is still possible:
> * extra features, quality & reliability are selling points
> * pricing, advertising
> * trying to manufacture in cheaper ways than the others
>
> Sharing the cost of development makes a lot of sense because the
> others *will* come up with their own linux drivers anyway if
> it turns out to be money in selling hardware to linux users.
> All loose by making separate drivers.
Another possibility in this same vein is if you're a board level
manufacturer integrating somebody elses silicon, prod the chip
manufacturer to help with a driver (GPLed code, docs, whatever). It
costs you very little, and you get to claim Linux support. If your extra
(binary) firmware only works with your card (technical or market
reasons, doesn't matter) you aren't giving away the store any more than
with a closed driver.
Regards
next prev parent reply other threads:[~2002-02-28 13:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 21:11 Kernel module ethics Allo! Allo!
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 3:59 ` Richard Thrapp
2002-02-28 17:52 ` Jeff V. Merkey
2002-03-01 0:22 ` Alan Cox
2002-02-28 1:20 ` Rik van Riel
2002-02-27 22:37 ` Greg KH
2002-02-28 9:42 ` Helge Hafting
2002-02-28 13:55 ` Reid Hekman [this message]
2002-02-28 16:04 ` Mark H. Wood
2002-02-28 18:31 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
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=1014904559.11411.11.camel@zeus \
--to=reid.hekman@ndsu.nodak.edu \
--cc=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