From: "SIP COP 009" <sipcop009@gmail.com>
To: linuxppc-embedded@ozlabs.org
Cc: sipcop009@gmail.com
Subject: Gianfar on 8347 sometimes get stuck at startup
Date: Thu, 22 Feb 2007 21:14:16 -0800 [thread overview]
Message-ID: <5a4792c00702222114ycd2b6a5xbec6bc996d99c9ce@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 917 bytes --]
next reply other threads:[~2007-02-23 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 5:14 SIP COP 009 [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-23 6:08 Gianfar on 8347 sometimes get stuck at startup Gary Kenaley
2007-02-28 23:52 ` SIP COP 009
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4792c00702222114ycd2b6a5xbec6bc996d99c9ce@mail.gmail.com \
--to=sipcop009@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).