From: Vitaly Bordug <vbordug@ru.mvista.com>
To: robin.gilks@tait.co.nz
Cc: ppc embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Freescale combined ethernet driver
Date: Thu, 9 Nov 2006 17:49:47 +0300 [thread overview]
Message-ID: <20061109174947.415c7f7f@vitb.ru.mvista.com> (raw)
In-Reply-To: <45515913.3080206@tait.co.nz>
On Wed, 08 Nov 2006 17:12:03 +1300
Robin Gilks <robin.gilks@tait.co.nz> wrote:
> OK - I give up - whats the name of the device?
>
> I've tried eth0, fsl-cpm-fec0 (and other combinations) with a
> commandline of the form:
>
> ip=172.25.206.113:172.25.140.15::255.255.0.0:unset:fsl-cpm-fec0:off \
> panic=1 console=ttyCPM0
>
I am not following why you're touching netdev name here... Your problem clearly points to the unregistered platform device (which should be added to the identification code that maps system to the platform device list). In short, bsp code does name matching of the supported boards, and ties it to the enum of platform devices aught to be registered for this board. It registers nothing by default, and since fs_enet fail to found anything suitable on platform bus, not network devices created.
Yet it may be not the case of course - too less information to be sure.
Assuming it is not relevant to you anymore, just for archive purposes.
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2006-11-09 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 4:12 Freescale combined ethernet driver Robin Gilks
2006-11-08 22:00 ` Jim Heck
2006-11-09 1:31 ` Robin Gilks
2006-11-09 14:49 ` Vitaly Bordug [this message]
2006-11-09 20:27 ` Robin Gilks
2006-11-09 20:47 ` Andy Fleming
2006-11-12 20:43 ` Robin Gilks
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=20061109174947.415c7f7f@vitb.ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=robin.gilks@tait.co.nz \
/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).