From: "John W. Linville" <linville@tuxdriver.com>
To: Steve.Glendinning@smsc.com
Cc: Bahadir Balban <Bahadir.Balban@arm.com>,
ian.saturley@smsc.com, netdev@vger.kernel.org,
Francois Romieu <romieu@fr.zoreil.com>,
Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH] SMSC LAN911x and LAN921x vendor driver
Date: Wed, 2 Aug 2006 15:51:33 -0400 [thread overview]
Message-ID: <20060802195128.GA7204@tuxdriver.com> (raw)
In-Reply-To: <OF9CB563CF.865D1AC6-ON802571BE.006924E4-802571BE.006A884B@smsc.com>
On Wed, Aug 02, 2006 at 08:23:40PM +0100, Steve.Glendinning@smsc.com wrote:
> > Does this need the magic "for (addr=1; addr <=32; addr++)" trick that
> > has become idiomatic for PHY discovery in our drivers?
>
> I don't understand the question - surely 32 is not a valid PHY address?
That's why it is magic! :-)
The idea is to probe PHY addr 0 last in the series. Apparently some
PHYs don't like seeing addr 0 or somesuch, so you try it last to avoid
screwing them up. It may well be folklore and legend at this point.
Still, you will find several examples in the various drivers.
The sundance driver is one example.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-08-02 19:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7ac1e90c0607140711p4529d4fbh98d3e9edf2c7a52f@mail.gmail.com>
2006-07-14 18:50 ` smsc911x driver Stephen Hemminger
2006-07-28 11:48 ` SMSC LAN911x and LAN921x vendor driver Steve Glendinning
2006-07-28 14:31 ` Stephen Hemminger
2006-07-28 21:38 ` Francois Romieu
2006-07-29 0:38 ` Stephen Hemminger
2006-07-31 20:20 ` Steve.Glendinning
2006-08-01 15:12 ` [PATCH] " Steve Glendinning
2006-08-01 15:33 ` John W. Linville
2006-08-02 19:23 ` Steve.Glendinning
2006-08-02 19:51 ` John W. Linville [this message]
2006-08-01 18:28 ` Scott Murray
2006-08-01 19:27 ` Steve.Glendinning
2006-08-01 23:51 ` Scott Murray
2006-08-03 15:26 ` Steve.Glendinning
2006-08-03 21:07 ` Scott Murray
2006-08-01 21:40 ` Francois Romieu
2006-08-02 19:39 ` Steve.Glendinning
2006-08-02 21:07 ` Francois Romieu
2006-08-04 11:29 ` Steve Glendinning
2006-12-04 22:31 Steve Glendinning
-- strict thread matches above, loose matches on Subject: below --
2006-12-30 16:34 Steve Glendinning
2007-01-04 14:42 ` Pierre TARDY
2007-07-16 18:54 Steve Glendinning
2007-07-18 22:38 ` Jeff Garzik
2007-07-20 16:22 ` Steve.Glendinning
2007-07-29 20:53 ` Peter Korsgaard
2007-07-30 18:31 ` Steve.Glendinning
2007-08-01 22:27 ` Peter Korsgaard
2007-08-07 23:09 ` Peter Korsgaard
[not found] <20080515170728.GA3176@PTXN0038.genpitfi01.og.ge.com>
2008-05-19 12:34 ` Steve Glendinning
2008-05-19 16:24 ` Catalin Marinas
2008-05-19 19:06 ` Steve.Glendinning
2008-06-02 10:45 ` Steve Glendinning
2008-06-02 15:54 ` Ben Hutchings
2008-06-02 16:09 ` Bill Gatliff
2008-06-02 18:32 ` Peter Korsgaard
2008-06-02 18:30 ` Steve.Glendinning
2008-06-02 19:03 ` Ben Hutchings
2008-06-04 16:34 ` Steve.Glendinning
2008-06-02 18:47 ` Peter Korsgaard
2008-10-21 13:00 Steve Glendinning
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=20060802195128.GA7204@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Bahadir.Balban@arm.com \
--cc=Steve.Glendinning@smsc.com \
--cc=ian.saturley@smsc.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@osdl.org \
/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).