From: Steffen Rumler <Steffen.Rumler@siemens.com>
To: "Gérard Guével" <gguevel@interfaceconcept.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260 FCC enet driver problem
Date: Fri, 10 Oct 2003 14:25:15 +0200 [thread overview]
Message-ID: <3F86A52B.1070803@siemens.com> (raw)
In-Reply-To: 000001c38766$68b14d90$5201a8c0@GEG2400
Hi Gérard,
> I use a 2.4.18 Linux kernel on my custom 8260 board with 3 FCC ports.
> These 3 ports work fine at 100Mbs half or full duplex.
>
> I connect 2 boards on the first port via a 10Mbs hub.
> The ports auto-negotiate and fall into 10Mbs half duplex mode.
Does it mean the eth0 port has been switched from full duplex (100Mbs Switch)
to half duplex (10 Mbs Hub) by changing the Hub/Switch ?
In this case, the new duplex mode will be negotiated by the two PHYs.
But, also the MAC Controller (FCC, FPSMR(FDE) bit) must be switched to half
duplex. Otherwise, the MAC Controller continues with full duplex.
This results in late collisions. In this case, the CPCR command RESTART TRANSMIT
is necessary.
I have not seen this kind of synchronization (PHY -- MAC) in fcc_enet.c.
I don't know why.
--
--------------------------------------------------------------
Steffen Rumler
ICN CP D NT SW 7
Siemens AG
Hofmannstr. 51 Email: Steffen.Rumler@siemens.com
D-81359 Munich Phone: +49 89 722-44061
Germany Fax : +49 89 722-36703
--------------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-10 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:20 8260 FCC enet driver problem Gérard Guével
2003-10-10 12:25 ` Steffen Rumler [this message]
2003-10-13 19:30 ` 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=3F86A52B.1070803@siemens.com \
--to=steffen.rumler@siemens.com \
--cc=gguevel@interfaceconcept.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).