Linux w/ML403 PLB TEMAC
Glenn.G.Hart at us.westinghouse.com
Glenn.G.Hart at us.westinghouse.com
Thu Feb 15 01:47:50 EST 2007
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
(Embedded "Ming Liu" <eemingliu at hotmail.com>@ozlabs.org
image moved 02/12/2007 11:48 AM
to file:
pic04169.pcx)
Sent by:
linuxppc-embedded-bounces+glenn.g.hart=us.westinghouse.com at ozlabs.org
To: Glenn.G.Hart at us.westinghouse.com
cc: linuxppc-embedded at ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold = 16, Receive Threshold = 2
>[ 44.448421] eth0: XTemac: Send Wait bound = 1, Receive Wait bound = 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed = (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed = MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. I
didn't try that before. So if you will try, pls let us know the result. :)
BR
Ming
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded at ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic04169.pcx
Type: application/octet-stream
Size: 128 bytes
Desc: not available
Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20070214/542457da/attachment.obj
More information about the Linuxppc-embedded
mailing list