From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by ozlabs.org (Postfix) with ESMTP id 7E0E2DDD07 for ; Fri, 23 Feb 2007 16:14:18 +1100 (EST) Received: by wr-out-0506.google.com with SMTP id 37so464984wra for ; Thu, 22 Feb 2007 21:14:17 -0800 (PST) Message-ID: <5a4792c00702222114ycd2b6a5xbec6bc996d99c9ce@mail.gmail.com> Date: Thu, 22 Feb 2007 21:14:16 -0800 From: "SIP COP 009" To: linuxppc-embedded@ozlabs.org Subject: Gianfar on 8347 sometimes get stuck at startup MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_39616_29414280.1172207656519" Cc: sipcop009@gmail.com List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_39616_29414280.1172207656519 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline We have the our own MPC8349 based board which has 2 GigEs. It is pretty much modelled similar to the 8349ADS EVAL boards, infact we have zero changes. The issue that we are seeing - Sometimes at startup, we have send 2 TX packets to kind-of-kickstart the TSEC Tranmission. If we send only packet it does not get to the other side. This does not happen always. The TSEC Registers dont really show any errors nor does the Marvell PHY show any errors. The kernel that we are using is 2.6.11. Anybody seen this before or something similar ? Any pointers will be appreciated. We cannot move to any other kernel verision right now. Thanks! ashutosh ------=_Part_39616_29414280.1172207656519 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
 
We have the our own MPC8349 based board which has 2 GigEs. It is pretty much modelled similar to the 8349ADS EVAL boards, infact we have zero changes.
 
The issue that we are seeing -
 
Sometimes at startup, we have send 2 TX packets to kind-of-kickstart the TSEC Tranmission. If we send only packet it does not get to the other side. This does not happen always.
 
The TSEC Registers dont really show any errors nor does the Marvell PHY show any errors.
 
The kernel that we are using is 2.6.11.
 
Anybody  seen this before or something similar ?
 
Any pointers will be appreciated. We cannot move to any other kernel verision right now.
 
Thanks!
ashutosh
 
------=_Part_39616_29414280.1172207656519--