linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: "David S. Miller" <davem@redhat.com>
Cc: Pete Wyckoff <pw@osc.edu>,
	nick@snowman.net, Kip Macy <kmacy@netapp.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: 25 Jun 2001 17:42:59 +0200	[thread overview]
Message-ID: <d366dkefb0.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <15145.11935.992736.767777@pizda.ninka.net> <Pine.LNX.4.21.0106141739140.16013-100000@ns> <15145.12192.199302.981306@pizda.ninka.net> <20010615111213.C2245@osc.edu> <15146.11179.315190.615024@pizda.ninka.net>
In-Reply-To: "David S. Miller"'s message of "Fri, 15 Jun 2001 08:37:15 -0700 (PDT)"

>>>>> "David" == David S Miller <davem@redhat.com> writes:

David> Pete Wyckoff writes:
>> We're currently working on using both processors of the Tigon in
>> parallel.

David> It is my understanding that on the Tigon2, the second processor
David> is only for working around hw bugs in the DMA controller of the
David> board and cannot be used for other tasks.

Actually it was intended to be used for other stuff but they ended up
having to use it for workarounds.

Jes

  parent reply	other threads:[~2001-06-25 15:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:24 3com Driver and the 3XP Processor 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
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 [this message]
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=d366dkefb0.fsf@lxplus015.cern.ch \
    --to=jes@sunsite.dk \
    --cc=davem@redhat.com \
    --cc=kmacy@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@snowman.net \
    --cc=pw@osc.edu \
    /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;
as well as URLs for NNTP newsgroup(s).