linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: <nick@snowman.net>
Cc: Kip Macy <kmacy@netapp.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Thu, 14 Jun 2001 14:37:35 -0700 (PDT)	[thread overview]
Message-ID: <15145.11935.992736.767777@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0106141731030.16013-100000@ns>
In-Reply-To: <Pine.GSO.4.10.10106141426170.6619-100000@orbit-fe.eng.netapp.com> <Pine.LNX.4.21.0106141731030.16013-100000@ns>


nick@snowman.net writes:
 > Erm, that is going to be a problem.  Crypto benifits more from open source
 > than any other market segment, and binary only drivers for linux are not
 > the way to go.  I guess I need to get rid of my 5-10 3cr990s and replace
 > them with someone else's product?

Many of us on the networking developer team believe that making the
programming interface to the cpus on the Tigon3 is the biggest mistake
3com could ever make.

What made the Acenic so ubiquitous and interesting was that you could
program the firmware on the board to do whatever you like.  They even
provided an entire firmware developer kit so you could hack on it.

So many useful projects came from this capability.

I feel dirty working on the Tigon3 driver for 2.4.x because of this.

Later,
David S. Miller
davem@redhat.com

  parent reply	other threads:[~2001-06-14 21:38 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
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 [this message]
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=15145.11935.992736.767777@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=kmacy@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@snowman.net \
    --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).