linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ron Flory <ron.flory@adtran.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: Dan Malek <dan@netx4.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Need CPM clock >= 100 Mhz for fast ethernet operation
Date: Wed, 03 May 2000 14:09:20 -0500	[thread overview]
Message-ID: <39107960.9A033139@adtran.com> (raw)
In-Reply-To: m12n2oz-001SyZC@bucks


diekema_jon wrote:
>
> > From: Dan Malek <dan@netx4.com>
> > Organization: Embedded Edge, LLC
>
> > diekema_jon wrote:
> >
> > >         - What clock multiplier are you using for the CPM?
>
> > I don't remember.  I think it was clock mode 0010_011, which would
> > be 133 MHz CPM and 166 MHz core.  This is all pretty simple.  Just
> > pick your own clock speed and set the board descriptor in embed_config.c
> > to match it.
>
> In order for fast Ethernet to work reliably, the CPM clock needs to be
> >= 100 Mhz.
>
> If the CPM clock is 66 Mhz, then about 1 of 5-20 Tx packets will get
> dropped.  It also appears that Rx has precedence over Tx.  We are
> guessing that the CPM runs out of cycles at 66 Mhz while trying to
> support fast ethernet.

 ???

 I didn't think the SCC could support fast ethernet at any clock speed,
thats why moto put the FEC (Fast Ethernet Controller) in the FEC, which
supports fast ethernet at rates > 25Mhz (full duplex @ 40Mhz).

ron

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

  reply	other threads:[~2000-05-03 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-27  0:52 Baud rate problems with the EST SBC8260 board diekema_jon
2000-04-27  2:13 ` Dan Malek
2000-04-27 23:15   ` diekema_jon
2000-05-03 17:20   ` Need CPM clock >= 100 Mhz for fast ethernet operation diekema_jon
2000-05-03 19:09     ` Ron Flory [this message]
2000-05-03 19:15     ` 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=39107960.9A033139@adtran.com \
    --to=ron.flory@adtran.com \
    --cc=dan@netx4.com \
    --cc=diekema@bucks.si.com \
    --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).