Hi Domingos,
On 05/08/11 19:53, dhl...@sapo.pt wrote:
I am using the uClinux-dist-20110603, and trying compile to MOD5272
(Netburner) kernel 2.4.x with m68k-uclinux-tools.
I have some problems with fec driver.
Configuration 1:
If i choose only this Kernell configuration:
[ * ]FEC ethernet controller (of coldfire 5272/5282/5280)
[ ] enable second FEC port (5274/5275)
[ ] enable IOCTL (EXPERIMENTAL)
[ ] Micrel KS8995M switch chip suport
In uClinux boot:
PHY is correctly recognized correctly:
......
fec.c: Probe number 1 with 0x0000
eth0: FEC ENET Version 0.2, 00:03:f4:04:49:4a
fec: PHY @ 0x1, ID 0x00221619 -- KS8721BL
......
But the ethernet don?t work correctly, ping for own IP works, ping for
other IP cause:
......
# ping -c 5 172.18.201.123
PING 172.18.201.123 (172.18.201.123): 56 data bytes
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
Ring data dump: cur_tx 2263100, dirty_tx 2263100 cur_rx: 2263008
........
--- 172.18.201.123 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
#
......
ping form other IP to MOD5272 too not work.
Configuration 2:
If i choose only this Kernell configuration:
[ * ]FEC ethernet controller (of coldfire 5272/5282/5280)
[ ] enable second FEC port (5274/5275)
[ ] enable IOCTL (EXPERIMENTAL)
[ * ] Micrel KS8995M switch chip suport
In uClinux boot:
PHY is NOT FOUND:
......
fec.c: Probe number 1 with 0x0000
eth0: FEC ENET Version 0.2, 00:03:f4:04:49:4a
FEC: No PHY device found.
......
But the ethernet work correctly, ping:
Digging in source files i found, the difference between configuration
1 and 2 is in file: uClinux-dist/linux-2.4.x/drivers/net/fec.c
configuration 1: 171: #define PHY_START_ADDR 0
configuration 2: 164: #define PHY_START_ADDR 5
Digging in mailing list uClinux-dev, i found many fec.c PATCHs...
Some for 2.4.x fec.c file, some for 2.6.x fec.c file, and others for
unknown fec.c file....
And, i got the doubt, if all these changes were present in the source
I am using??
If you follow the email trail for this patch though you will see
it is solved by a different code change. So you won't see that
exact code change in that patch. And this is probably true of a
few changes over the years if you follow the trail.
What sort of PHY does your board actually have on it?
And what PHY address is it mapped to?
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: g...@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
