From: "Shen Rong" <rshen@udtech.com.cn>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: wrong definition in cpm_8260.h?
Date: Wed, 22 Jan 2003 19:03:25 +0800 [thread overview]
Message-ID: <00bc01c2c205$e4c95520$e600a8c0@udtech.net> (raw)
Hi,
In cpm_8260.h, BD_ENET_RX_STATS is defined to 0x1ff, which leads
to the fcc driver can't clean the BD_ENET_RX_LAST&BD_ENET_RX_FIRST bits
with the following statement:
bdp->cbd_sc &= ~BD_ENET_RX_STATS;
The first&last bits are set by the CPM not the CPU, so they
should be cleared after the frame is received. So it should be:
#define BD_ENET_RX_STATS ((ushort)0x0fff) /* All status bits */
The same problem in ppcboot.
Shenrong
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-01-22 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 11:03 Shen Rong [this message]
2003-01-22 14:54 ` wrong definition in cpm_8260.h? Joakim Tjernlund
2003-01-22 18:04 ` Dan Malek
2003-01-22 21:33 ` Joakim Tjernlund
2003-01-22 22:20 ` Dan Malek
2003-01-22 23:08 ` Joakim Tjernlund
2003-01-23 2:04 ` Shen Rong
2003-01-23 15:45 ` Dan Malek
2003-01-24 2:20 ` Shen Rong
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='00bc01c2c205$e4c95520$e600a8c0@udtech.net' \
--to=rshen@udtech.com.cn \
--cc=linuxppc-embedded@lists.linuxppc.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).