From: alebas@televes•com
To: linuxppc-embedded@ozlabs•org
Subject: Full duplex, MDIO and both Ethernet in MPC8272ADS
Date: Tue, 28 Sep 2004 16:12:18 +0200 [thread overview]
Message-ID: <1096380738.415971420df80@webmail.televes.com:443> (raw)
Hi to all,
As long as I have seen (tested and surfed in the code), current
linuxppc_2.4.26_devel support for MPC8272ADS board is limited to one PHY,
without MII management support and the interface is always configured as Half
Duplex. Unfourtunately, this is little useful for me, as long as i am trying to
set up a bridge between both interfaces.
I have been also testing the Linux Reference Design, from Arabella SW, which, as
long as I have seen, has support for both PHYs, MII management and Full Duplex.
So, is there any plan to merge any of Arabella's changes into the ppc tree? Or
is there anyone currently working on that ethernet stuff for current 2.4.26
tree? Is it planned to provide a patch soon?
Best regards,
Alex.
next reply other threads:[~2004-09-28 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 14:12 alebas [this message]
2004-09-28 17:04 ` Full duplex, MDIO and both Ethernet in MPC8272ADS Matt Porter
2004-09-29 8:33 ` Jaap-Jan Boor
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 6:41 full duplex, mdio and both ethernet in mpc8272ads Bastos Fernandez Alexandre
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='1096380738.415971420df80@webmail.televes.com:443' \
--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