From: Grant Likely <glikely@gmail.com>
To: Sylvain Munaut <tnt@246tnt.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Lite5200 full duplex support
Date: Thu, 17 Feb 2005 15:35:14 -0700 [thread overview]
Message-ID: <528646bc05021714356238ff35@mail.gmail.com> (raw)
In-Reply-To: <528646bc05021714135dcb1d01@mail.gmail.com>
On Thu, 17 Feb 2005 15:13:33 -0700, Grant Likely <glikely@gmail.com> wrote:
> On Wed, 16 Feb 2005 21:46:09 +0100, Sylvain Munaut <tnt@246tnt.com> wrote:
> > Grant Likely wrote:
> >
> > >BTW, here's what I changed:
> > >drivers/net/fec_mpc52xx/fec_phy.c line 294 (phy_info_lxt971)
> > >from:
> > > { mk_mii_write(MII_REG_ANAR, 0x0A1), NULL }, /* 10/100, HD */
> > >to:
> > > { mk_mii_write(MII_REG_ANAR, 0x1E1), NULL }, /* 10/100, HD */
> > >
> > >
> > >
> > I'm not sure actually. I also wondered and forgot to ask the author. I guess
> > I always tought there was a problem with it without checking.
> >
> I've played around with it a bit more and I have discovered one
> problem. When in full duplex the carrier detect seems to bounce up
> and down for every frame received off the wire. I've beaten the tar
> out of it with netperf and it doesn't seem to be causeing any
> instability (yet)... Still investigating.
>
Update: The error seems to be carrier sense loss during transmit. The
FEC documentation states that carrier loss errors are counted, but the
frame is not retransmitted and no interrupt is generated. The driver
copies the value directly out of the counter register when reporting
status.
I do not know yet if it affects received frames...
Cheers,
g.
> Cheers,
> g.
>
next prev parent reply other threads:[~2005-02-17 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 23:48 Lite5200 full duplex support Grant Likely
2005-02-16 20:46 ` Sylvain Munaut
[not found] ` <528646bc05021714135dcb1d01@mail.gmail.com>
2005-02-17 22:35 ` Grant Likely [this message]
2005-02-18 17:20 ` Dale Farnsworth
2005-02-18 19:28 ` cpclark
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=528646bc05021714356238ff35@mail.gmail.com \
--to=glikely@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tnt@246tnt.com \
/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).