All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Konovalov <akonovalov@ru.mvista.com>
To: Peter Mendham <petermendham@computing.dundee.ac.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Tri-mode auto-negotiation on ML405
Date: Sun, 22 Apr 2007 18:18:26 +0400	[thread overview]
Message-ID: <462B6EB2.70109@ru.mvista.com> (raw)
In-Reply-To: <46278F3A.4070007@computing.dundee.ac.uk>

Hi Peter,

Peter Mendham wrote:
> Andrei Konovalov wrote:
> 
>> And I've tried the PHY library (drivers/net/phy/*) introduced by Andy 
>> Fleming.
>> Kinda works. [...]
>> Attached is the incomplete adapter.c (with FIFO mode support only) which
>> uses the PHY lib to handle the PHY. Just to illustrate the idea (will 
>> post the
>> patch later when it is completed).
> 
> Hi Andrei,
> 
> I've now had a chance to have a go at the adapter.c you sent properly 
> (sorry about the delay).  I'm afraid I can't get it to work.  I was 
> wondering if you could tell me what I'm doing wrong.  When I try and 
> bring the interface up I get:
> SIOCSIFADDR: No such device
> SIOCSIFNETMASK: No such device
> SIOCSIFBRDADDR: No such device
> SIOCGIFFLAGS: No such device
> route: SIOC[ADD|DEL]RT: No such device
> 
> I have included PHYLIB and even tried including support for the Marvell 
> PHY.  I still get the same. I'm sure I've made a stupid mistake, any ideas?

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.

Thanks,
Andrei

> Thanks,
> -- Peter
> 
> 
> 

  reply	other threads:[~2007-04-26 22:10 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 [this message]
2007-04-23 12:48       ` Peter Mendham

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=462B6EB2.70109@ru.mvista.com \
    --to=akonovalov@ru.mvista.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=petermendham@computing.dundee.ac.uk \
    /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.