All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: AMCC 440EP phy detection
Date: Tue, 07 Apr 2009 17:10:55 -0700	[thread overview]
Message-ID: <49DBEB8F.2040307@embeddedarm.com> (raw)
In-Reply-To: <fa686aa40904071011n22084931wc8900606fd62f167@mail.gmail.com>

Hello,

Thanks for the suggestions :)

I found the ibm_newemac driver(2.6.29) makes the assumption that the bootloader 
has already configured the tx enable pin as it is a multiplexed pin. 
Unfortuantley I am not using U-Boot and our minimal bootloader does not do this. 
  After finding tx enable was never asserting for Eth0 a quick user space 
program verified tx enable was configured as a GPIO pin.

> On Tue, Apr 7, 2009 at 9:32 AM, Eddie Dawydiuk <eddie@embeddedarm.com> wrote:
>> Hello,
>>
>> I'm working on a board based on the Yosemite AMCC 440EP eval board. I'm
>> having some difficulty getting both network interfaces working. The first
>> problem I found is the ibm_newemac driver was detecting the two phys at
>> address 0 and 1 where we have them wired for addresses 1 and 3. As a result
>> I hardcoded the phy-address in the dts file. I then found I was able to
>> receive and send data on eth1(phy-address 3) without incident. Although I
>> found eth0 can receive data but I see no packets being transmitted(using a
>> packet sniffer) and I see no indication from a software standpoint of any
>> transmit failures. We are using Micrel KSZ8041FTL phys(RMII mode) where the
>> Yosemite board used Micrel KS8721BL phys.  I've reviewed the schematic and
>> it appears both phys are connected identically and I've seen this same
>> failure on multiple boards. I thought the fact that the driver detected a
>> phy at address 0 might be a clue, but I can't make much of the clue. So I
>> thought I'd post this info in the hopes someone else might have run into a
>> similar problem or have a suggestion.
> 
> Phy address 0 is the broadcast address.  All phys will usually respond
> to address 0 accesses.  Off the top of my head, It sounds like one PHY
> is responding to addresses 0 & 1, and the other phy isn't responding
> at all.
> 
> g.
> 


-- 
Best Regards,
________________________________________________________________
  Eddie Dawydiuk, Technologic Systems | voice:  (480) 837-5200
  16525 East Laser Drive 	     | fax:    (480) 837-5300
  Fountain Hills, AZ 85268            | web: www.embeddedARM.com

  parent reply	other threads:[~2009-04-08  0:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 16:32 AMCC 440EP phy detection Eddie Dawydiuk
2009-04-07 16:47 ` Feng Kan
2009-04-07 18:20   ` Eddie Dawydiuk
2009-04-07 17:11 ` Grant Likely
2009-04-07 17:18   ` Stefan Roese
2009-04-08  0:10   ` Eddie Dawydiuk [this message]
2009-04-08 15:47     ` Eddie Dawydiuk
2009-04-08 16:01       ` Stefan Roese
2009-04-08 17:00         ` Grant Likely
2009-04-08 18:19           ` Stefan Roese
2009-04-08 18:35             ` Eddie Dawydiuk

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=49DBEB8F.2040307@embeddedarm.com \
    --to=eddie@embeddedarm.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.