From: Chris Friesen <cfriesen@nortel.com>
To: parker@citynetwireless.net
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Please open sysfs symbols to proprietary modules
Date: Thu, 17 Feb 2005 21:32:17 -0600 [thread overview]
Message-ID: <421561C1.1050406@nortel.com> (raw)
In-Reply-To: <20050217231304.GA18940@core.citynetwireless.net>
parker@citynetwireless.net wrote:
> On Thu, 03 Feb 2005 09:41:00 +0100, Arjan van de Ven <arjan@infradead.org> wrote:
>>I suggest you talk to a lawyer and review the general comments about
>>binary modules with him (http://people.redhat.com/arjanv/COPYING.modules
>>for example). You are writing an addition to linux from scratch, and it
>>is generally not considered OK to do that in binary form (I certainly do
>>not consider it OK).
> So what about companies like ImageStream who write proprietary Linux network
> drivers for their hardware from scratch with no previous ports from another OS?
Obviously he doesn't consider that to be okay, and those companies are
taking a risk that someone will take legal action against them.
Chris
next prev parent reply other threads:[~2005-02-18 3:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 23:13 parker
2005-02-18 3:32 ` Chris Friesen [this message]
2005-02-18 13:13 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2005-02-03 12:30 Jonathan A. George
2005-02-04 15:16 ` Adrian Bunk
2005-02-03 4:08 Jonathan A. George
2005-02-03 5:07 ` Kyle Moffett
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
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
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=421561C1.1050406@nortel.com \
--to=cfriesen@nortel.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parker@citynetwireless.net \
/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