* FEC driver not working after upgrade
@ 2007-08-01 19:47 Mit Matelske
2007-08-02 20:51 ` Wolfgang Denk
0 siblings, 1 reply; 3+ messages in thread
From: Mit Matelske @ 2007-08-01 19:47 UTC (permalink / raw)
To: linuxppc-dev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FEC driver not working after upgrade
2007-08-01 19:47 FEC driver not working after upgrade Mit Matelske
@ 2007-08-02 20:51 ` Wolfgang Denk
2007-08-02 23:32 ` Mit Matelske
0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang Denk @ 2007-08-02 20:51 UTC (permalink / raw)
To: Mit Matelske; +Cc: linuxppc-dev
In message <11952546.post@talk.nabble.com> you wrote:
>
> I upgraded from an old 2.4.25 kernel to the latest Denx snapshot and cannot
...
> I am running a 5200B. Thanks for any help.
Do you really have the latest snapshot, i. e. top of tree from the git
repository?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
There are very few personal problems that cannot be solved through a
suitable application of high explosives.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FEC driver not working after upgrade
2007-08-02 20:51 ` Wolfgang Denk
@ 2007-08-02 23:32 ` Mit Matelske
0 siblings, 0 replies; 3+ messages in thread
From: Mit Matelske @ 2007-08-02 23:32 UTC (permalink / raw)
To: linuxppc-dev
wd wrote:
>
> In message <11952546.post@talk.nabble.com> you wrote:
>>
>> I upgraded from an old 2.4.25 kernel to the latest Denx snapshot and
>> cannot
> ...
>> I am running a 5200B. Thanks for any help.
>
> Do you really have the latest snapshot, i. e. top of tree from the git
> repository?
>
Yes sir. I have the 2007-7-10 snapshot.
Someone posted what I assume to be a similar problem back in March:
http://www.nabble.com/Problems-with-PHY-on-STK5200-tf3326321.html#a9247789
but there was no solution. Thanks for any and all help.
Mit Matelske
--
View this message in context: http://www.nabble.com/FEC-driver-not-working-after-upgrade-tf4202285.html#a11975001
Sent from the linuxppc-dev mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-08-02 23:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-01 19:47 FEC driver not working after upgrade Mit Matelske
2007-08-02 20:51 ` Wolfgang Denk
2007-08-02 23:32 ` Mit Matelske
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).