From: "Lichang Che" <lichang.che@nec.com.au>
To: <linuxppc-embedded@ozlabs.org>
Subject: scc ethernet driver error - bus contention?
Date: Fri, 29 Sep 2006 13:07:55 +1000 [thread overview]
Message-ID: <000d01c6e374$757f5b30$bfd34c93@mul7.nec.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Hello,
I'm using Linux 2.6.16 + uboot on MPC8250 - SMC2 for UART and SCC4 for 10M
Ethernet. The problem I got is as follows:
1. If the GBL bit is set (with address snooping), an underrun happens for
each frame transmission.
2. If the GBL bit is disabled, the underrun problem disappears but nearly
all frames are corrupted - the frame can be received (without CRC etc) by
another machine but the data is not correct.
3. If the frame to be sent is copied into the dual port ram first and the
transmission is triggered, the frame can be successfully received.
Can anyone give me some hint?
Cheers
[-- Attachment #2: Type: text/html, Size: 3521 bytes --]
reply other threads:[~2006-09-29 3:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000d01c6e374$757f5b30$bfd34c93@mul7.nec.com.au' \
--to=lichang.che@nec.com.au \
--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).