All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Mendham <petermendham@computing.dundee.ac.uk>
To: Andrei Konovalov <akonovalov@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Tri-mode auto-negotiation on ML405
Date: Mon, 23 Apr 2007 13:48:56 +0100	[thread overview]
Message-ID: <462CAB38.8040506@computing.dundee.ac.uk> (raw)
In-Reply-To: <462B6EB2.70109@ru.mvista.com>

Andrei Konovalov wrote:
> Has the ethernet device been registered on the platform bus?
> There should be a call to platform_device_register()
> in arch/ppc/syslib/virtex_devices.c or arch/ppc/platforms/4xx/virtex.c 
> depending
> on the kernel tree used and the patches appiled.
Hi Andrei,

Drat.  I forgot to put that back in when I went to Grant Likely's latest 
patchset.  The errors I am getting now are (when I try and bring the 
network up):
eth0: XTemac Options: 
0xbcf0                                                   
eth0: XTemac could not start 
device.                                           
SIOCSIFFLAGeth0: XTemac Options: 
0xbcf0                                        
eth0: XTemac could not start 
device.                                           
S: Device or resource 
busy                                                     
SIOCSIFFLAGS: Device or resource 
busy                                          
route: SIOC[ADD|DEL]RT: Network is unreachable

During boot it said:
eth%d: XTemac using fifo direct interrupt driven 
mode.                         
mdiobus_reset on 
eth%d                                                         
temac_mii: 
probed                                                              
eth%d: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, 
irq=-1)       
eth0: Xilinx TEMAC #0 at 0x80000000 mapped to 0xC5020000, 
irq=0                
eth0: XTemac id 1.0f, block id 5, type 8

It seems like it's finding the MAC and PHY OK, what else have I done wrong?

Thanks,
-- Peter

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

      reply	other threads:[~2007-04-23 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 11:13 Tri-mode auto-negotiation on ML405 Peter Mendham
2007-04-13 16:25 ` Andrei Konovalov
2007-04-19 15:48   ` Peter Mendham
2007-04-22 14:18     ` Andrei Konovalov
2007-04-23 12:48       ` Peter Mendham [this message]

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=462CAB38.8040506@computing.dundee.ac.uk \
    --to=petermendham@computing.dundee.ac.uk \
    --cc=akonovalov@ru.mvista.com \
    --cc=linuxppc-embedded@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.