All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH: add support for MII-connected	ethernet switch for IPX42x
Date: Sat, 08 Dec 2007 23:22:11 +0100	[thread overview]
Message-ID: <475B1913.7040902@discworld.dascon.de> (raw)
In-Reply-To: <20071208124024.GA32116@game.jcrosoft.org>

Jean-Christophe PLAGNIOL-VILLARD wrote:
> 	If you have a switch between your phy and your cpu the speed and
> 	the duplex must be specified by the phy driver.
>   
Which PHY driver? The NPE code directly calls miiphy_read to acces 
standard PHY registers, so where does a PHY driver come into play here?

> 	The best way is to add a function that request the phy status
> 	and do not wait the phy autonegociation like done in the kernel
> 	by read_status callback and it's implementation
> 	genphy_read_status.
>   
I do not really see how that should work, for multiple reasons:
 - speed/duplex on the MII bus depend on the attached switch and may be 
different from the speed/duplex on any of the PHYs that are attached to 
the switch.
 - most switches (Marvell 88E6060 or similar) have multiple downstream 
ports with PHYs - which one should I poll to get useful information? 
Simply waiting for a link on any port will not guarantee that this is 
the port via which the server is connected, so polling anything is 
pretty useless IMHO.
 - there are switches (Marvell 88E6050) that have no MDIO interface - 
they have a fixed MII speed/duplex, and the CPU has no way to know about 
the status of any of the PHYs.

I am a bit confused - could you please clarify in what direction the 
code should evolve to solve these problems better than my patch does?

cu
Michael

  reply	other threads:[~2007-12-08 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10 15:34 [U-Boot-Users] PATCH: add support for MII-connected ethernet switch for IPX42x Michael Schwingen
2007-12-08 12:40 ` Jean-Christophe PLAGNIOL-VILLARD
2007-12-08 22:22   ` Michael Schwingen [this message]
2007-12-09  0:44     ` Ben Warren
2007-12-09  9:21       ` Jean-Christophe PLAGNIOL-VILLARD
2007-12-09 16:45         ` Michael Schwingen

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=475B1913.7040902@discworld.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.