linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: duncanp@research.canon.com.au
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Embedded planet 860T CLLF HELP!
Date: Tue, 25 Jan 2000 00:05:21 -0500	[thread overview]
Message-ID: <388D2F11.5B6EC6ED@netx4.com> (raw)
In-Reply-To: 20000125043638.22DD31B3F8@elph.research.canon.com.au


duncanp@research.canon.com.au wrote:

> This works well for me - thanks.

Good.  Just remember, playing with two physical Ethernet ports
is sometimes a challenge....make sure you use separate network
numbers :-).

I had the chance to use a 66 MHz 860P CLLF.  I ran a TCP
source/sink set of programs between my iMac and the CLLF.  The
TCP/IP interface ran 30 Mbits/sec, so we are getting there.
I am assuming the CLLF was the slow end, I guess I will try
my G4 and make sure :-).


> If you haven't done any more work on this, i'll be happy to have a look
> at neatening things up.

I wouldn't spend any time right now.  The QS6612 has been
discontinued and Embedded Planet is changing the PHY.  We can
update the driver when the new PHY appears, and I will keep
you in mind :-).

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-25  5:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19991230.21564500@alanm.penguinpowered.com>
1999-12-30 22:38 ` Embedded planet 860T CLLF HELP! Dan Malek
1999-12-31  0:24   ` David Clear
     [not found]     ` <386BF96A.52C62EA1@uswest.net>
1999-12-31  0:33       ` Dan Malek
1999-12-31  0:59       ` Alan Mimms
2000-01-14  0:23   ` Graham Stoney
2000-01-14  0:46     ` Dan Malek
2000-01-14  2:56       ` Graham Stoney
2000-01-19  4:07       ` duncanp
2000-01-19 16:45         ` Dan Malek
2000-01-25  4:33           ` duncanp
2000-01-25  5:05             ` Dan Malek [this message]
2000-01-20 20:13 Ralf HECKHAUSEN
2000-01-20 21:36 ` Dan Malek

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=388D2F11.5B6EC6ED@netx4.com \
    --to=dan@netx4.com \
    --cc=duncanp@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).