From: Bastos Fernandez Alexandre <ALEBAS@televes•com>
To: "'linuxppc-embedded@ozlabs•org'" <linuxppc-embedded@ozlabs•org>
Subject: full duplex, mdio and both ethernet in mpc8272ads
Date: Tue, 5 Oct 2004 08:41:27 +0200 [thread overview]
Message-ID: <51DB8827D393D411BB69003048003F46FDCF23@tvesntr.televes.com> (raw)
Hi,
>I use the fcc enet driver and a dual port phy using the fcc driver's mii
>implementation on a 8270, but on a propietary board design.
After your reply I checked my work. I upgraded into the last version of
linuxppc-2.4 from ppc.bkbits.net, which is version 2.4.27 of the kernel and
1.22 of the fcc_enet driver, and then MII management and Full-duplex seemed
to work.
However, the second interface were still not working. I have seen that one
reason could be the second PHY not being enabled during device init
(BCSR3_FETHIEN2), while the first PHY were. I changed it and now, i think it
works. At least, it answer and sends echoes.
Thanks
Alex Bastos
>Jaap-Jan
next reply other threads:[~2004-10-05 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 6:41 Bastos Fernandez Alexandre [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 14:12 Full duplex, MDIO and both Ethernet in MPC8272ADS alebas
2004-09-28 17:04 ` Matt Porter
2004-09-29 8:33 ` Jaap-Jan Boor
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=51DB8827D393D411BB69003048003F46FDCF23@tvesntr.televes.com \
--to=alebas@televes$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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