linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Moerman <linuxham@4us.org>
To: Pekka Pietikainen <pp@evil.netppl.fi>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Sat, 16 Jun 2001 11:12:15 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0106161110420.5331-100000@root.4us.org> (raw)
In-Reply-To: <20010615185235.A29313@netppl.fi>



On Fri, 15 Jun 2001, Pekka Pietikainen wrote:

> On Fri, Jun 15, 2001 at 08:37:15AM -0700, David S. Miller wrote:
> > 
> > Pete Wyckoff writes:
> >  > We're currently working on using both processors
> >  > of the Tigon in parallel.
> > 
> > It is my understanding that on the Tigon2, the second processor is
> > only for working around hw bugs in the DMA controller of the board and
> > cannot be used for other tasks.
> > 
> > WRT. tigon3, it was mentioned on this list that it is a pair of arm9
> > cpus, one for rx and one for tx.
> > 
> Might be worth asking broadcom instead of 3com for the specs, 
> as they seem to be selling it as a chip (BCM5700/5701), whereas 3com sells a
> board (3c996).
> 

Guys,

To make it easier, Tell me exactly what you need in documentation and I
will try to get it for you. 

Martin Moerman
martin_moerman@eur.3com.com




> -- 
> Pekka Pietikainen
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2001-06-16  9:12 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 [this message]
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.LNX.4.21.0106161110420.5331-100000@root.4us.org \
    --to=linuxham@4us.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pp@evil.netppl.fi \
    /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).