linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@netapp.com>
To: "Brent D. Norris" <brent@biglinux.tccw.wku.edu>
Cc: Kip Macy <kmacy@netapp.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Mon, 11 Jun 2001 18:18:51 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.10.10106111812370.22254-100000@orbit-fe.eng.netapp.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0106111942080.8721-100000@biglinux.tccw.wku.edu>

I think that they are relatively friendly. However, if they publish the
interface to their card another company could come along with a card
with the same functionality and take advantage of pre-existing drivers and
undercut their price, thus taking away their margins. At least that is the
rationale I have been given and this has occurred on at least one
occasion to Adaptec. 

My opinion is that if you have to obscure your interface to protect your
margins because you are making a commodity component then you are in the
wrong business. Nonetheless they can correctly point out that they are
still making a lot more money than I am :-).

		-Kip

On Mon, 11 Jun 2001, Brent D. Norris wrote:

> I thought 3com was pretty friendly to the Linux Community, was that a
> misconception?
> 
> > It can't because 3com hasn't implemented in the driver and they won't
> > publish the interface.
> > 		-Kip
> >
> 
> Brent
> 
> Executive Advisor -- WKU-Linux
> 
> 


  reply	other threads:[~2001-06-12  1:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:24 Brent D. Norris
2001-06-12  0:29 ` Kip Macy
2001-06-12  0:43   ` Brent D. Norris
2001-06-12  1:18     ` Kip Macy [this message]
2001-06-12 16:24       ` Alan Cox
2001-06-12 16:12 ` Pavel Machek
2001-06-13 10:30   ` James Sutherland
2001-06-14 19:13     ` Brent D. Norris
2001-06-14 21:13       ` Martin Moerman
2001-06-14 21:18         ` nick
2001-06-14 21:26           ` Kip Macy
2001-06-14 21:32             ` nick
2001-06-14 21:37               ` Kip Macy
2001-06-15  2:50                 ` Dr. Kelsey Hudson
2001-06-15  2:47               ` Dr. Kelsey Hudson
2001-06-15  2:51                 ` nick
2001-06-15  4:01                   ` [OT] " Brent D. Norris
2001-06-15 14:45                   ` Alan Cox
2001-06-15 14:59                     ` Venkatesh Ramamurthy
2001-06-17 16:35                       ` Pavel Machek
2001-06-16  9:04               ` Martin Moerman
2001-06-14 21:37             ` David S. Miller
2001-06-14 21:40               ` nick
2001-06-14 21:40               ` Kip Macy
2001-06-14 21:41               ` David S. Miller
2001-06-15 15:12                 ` Pete Wyckoff
2001-06-15 15:37                 ` David S. Miller
2001-06-15 15:52                   ` Pekka Pietikainen
2001-06-16  9:12                     ` Martin Moerman
2001-06-18 14:43                   ` Jamie Lokier
2001-06-25 15:42                   ` Jes Sorensen
2001-06-14 21:45               ` David S. Miller
2001-06-14 21:48                 ` Kip Macy
2001-06-14 21:51                 ` David S. Miller
2001-06-25 15:45                 ` Jes Sorensen
2001-06-12 16:27 ` Alan Cox
2001-06-12  2:27 Brent D. Norris

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.GSO.4.10.10106111812370.22254-100000@orbit-fe.eng.netapp.com \
    --to=kmacy@netapp.com \
    --cc=brent@biglinux.tccw.wku.edu \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 3com Driver and the 3XP Processor' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).