Freescale combined ethernet driver

Freescale combined ethernet driver

[Robin Gilks]

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

and I get the following errors:
[   37.249708] TCP bic registered
[   37.255389] Initializing IPsec netlink socket
[   37.264134] NET: Registered protocol family 1
[   37.272673] NET: Registered protocol family 17
[   37.281436] NET: Registered protocol family 15
[   37.796233] IP-Config: Device `fsl-cpm-fec0' not found.
[   37.807814] Looking up port of RPC 100003/2 on 172.25.140.15
[   37.819328] portmap: RPC call returned error 101

This is on an 859T CPU so its a CPM1 and I'm using the single SCC 
channel as a serial UART.

-- 
Robin

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

Re: Freescale combined ethernet driver

[Jim Heck]

Assuming you have a filesystem and can get some software onto it (with 
the network not up...), the package 'iproute' contains the 'ip' tool 
that would quickly show you the name of the device using the command.

ip link show

# ip link show
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0b:cd:01:d0:6b brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast 
qlen 1000    link/ether 00:01:02:48:4d:41 brd ff:ff:ff:ff:ff:ff
4: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0

-Jim

Robin Gilks 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
>
> and I get the following errors:
> [   37.249708] TCP bic registered
> [   37.255389] Initializing IPsec netlink socket
> [   37.264134] NET: Registered protocol family 1
> [   37.272673] NET: Registered protocol family 17
> [   37.281436] NET: Registered protocol family 15
> [   37.796233] IP-Config: Device `fsl-cpm-fec0' not found.
> [   37.807814] Looking up port of RPC 100003/2 on 172.25.140.15
> [   37.819328] portmap: RPC call returned error 101
>
> This is on an 859T CPU so its a CPM1 and I'm using the single SCC 
> channel as a serial UART.
>
>   

Re: Freescale combined ethernet driver

[Robin Gilks]

Jim Heck wrote:
> Assuming you have a filesystem and can get some software onto it (with 
> the network not up...), the package 'iproute' contains the 'ip' tool 
> that would quickly show you the name of the device using the command.
> 

I've given up on the Freescale driver as its obviously broken and gone 
back to the intermediate one (not the 8xx_io one!!) so I have a network 
connection now (on eth0).

No filesystem yet as I've yet to write a platform support map for the 
flash, initrd (ramfs) fails with an oops and root nfs fails as well even 
though it manages the mount, it says it can't find an init (same fs on 
2.4 is fine!!).

My head hurts...

-- 
Robin

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

Re: Freescale combined ethernet driver

[Vitaly Bordug]

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

Re: Freescale combined ethernet driver

[Robin Gilks]

Vitaly Bordug wrote:

> 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.
> 

Is there a howto that explains in simple terms (i.e. not "do like board 
X but I'm not going to tell which bits of the code are crap" but an 
actual interface spec) on how to create this (as far as I can see 
totally undocumented) platform device.

BTW: the code is NOT the documentation - that is the 'how' not the 'why'!


=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

Re: Freescale combined ethernet driver

[Andy Fleming]

On Nov 9, 2006, at 14:27, Robin Gilks wrote:

>
> Is there a howto that explains in simple terms (i.e. not "do like  
> board
> X but I'm not going to tell which bits of the code are crap" but an
> actual interface spec) on how to create this (as far as I can see
> totally undocumented) platform device.
>
> BTW: the code is NOT the documentation - that is the 'how' not the  
> 'why'!

Documentation/driver-model/*

Re: Freescale combined ethernet driver

[Robin Gilks]

Andy Fleming wrote:

> 
> Documentation/driver-model/*
> 

Duh!!

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================