From: Greg KH <greg@kroah.com>
To: Zan Lynx <zlynx@acm.org>
Cc: Pavel Roskin <proski@gnu.org>,
Patrick Mochel <mochel@digitalimplant.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Please open sysfs symbols to proprietary modules
Date: Wed, 2 Feb 2005 21:07:42 -0800 [thread overview]
Message-ID: <20050203050742.GA17909@kroah.com> (raw)
In-Reply-To: <1107406442.23059.16.camel@localhost>
On Wed, Feb 02, 2005 at 09:54:02PM -0700, Zan Lynx wrote:
> So, what's the magic amount of redirection and abstraction that cleanses
> the GPLness, hmm? Who gets to wave the magic wand to say what
> interfaces are GPL-to-non-GPL and which aren't?
Go read the historical posts from Linus that talk about how and why
closed source modules were allowed for Linux. Then think about the fact
that those issues are no longer pertintante these days for the majority
of people who are trying to create such things.
Then go consult an IP lawyer and listen to what they say. If your
company feels that it can still ship a closed source driver, with legal
approval, great, you've accepted the risk that this involves, and are
willing to handle the issues that will occur (cease-and-deist letters,
lawsuits, etc.)
> If the trend of making everything _GPL continues, I don't see any choice
> for binary module vendors but to join together to develop a stable
> driver API and build it as a GPL/BSD module. Do the same API for BSD
> systems to prove modules using it are not GPL derived. Watch Greg foam.
> It'd be fun.
Ah, UDI is over that-a-way. Been there, done that, watched everyone
abandon it due to it being a stupid idea.
If you want to revisit it and dig it up and get it working again, more
power to you. I'll not foam, but laugh.
good luck,
greg k-h
next prev parent reply other threads:[~2005-02-03 5:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 22:56 Pavel Roskin
2005-02-02 23:07 ` Greg KH
2005-02-02 23:23 ` Patrick Mochel
2005-02-02 23:29 ` Greg KH
2005-02-03 0:07 ` Pavel Roskin
2005-02-03 0:30 ` Greg KH
2005-02-03 4:54 ` Zan Lynx
2005-02-03 5:07 ` Greg KH [this message]
2005-02-03 8:59 ` Helge Hafting
2005-02-03 15:12 ` Alan Cox
2005-02-03 17:26 ` Theodore Ts'o
2005-02-03 13:47 ` linux-os
2005-02-04 16:05 ` David Woodhouse
2005-02-03 0:09 ` Joseph Pingenot
2005-02-03 1:13 ` Pavel Roskin
2005-02-03 2:50 ` Kyle Moffett
2005-02-03 3:17 ` Jon Masters
2005-02-06 7:24 ` Lee Revell
2005-02-07 16:05 ` Chris Friesen
2005-02-07 16:55 ` linux-os
2005-02-07 18:58 ` jerome lacoste
2005-02-07 19:35 ` linux-os
2005-02-07 16:55 ` Randy.Dunlap
2005-02-08 1:40 ` Horst von Brand
2005-02-03 4:57 ` Greg KH
2005-02-03 8:41 ` Arjan van de Ven
2005-02-03 21:00 ` Ben Greear
2005-02-04 9:20 ` Andrew Morton
2005-02-04 9:40 ` Arjan van de Ven
2005-02-15 1:41 ` Alan Cox
2005-02-03 4:08 Jonathan A. George
2005-02-03 5:07 ` Kyle Moffett
2005-02-03 12:30 Jonathan A. George
2005-02-04 15:16 ` Adrian Bunk
2005-02-17 23:13 parker
2005-02-18 3:32 ` Chris Friesen
2005-02-18 13:13 ` Arjan van de Ven
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=20050203050742.GA17909@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=proski@gnu.org \
--cc=zlynx@acm.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
Powered by JetHome