From: Wolfgang Denk <wd@denx.de>
To: "sruel@oerlikon.ca" <sruel@oerlikon.ca>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: eth1 FEC on RPX-CLLF info
Date: Tue, 20 Nov 2001 20:03:54 +0100 [thread overview]
Message-ID: <20011120190359.27783F9B9@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 20 Nov 2001 12:07:02 EST." <3BFA8DB6.1050405@oerlikon.ca>
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/
next prev parent reply other threads:[~2001-11-20 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-13 21:09 ` Re[2]: " Ricardo Scop
2001-11-20 17:07 ` eth1 FEC on RPX-CLLF info sruel
2001-11-20 19:03 ` Wolfgang Denk [this message]
[not found] <3BFBE9F2.2090800@oerlikon.ca>
2001-11-21 17:59 ` Wolfgang Denk
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=20011120190359.27783F9B9@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sruel@oerlikon.ca \
/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).