From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org, joakim.tjernlund@transmode.se
Cc: scottwood@freescale.com,
Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-net@vger.kernel.org
Subject: Re: [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs.
Date: Fri, 11 Apr 2008 10:06:04 +0200 [thread overview]
Message-ID: <200804111006.04708.sr@denx.de> (raw)
In-Reply-To: <1207897589.9544.13.camel@gentoo-jocke.transmode.se>
On Friday 11 April 2008, Joakim Tjernlund wrote:
> On Thu, 2008-04-10 at 13:51 -0400, Paul Gortmaker wrote:
> > In addition to marking 0x0 as an invalid PHY ID, I've also
> > changed the existing somewhat useless printk to actually
> > list the bus IDs where it found a PHY so we get a basic
> > bus summary.
>
> PHY ID 0x0 isn't an invalid id, I got a Broadcom PHY that has
> PHY ID=0. Maybe I am misunderstanding something?
IIRC, address 0 is the PHY broadcast address, but can be used without problem
with some PHY's. I remember some designs were we had the PHY at address 0.
Best regards,
Stefan
next prev parent reply other threads:[~2008-04-11 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 17:51 [PATCH 0/5] dynamic detection of gianfar TPIPA Paul Gortmaker
2008-04-10 17:51 ` [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs Paul Gortmaker
2008-04-10 17:51 ` [PATCH 2/5] gianfar: assign mii_bus value in dev->priv Paul Gortmaker
2008-04-10 17:52 ` [PATCH 3/5] gianfar: limit scope of gfar_local_mdio functions Paul Gortmaker
2008-04-10 17:52 ` [PATCH 4/5] gianfar: dont hog the mii_bus->priv with just the regs Paul Gortmaker
2008-04-10 17:52 ` [PATCH 5/5] gianfar: don't hard code the TBIPA MDIO address Paul Gortmaker
2008-04-11 7:06 ` [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs Joakim Tjernlund
2008-04-11 8:06 ` Stefan Roese [this message]
2008-04-11 10:47 ` Joakim Tjernlund
2008-04-11 13:54 ` Grant Likely
2008-04-10 22:17 ` [PATCH 0/5] dynamic detection of gianfar TPIPA David Miller
2008-04-10 23:30 ` Andy Fleming
2008-04-11 3:34 ` Paul Gortmaker
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=200804111006.04708.sr@denx.de \
--to=sr@denx.de \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-net@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paul.gortmaker@windriver.com \
--cc=scottwood@freescale.com \
/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).