public inbox for u-boot@lists.denx.de
 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 Generic PHY in macb
Date: Fri, 22 Feb 2008 16:46:36 +0100	[thread overview]
Message-ID: <47BEEE5C.1020206@discworld.dascon.de> (raw)
In-Reply-To: <20080222163403.1b2566ca@dhcp-252-066.norway.atmel.com>

Haavard Skinnemoen wrote:
> Right. We might need to add support for such PHYs, but just disabling
> the sanity check is far from enough.
>   
Agreed - in the case of a single MII-connected TP PHY, we really need 
working MDIO (or some replacement). For special cases (100BaseF fiber, 
which is always fixed speed and duplex), some equivalent to Linux' fixed 
phy handling would be needed.

>> The chip may do autonegotiation by default, however, the MAC driver 
>> still needs to know about the negotiated speed/duplex, so unless there 
>> is some board-specific way to read those (eg. by GPIO pins), only one 
>> speed/duplex will work and all other modes will be broken. This is 
>> different from the case with the hardwired ethernet switch - in case of 
>> the switch, we know that the MII port is always running at 100Mbps, 
>> full-duplex.
>>     
>
> Hmm...most switches support autonegotiation don't they? If not, what
> happens if you plug in in an old computer with a 10Mbps ethernet board?
>   
The switches support autonegotiation on the TP ports. The internal MII 
port which connects them to the CPU/MAC is usually run at fixed 100Mbps 
full-duplex.

If the switch has MDIO, you can quary the status of the external PHYs - 
however, from the point of the MAC driver, that is useless, you need to 
assume that the MII link is always up, since there is no autonegotiation 
on the MII bus.

Older switches (I have worked with the Marvell M88E6050) do not even 
have MDIO - the MII runs fixed, and the TP ports can either 
autonegotiate, or can be set to fixed 10/100/halfduplex operation using 
strapping pins.

cu
Michael

  reply	other threads:[~2008-02-22 15:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 12:27 [U-Boot-Users] [PATCH] Add support for Generic PHY in macb Michael Trimarchi
2008-02-22 12:52 ` Haavard Skinnemoen
2008-02-22 14:05   ` michael
2008-02-22 14:39     ` Haavard Skinnemoen
2008-02-22 15:05   ` Michael Schwingen
2008-02-22 15:34     ` Haavard Skinnemoen
2008-02-22 15:46       ` Michael Schwingen [this message]
2008-02-26  1:23       ` Ben Warren
  -- strict thread matches above, loose matches on Subject: below --
2008-02-22 16:19 Michael Trimarchi
2008-02-26  1:30 ` Ben Warren
2008-02-22 16:02 Michael Trimarchi
2008-02-22 16:08 ` Haavard Skinnemoen
2008-02-22 16:22   ` Michael Schwingen
2008-02-23 12:23   ` michael
2008-02-24  9:10     ` Michael Schwingen
2008-02-24 13:30       ` trimarchi at gandalf.sssup.it
2008-02-24 16:36         ` Michael Schwingen
2008-02-24 17:48           ` trimarchi at gandalf.sssup.it
2008-02-24 18:24         ` Andy Fleming
2008-02-22 14:07 Michael Trimarchi
2008-02-22 12:29 Michael Trimarchi
2008-02-22 11:41 michael
2008-02-22 12:16 ` Haavard Skinnemoen

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=47BEEE5C.1020206@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