linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dean Matsen <deanm@earthlink.net>
To: Dan Malek <dan@embeddededge.com>
Cc: Eugene Surovegin <ebs@ebshome.net>,
	Dean Matsen <deanmatsen@earthlink.net>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ethernet PHY chip discovery not working on 855T with  971/972 chips
Date: Tue, 08 Jul 2003 22:50:49 -0700	[thread overview]
Message-ID: <3F0BAD39.9060708@earthlink.net> (raw)
In-Reply-To: <3F0BA671.1050900@embeddededge.com>


Dan Malek wrote:

>
> Eugene Surovegin wrote:
>
>> It usually means that your hw lacks pull-up on MII MDIO line.
>
>
> Yep, and even when PHYs indicate they have internal pull-ups, either
> they don't or they aren't sufficient.
>
>
> -- Dan
>
>
>
>
Yes, I see we have no pullup on that line. We do dedicated HVAC
applications, so we
don't need to do this search. Our dedicated software wouldn't talk to
the chip
at the wrong address.

Don't you think the fix from my original message should still be
considered for
integration into the kernel? It will improve the odds that the kernel can
auto-detect someone's hardware....

Thanks
Dean


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-07-09  5:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09  2:17 Ethernet PHY chip discovery not working on 855T with 971/972 chips Dean Matsen
2003-07-09  2:29 ` Dean Matsen
2003-07-09  2:56   ` Eugene Surovegin
2003-07-09  5:21     ` Dan Malek
2003-07-09  5:50       ` Dean Matsen [this message]
2003-07-09 14:37         ` Dan Malek
2003-07-09 16:39           ` Dean Matsen
2003-07-09 20:54           ` Dean Matsen
2003-07-09 21:21             ` Wolfgang Denk
     [not found]               ` <20030711151834.GU17433@ip68-0-152-218.tc.ph.cox.net>
2003-07-11 15:43                 ` Wolfgang Denk
2003-07-11 15:52                   ` Tom Rini
2003-07-11 18:29                     ` Wolfgang Denk
2003-07-11 18:50                       ` Tom Rini
2003-07-11 19:18                         ` Wolfgang Denk
2003-07-11 19:34                           ` Tom Rini
2003-07-11 21:04                             ` Wolfgang Denk
2003-07-14  6:21                         ` Pantelis Antoniou
2003-07-14  7:58                           ` Wolfgang Denk
2003-07-14 14:31                             ` Tom Rini
2003-07-14 19:26                               ` Wolfgang Denk
2003-07-15 15:04                                 ` Tom Rini
2003-07-11 23:21                 ` Dean Matsen
2003-07-12  1:01                   ` Paul Mackerras
2003-07-12 21:13                     ` Dean Matsen
2003-07-12 21:54                       ` Wolfgang Denk
2003-07-14 14:52                       ` Tom Rini
2003-07-13 15:48                     ` Dan Malek
2003-07-13 16:29                       ` Roland Dreier
2003-07-14 20:49                         ` Matt Porter
2003-07-15  5:08                           ` Roland Dreier

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=3F0BAD39.9060708@earthlink.net \
    --to=deanm@earthlink.net \
    --cc=dan@embeddededge.com \
    --cc=deanmatsen@earthlink.net \
    --cc=ebs@ebshome.net \
    --cc=linuxppc-embedded@lists.linuxppc.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).