* eth1 FEC on RPX-CLLF info
2001-11-13 18:21 ` Dan Malek
@ 2001-11-20 17:07 ` sruel
2001-11-20 19:03 ` Wolfgang Denk
0 siblings, 1 reply; 3+ messages in thread
From: sruel @ 2001-11-20 17:07 UTC (permalink / raw)
To: Dan Malek; +Cc: linuxppc-embedded
Hello Wolfgang,
I'm trying to activate the FEC on my RPX-CLLF board. Everything seems ok
when I do a ifconfig -a, but the FEC eth1 interface seems dead. I wonder
if the base address of the FEC is really 0xe00?
Here is my eth1 config:
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10:EC:00:2C:93
inet addr:172.16.200.10 Bcast:172.16.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:719 errors:0 dropped:0 overruns:0 frame:14
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Base address:0x3c00
eth1 Link encap:Ethernet HWaddr 00:10:EC:80:2C:93
inet addr:148.33.216.245 Bcast:148.33.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Base address:0xe00
lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Here is the boot screen dump. The eth1 FEC MAC address is correctly read.
...
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
eth0: CPM ENET Version 0.2 on SCC1, 00:10:ec:00:2c:93
eth1: FEC ENET Version 0.2, FEC irq 3, addr 00:10:ec:80:2c:93
JFFS version 1.0, (C) 1999, 2000 Axis Communications AB
loop: loaded (max 8 devices)
RPX Lite or CLLF flash device: 1000000 at ff000000
Amd/Fujitsu Extended Query Table v1.2 at 0x0040
number of CFI chips: 1
...
Would you have any idea of the problem?
By the way, in the file fec.c from kernel 2.4.4 (2001-07-23), it is
mentionned that the FEC PHY for the RPX-CLLF board is a QS6612. I have
an RPX-CLLF board, and it uses an LXT971.
Thank!
Sebastien Ruel, System Engineer.
Oerlikon Contraves
Quebec, Canada
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: eth1 FEC on RPX-CLLF info
2001-11-20 17:07 ` eth1 FEC on RPX-CLLF info sruel
@ 2001-11-20 19:03 ` Wolfgang Denk
0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2001-11-20 19:03 UTC (permalink / raw)
To: sruel@oerlikon.ca; +Cc: linuxppc-embedded
Dear Sebastien,
in message <3BFA8DB6.1050405@oerlikon.ca> you wrote:
>
> Hello Wolfgang,
I'm not exactly sure whom you're addressing: the email addess was
Dan's but the name is mine, and it seems you are referring to the
kernel version on our FTP server, so I jump in ...
> I'm trying to activate the FEC on my RPX-CLLF board. Everything seems ok
> when I do a ifconfig -a, but the FEC eth1 interface seems dead. I wonder
> if the base address of the FEC is really 0xe00?
What do you think it means? Here, it's the offset of the FEC
parameter RAM in the IMMR memory map. And yes, 0xE00 is correct.
> Here is the boot screen dump. The eth1 FEC MAC address is correctly read.
> ...
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> eth0: CPM ENET Version 0.2 on SCC1, 00:10:ec:00:2c:93
> eth1: FEC ENET Version 0.2, FEC irq 3, addr 00:10:ec:80:2c:93
Looks good to me...
> eth1 Link encap:Ethernet HWaddr 00:10:EC:80:2C:93
> inet addr:148.33.216.245 Bcast:148.33.255.255 Mask:255.255.255.0
Are you sure about those settings? To me it seems Bcast and Mask
don't match...
> Would you have any idea of the problem?
What happens when you enable the MDIO option?
> By the way, in the file fec.c from kernel 2.4.4 (2001-07-23), it is
> mentionned that the FEC PHY for the RPX-CLLF board is a QS6612. I have
> an RPX-CLLF board, and it uses an LXT971.
Did you enable the LXT971 code, then? Sorry, I don't have any CLLF
boards here, so I cannot test this myself.
Just tested it (again) on a TQM860L-P.50; works fine for me.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Above all else -- sky.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: eth1 FEC on RPX-CLLF info
[not found] <3BFBE9F2.2090800@oerlikon.ca>
@ 2001-11-21 17:59 ` Wolfgang Denk
0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2001-11-21 17:59 UTC (permalink / raw)
To: sruel@oerlikon.ca; +Cc: linuxppc-embedded
Dear Sebastien,
in message <3BFBE9F2.2090800@oerlikon.ca> you wrote:
>
> >What happens when you enable the MDIO option?
>
> It says:
> ...
> fec: No PHY device found.
Well, this seems to be a hint...
> Yes, the LXT971 code is enabled in fec.c.
> I find out that the older CLLF_BW board was using a QS6612 PHY, but the
> CLLF_BW31 (my board revision) is using an LXT971.
Check if your hardware requires to enable and/or reset the PHY using
some port pins or bits in a board control register...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A fail-safe circuit will destroy others. -- Klipstein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-11-21 17:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <3BFBE9F2.2090800@oerlikon.ca>
2001-11-21 17:59 ` eth1 FEC on RPX-CLLF info Wolfgang Denk
[not found] <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
2001-11-13 11:03 ` Linuxppc and MPC8255 routing performance Ricardo Scop
2001-11-13 17:02 ` Dan Malek
2001-11-13 12:38 ` Ricardo Scop
2001-11-13 18:21 ` Dan Malek
2001-11-20 17:07 ` eth1 FEC on RPX-CLLF info sruel
2001-11-20 19:03 ` Wolfgang Denk
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).