public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 08 Oct 2004 20:09:50 -0700	[thread overview]
Message-ID: <52zn2wlh8h.fsf@topspin.com> (raw)
In-Reply-To: <41673772.9010402@pobox.com> (Jeff Garzik's message of "Fri, 08 Oct 2004 20:57:22 -0400")

    Jeff> Read the member agreement :) It -explicitly- does -not-
    Jeff> require waiving of patent claims related to any
    Jeff> implementation of IB.

    Jeff> That's different from ATA, SCSI, USB, the list goes on...

Fair enough, but read the Bluetooth SIG patent agreement [1].  As far
as I can tell, all it requires is that other SIG members receive a
patent license.  Do we need to do rm -rf net/bluetooth?  IEEE only
requires that patents be licensed under RAND terms (it does not even
require royalty free licensing) [2].  Time for rm -rf drivers/ieee1394?

The code that we have written so far is pretty standard driver code,
so I have a hard time believing that the IB drivers are any more at
risk than any other Linux code.  There may be good and valid reasons
not to merge IB drivers upstream, but I'd be very disappointed if this
FUD about patents is what keeps them out.

Thanks,
  Roland

[1]  https://www.bluetooth.org/foundry/sitecontent/document/Patent_and_Copyright_License_Agreement

[2]  http://standards.ieee.org/guides/bylaws/sect6-7.html#6

  reply	other threads:[~2004-10-09  3:09 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 [this message]
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=52zn2wlh8h.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