linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: alebas@televes.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Full duplex, MDIO and both Ethernet in MPC8272ADS
Date: Wed, 29 Sep 2004 10:33:27 +0200	[thread overview]
Message-ID: <1096446806.32438.5.camel@linpc003.aimsys.nl> (raw)
In-Reply-To: <1096380738.415971420df80@webmail.televes.com:443>

On di, 2004-09-28 at 16:12, alebas@televes.com wrote:
> 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?

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.

Jaap-Jan

> 
> Best regards,
> 
> Alex.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  parent reply	other threads:[~2004-09-29  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- 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=1096446806.32438.5.camel@linpc003.aimsys.nl \
    --to=jjboor@aimsys.nl \
    --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).