From: Greg KH <greg@kroah.com>
To: Roland Dreier <roland@topspin.com>
Cc: openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Fri, 8 Oct 2004 16:34:50 -0700 [thread overview]
Message-ID: <20041008233450.GA1490@kroah.com> (raw)
In-Reply-To: <528yagn63x.fsf@topspin.com>
On Fri, Oct 08, 2004 at 04:27:14PM -0700, Roland Dreier wrote:
> The increase in cost for the spec is rather unfortunate but I think
> it's orthogonal to any IP issues. Since the Linux kernel contains a
> lot of code written to specs available only under NDA (and even
> reverse-engineered code where specs are completely unavailable), I
> don't think the expense should be an issue.
It isn't at all, just an odd side point.
> As for IP, as far as I know, there has been no change to any of the
> bylaws or other members agreements.
The "purchase a spec" agreement has changed, right?
> If there is some specific
> provision that concerns you, please bring it to our attention -- the
> IBTA in general and the IBTA steering committee in general have been
> very supportive of the OpenIB effort. In fact, most of the IBTA
> steering commitee companies (Agilent, HP, IBM, InfiniCon, Intel,
> Mellanox, Sun, Topspin, and Voltaire) have been active participants in
> OpenIB development. I would hope we can resolve any issues relating
> to open source and the Linux kernel.
What about the issue of not being able to use the spec for "commercial"
applications? And doesn't the member agreement not cover anyone who
implements the spec, and then gives that implementation to someone who
is not a member?
> However, I would suspect that we'll find the USB, Firewire, Bluetooth,
> etc., etc. standards bodies all have very similar IP language in their
> bylaws and licenses.
No, the USB bylaws explicitly forbid any member company from putting in,
or trying to claim any IP that is in the USB specs. That is something
that makes USB quite different from IB.
I haven't had the misfortune to have to go read the PCI SIG bylaws and
member agreement...
thanks,
greg k-h
next prev parent reply other threads:[~2004-10-08 23:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 20:22 InfiniBand incompatible with the Linux kernel? Greg KH
2004-10-08 20:38 ` [openib-general] " Ronald G. Minnich
2004-10-08 22:49 ` Eric W. Biederman
2004-10-08 23:13 ` Greg KH
2004-10-08 23:24 ` Lee Revell
2004-10-08 23:26 ` Dave Jones
2004-10-08 23:29 ` Roland Dreier
2004-10-08 23:13 ` Jeff Garzik
2004-10-08 23:27 ` Roland Dreier
2004-10-08 23:34 ` Greg KH [this message]
2004-10-09 3:40 ` Roland Dreier
2004-10-09 0:57 ` Jeff Garzik
2004-10-09 3:09 ` Roland Dreier
2004-10-09 4:23 ` Jeff Garzik
2004-10-09 21:11 ` Roland Dreier
2004-10-10 19:05 ` Alan Cox
2004-10-10 20:33 ` Roland Dreier
2004-10-09 11:50 ` Francois Romieu
2004-10-09 20:47 ` Roland Dreier
2004-10-22 23:59 ` Troy Benjegerdes
[not found] ` <6.1.2.0.2.20041008152933.01f671a8@esmail.cup.hp.com>
2004-10-11 18:27 ` Ronald G. Minnich
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=20041008233450.GA1490@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=roland@topspin.com \
/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