From: Grant Likely <glikely@gmail.com>
To: Sylvain Munaut <tnt@246tnt.com>, linuxppc-embedded@ozlabs.org
Subject: Lite5200 full duplex support
Date: Tue, 15 Feb 2005 16:48:19 -0700 [thread overview]
Message-ID: <528646bc05021515486bd9f926@mail.gmail.com> (raw)
I'm using Sylvain's http://bkbits.246tnt.com:14690/linux-2.5-mpc52xx
bk tree on a lite5200 evb. I noticed that the FEC driver is hard
coded to only support half duplex 10/100 auto-negotiation. Is that
intentional? Are there any known problems with running full duplex?
I modified the code to allow full duplex and I haven't observed any
problems yet. (w/ nfsroot and compiling apps on the target natively)
Cheers,
g.
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 */
next reply other threads:[~2005-02-15 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 23:48 Grant Likely [this message]
2005-02-16 20:46 ` Lite5200 full duplex support Sylvain Munaut
[not found] ` <528646bc05021714135dcb1d01@mail.gmail.com>
2005-02-17 22:35 ` Grant Likely
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=528646bc05021515486bd9f926@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).