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: Sun, 09 Dec 2007 17:45:13 +0100 [thread overview]
Message-ID: <475C1B99.9040403@discworld.dascon.de> (raw)
In-Reply-To: <20071209092122.GB22305@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD wrote:
> You're right the speed depends on the switch, and as example for the marvell
> 88E6031/88E6060 this speed/duplex is determine by pull-up at the switch reset
> (CPU port) and could be read through the MDIO bus but not modify.
>
> You could also have a tree of switch that need to be configured and not
> only forced the cpu port speed/duplex at 100/FULL.
>
I have one of these - the MII bus is forced to 100/FULL, and the switch
configuration happens in the reset_phy function.
I could imagine some setup where the MII bus needs to be set to
100/HALF, but probably only for PHYs that lack MDIO configuration and
not for switches.
>> Change the CONFIG_MII_ETHSWITCH to CONFIG_FIXED_PHY (as done in Linux)
>> and I'll be happy. Later on we need to change things to have port-wise
>> granularity, but we're not there yet.
>>
>
> As I said before each as it's own way to determine the speed/duplex do
> it as hard-code is not the best way.
> I will prefer an external function that take care of the switch that
> could me merge with the new phylib after.
>
Now I understand what you wanted. Lets just decide which way it whould
be done for now (before we have the PHY library), so I can modify the
patch accordingly.
For the general case, the code will need to pass the number of the
ethernet port - there may be configurations with one MII connected to a
switch with hardwired speed, and one MII connedted to a normal
single-port PHY.
cu
Michael
prev parent reply other threads:[~2007-12-09 16:45 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
2007-12-09 0:44 ` Ben Warren
2007-12-09 9:21 ` Jean-Christophe PLAGNIOL-VILLARD
2007-12-09 16:45 ` Michael Schwingen [this message]
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=475C1B99.9040403@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox