<br><font size=2 face="sans-serif">Thanks for the inputs,</font>
<br><font size=2 face="sans-serif">We are still in the process of debugging
the nfs mounting for our target board,</font>
<br><font size=2 face="sans-serif">there were Tx clock and Rx clock pins
in our board were different as compared to MPC8272ADS board and we
configured PC_F2RXCLK and PC_F2TXCLK macro,s accordingly in \arch\ppc\8260_io\fcc_enet.c.</font>
<br><font size=2 face="sans-serif">still nfs is not up.. same error "
Root-NFS: Server returned error -5 while mounting /opt/montavista/pro/devkit/ppc//82xx/target"
is comming up.</font>
<br>
<br><font size=2 face="sans-serif">We verified " immr->im_cpmux.cmx_fcr
= 0x2c0000" reg value both in bootloader and kernel, both are same
but ethernet works in u-boot and does not work in kernel.</font>
<br><font size=2 face="sans-serif">Please suggest how we can attack this
problem.</font>
<br><font size=2 face="sans-serif">Thanks</font>
<br><font size=2 face="sans-serif">Manjunath AM</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Andre Haupt <haupt.andre@gmx.de></b>
</font>
<br><font size=1 face="sans-serif">Sent by: linuxppc-embedded-bounces+manjunath.am=lntemsys.com@ozlabs.org</font>
<p><font size=1 face="sans-serif">01/24/2007 01:40 PM</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">Scott Wood <scottwood@freescale.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">kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org,
Manjunath AM <Manjunath.AM@Lntemsys.com></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: nfs mounting problem</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Scott Wood wrote:<br>
> Andre Haupt wrote:<br>
>> Also what seems a bit odd to me is that your dmesg shows no rootpath<br>
>><br>
>> IP-Config: Complete:<br>
>> device=eth1, addr=192.168.178.234, mask=255.255.255.0,
<br>
>> gw=192.168.178.47,<br>
>> host=cashel, domain=, nis-domain=(none),<br>
>> bootserver=192.168.178.110, rootserver=192.168.178.110,
rootpath=<br>
>><br>
>> On my system the complete root path is printed here.<br>
><br>
> I don't think I've ever seen the root path printed there (with nfsroot
<br>
> otherwise working), so I don't think that's the problem... From
<br>
> looking at the code, it seems that the root path received from BOOTP
<br>
> is stored in a different variable than the path from the nfsroot boot
<br>
> option, and it's the former that gets printed there.<br>
Ahh, ok. I am using BOOTP, so this has nothing to do with Manjunaths <br>
problem. Thanks for clarification.<br>
<br>
Best,<br>
<br>
Andre<br>
_______________________________________________<br>
Linuxppc-embedded mailing list<br>
Linuxppc-embedded@ozlabs.org<br>
https://ozlabs.org/mailman/listinfo/linuxppc-embedded<br>
</tt></font>
<br>