From: Roland Dreier <roland@topspin.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Greg KH <greg@kroah.com>,
openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Sat, 09 Oct 2004 14:11:06 -0700 [thread overview]
Message-ID: <52k6tzlhqt.fsf@topspin.com> (raw)
In-Reply-To: <416767BA.1020204@pobox.com> (Jeff Garzik's message of "Sat, 09 Oct 2004 00:23:22 -0400")
Jeff> If there is questionable code, that is _not_ a justification
Jeff> to add more.
I guess my point was not that the bluetooth stack is somehow
questionable, but rather that the IP policies of a standards bodies
are really not a good reason to keep code out of the kernel. If
someone can name one patent that the IB driver stack looks like it
might possibly run into, then we would have to take that very
seriously. However, no one has done this here -- all we have is FUD
or guilt by association or whatever you want to call it.
The mere fact that the IBTA bylaws only require members license their
patents under RAND terms shouldn't be an issue. If nothing else, the
fact that there are hugely more non-IBTA member companies than member
companies who might have patents makes the IBTA bylaws almost a moot
point.
For what its worth, I know of at least five companies shipping IB
stacks and the only patent licensing that I know of is the Microsoft
SDP license, and even that is really just CYA: all Microsoft says is
that they _might_ have patents that cover SDP and that they will
license them at no cost to anyone who wants them; unfortunately this
license is not GPL-compatible, but for proprietary stacks the
zero-cost terms look fine. There are people who have looked at
Microsoft's patents and concluded that none of them actually apply to
SDP as specified by the IBTA.
Thanks,
Roland
next prev parent reply other threads:[~2004-10-09 21:12 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
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 [this message]
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=52k6tzlhqt.fsf@topspin.com \
--to=roland@topspin.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.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