From: Mit Matelske <mit@sweeet.net>
To: linuxppc-dev@ozlabs.org
Subject: FEC driver not working after upgrade
Date: Wed, 1 Aug 2007 12:47:26 -0700 (PDT) [thread overview]
Message-ID: <11952546.post@talk.nabble.com> (raw)
I upgraded from an old 2.4.25 kernel to the latest Denx snapshot and cannot
get the ethernet to work. I was previously running the FEC driver that used
the sdma interface. I get a couple of interrupts and that is it.
Output when initializing:
mpc5xxx_fec_init
fec_priv c3f83160
MPC5200 I2S driver (16 BDs x 16 bytes).
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
mpc5xxx_fec_open
mpc5xxx_fec_restart
eth0: duplex set to 1
mii_queue: 600a0000 c0130bb0 00000000
mpc5xxx_fec_interrupt:
mpc5xxx_fec_mii 60080141 c0130bb0 00000000
mii_discover_phy
mii_queue: 600e0000 c0130abc 00000000
mpc5xxx_fec_interrupt:
mpc5xxx_fec_mii 600e0c87 c0130abc 00000000
eth0: Phy @ 0x0, type 88E6060 (0x01410c87)
Whenever I try to transmit anything I get:
mpc5xxx_fec_hard_start_xmit:
dev c3f83000, priv c3f83160, skb c3bcc860
The phy code works in the old fec driver fine, but I have tried the generic
phy driver also and it acts exactly the same.
The major change was done by this patch back on Sept 4, 2005:
Modifications to the MPC5200 ATA and FEC drivers based on the
linuxppc_2_4_devel-fec+ata.patch and linux.habanero.fifo_cntrl.patch
patches from Freescale.
I am running a 5200B. Thanks for any help.
Mit
--
View this message in context: http://www.nabble.com/FEC-driver-not-working-after-upgrade-tf4202285.html#a11952546
Sent from the linuxppc-dev mailing list archive at Nabble.com.
next reply other threads:[~2007-08-01 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 19:47 Mit Matelske [this message]
2007-08-02 20:51 ` FEC driver not working after upgrade Wolfgang Denk
2007-08-02 23:32 ` Mit Matelske
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=11952546.post@talk.nabble.com \
--to=mit@sweeet.net \
--cc=linuxppc-dev@ozlabs.org \
/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.