From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: "'Bastos Fernandez Alexandre'" <alebas@televes.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: 82xx fcc_enet problem between Linux 2.4 and 2.6
Date: Fri, 1 Sep 2006 16:26:02 +0200 [thread overview]
Message-ID: <001701c6cdd2$9221c230$5201a8c0@GEG2400> (raw)
In-Reply-To: <1157111000.44f81cd8cb6d6@webmail.televes.com:443>
Hello Alex,
> > I have ported Linux 2.6.9 on different boards and I noticed
> > that I have tx carrier errors on my FCC ports. Almost one
> > error per xmit.
> I have experienced same problem. I suppose you are using the old
> fcc driver in /arch/ppc
Yes that's right.
> > I reinstalled Linux 2.4.18 on these boards and I have NO ERROR.
> > The errors arise with PHY configured in 100M full duplex (or autoneg).
> > The FCC has the same duplex as PHY.
> Are you sure? In my case, the problem was that while the PHY had autoneg
> to full-duplex, the MAC kept in half-duplex mode
I have modified some code in fcc_enet.c for Linux 2.4 to manage PHY as I
wanted.
Perhaps was I in luck to correct something wrong. I checked that the duplex
were identical for FCC and PHY and I had no carrier error.
> > I think this is not a phy or hardware problem but rather a
> FCC configuration mismatch in fcc_enet.c.
> Yes. But I think the driver has been obsoleted by fs_enet one,
> so modifiying it now has no sense.
Yes I retreived fs_enet in Linux 2.6.15 and I'll try it.
This driver seems to appear in Linux 2.6.11 tree not before.
Is it right ?
Thanks very much for your reply.
Best regards
Laurent
prev parent reply other threads:[~2006-09-01 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 17:46 82xx fcc_enet problem between Linux 2.4 and 2.6 Laurent Lagrange
2006-09-01 11:43 ` Bastos Fernandez Alexandre
2006-09-01 14:26 ` Laurent Lagrange [this message]
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='001701c6cdd2$9221c230$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=alebas@televes.com \
--cc=linuxppc-embedded@ozlabs.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).