mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Michael Krause <krause@cup.hp.com>
Cc: openib-general@openib.org, linux-kernel@vger.kernel.org
Subject: Re: [openib-general] InfiniBand incompatible with the Linux kernel?
Date: Mon, 11 Oct 2004 12:27:48 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0410111226460.17999@linux.site> (raw)
In-Reply-To: <6.1.2.0.2.20041008152933.01f671a8@esmail.cup.hp.com>



On Fri, 8 Oct 2004, Michael Krause wrote:

> Spec for free or spec for a price - neither grants anyone rights to any
> IP contained within the specifications or on the technologies that
> surround the specification.  The change in spec cost, while clearly
> unfortunate, has no impact on the IP rights.  IP rights are defined by
> the IBTA membership agreement (just like they are for PCI and any number
> of other technologies used within the industry).  If you want to
> implement a technology, then you have to be a member of the appropriate
> organization and agree to the same industry-wide terms that others do.  
> Hence, this problem is not IB-specific but a fact of life within the
> industry.

funny, I don't recall these problems with Ethernet. 


> Again, this is true of many technologies not just IB.  For example, if a
> company has patents on PCI Express and someone implements a device /
> chipset / whatever and they are not part of the PCI-SIG, then they can
> be subject to different terms than someone who is a member of the
> PCI-SIG.  In both cases, the access to specs, etc. has nothing to do
> with IP licensing.

sorry, I think about protocol software differently than chips. Maybe I'm 
thinking incorrectly here.

ron

      parent reply	other threads:[~2004-10-11 18:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 20:22 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
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 [this message]

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=Pine.LNX.4.58.0410111226460.17999@linux.site \
    --to=rminnich@lanl.gov \
    --cc=krause@cup.hp.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

all inboxes | Powered by JetHome®