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:05:34 +0100 [thread overview]
Message-ID: <47BEE4BE.4060805@discworld.dascon.de> (raw)
In-Reply-To: <20080222135209.026eb091@dhcp-252-066.norway.atmel.com>
Haavard Skinnemoen wrote:
> All MII-capable PHYs should have a working PHYSID1 register. If it
> doesn't, something is broken.
>
It depends - I am not sure if there are PHYs which simply do not
implement MDIO, but at least for ethernet switches, such chips do exist.
> So I think the CONFIG_GENERIC_PHY name is misleading -- the test is
> generic enough as is. CONFIG_BROKEN_PHY would be better, if there's
> really no way to get your PHY to behave.
>
Right. Or CONFIG_PHY_NO_MDIO or something like that. This is in the
direction of CONFIG_MII_ETHSWITCH which is used eg. by AcTux-2 for this
purpose.
> But note that if MDIO communication isn't working, autonegotiation
> won't work, and the speed and duplex settings will most likely be
> wrong. So I don't think simply #ifdefing out that sanity check is
> really going to solve any problems.
>
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.
cu
Michael
next prev parent reply other threads:[~2008-02-22 15:05 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 [this message]
2008-02-22 15:34 ` Haavard Skinnemoen
2008-02-22 15:46 ` Michael Schwingen
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=47BEE4BE.4060805@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