<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">We got the correct value of CLK9 and
CLK10. We found out a bug in the function fcc_enet_open(). Our setting
was CONFIG_USE_MDIO. In this mode, the board is able to get packets from
out side, but was unable to send packets. </font>
<br>
<br><font size=2 face="sans-serif">Now we changed the code like this. </font>
<br>
<br><font size=2 face="sans-serif">
fep->link = 1;</font>
<br><font size=2 face="sans-serif">
netif_start_queue(dev);</font>
<br><font size=2 face="sans-serif">
mii_do_cmd(dev, phy_cmd_config); /* display configuration
*/</font>
<br><font size=2 face="sans-serif">
return 0; </font>
<br>
<br><font size=2 face="sans-serif">Originally the code was ( Line no 2174)</font>
<br>
<br><font size=2 face="sans-serif">
netif_start_queue(dev);</font>
<br><font size=2 face="sans-serif">
return 0;
/* Success */</font>
<br>
<br><font size=2 face="sans-serif">Now the ethernet works perfectly. </font>
<br>
<br><font size=2 face="sans-serif">BTW, is there any tool/test case available
to test the ethernet driver for a long period of time? </font>
<br>
<br><font size=2 face="sans-serif">Thanks<br>
Batsayan Das<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Wolfgang Denk <wd@denx.de></b>
</font>
<br><font size=1 face="sans-serif">Sent by: wd@denx.de</font>
<p><font size=1 face="sans-serif">01/12/2006 02:04 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">batsayan.das@tcs.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">Linuxppc-embedded@ozlabs.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: Ethernet not initialized: Help req</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>In message <OFDC66830E.1EDE14C4-ON652570F3.00265CDF-652570F3.00297A66@tcs.com>
you wrote:<br>
> <br>
> In our MPC8260 based customs board the CLK9 is for transmit and CLK10
is <br>
> for receive. The ELDK tree uses CLK12 is receive, CLK11 is transmit
and <br>
<br>
This is not correct. The ELDK does not do this. The ELDK is
not a<br>
Linux source tree.<br>
<br>
Also, this setting is hardware dependent and differs from board
to<br>
board.<br>
<br>
> We got CLK9 and CLK10 from U-Boot tree and set those varables,
but <br>
> ethernet does not work. <br>
<br>
Then probably other changes / initializations
(port pin<br>
configurations) are needed as well.<br>
<br>
> My question is what value shall I use for CLK9 and CLK10? <br>
<br>
This idepends on your hardware. Study the schematics.<br>
<br>
> What else setting we need to change to make Ethernet work?<br>
<br>
Compare U-Boot code and other board definitions.<br>
<br>
Best regards,<br>
<br>
Wolfgang Denk<br>
<br>
-- <br>
Software Engineering: Embedded and Realtime Systems, Embedded
Linux<br>
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de<br>
A secure program has to be robust: it must be able to
deal with<br>
conditions that "can't happen", whether user input, program
error or<br>
library/etc. This is basic damage control. Buffer overflow
errors<br>
have nothing to do with security, but everything with stupidity.<br>
-- Wietse Venema
in <5cnqm3$8r9@spike.porcupine.org><br>
</tt></font>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT00008EB6
</font>
<br>
<table><tr><td bgcolor=#ffffff><font color=#000000>Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you<br>
</font></td></tr></table>