From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Roland Dreier <roland@topspin.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Greg KH <greg@kroah.com>,
openib-general@openib.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Sun, 10 Oct 2004 20:05:32 +0100 [thread overview]
Message-ID: <1097435131.29422.7.camel@localhost.localdomain> (raw)
In-Reply-To: <52k6tzlhqt.fsf@topspin.com>
On Sad, 2004-10-09 at 22:11, Roland Dreier wrote:
> 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.
Its called "caution". It's why nobody does innovation in the USA any
more, its too dangerous to innovate. Far better to make it available as
before with a blue led and a beeper.
> 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.
The big question seems to be about the standard itself. Are the items at
issue hardware or software ? We already deal with a lot of devices that
have hardware related patent pools and those by themselves don't seem to
cause problems.
In the mean time I guess the guys down in Bristol[1] will be feeling
happier and happier at the Infiniband self destruct sequence.
Alan
[1] Quadrics
next prev parent reply other threads:[~2004-10-10 20:08 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
2004-10-10 19:05 ` Alan Cox [this message]
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=1097435131.29422.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.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