From: Domen Puncer <domen.puncer@telargo.com>
To: galak@kernel.crashing.org, jgarzik@pobox.com
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: [PATCH v3 2/4] FEC mpc52xx: add some bestcomm flags
Date: Sun, 14 Oct 2007 09:58:34 +0200 [thread overview]
Message-ID: <20071014075834.GE3000@nd47.coderock.org> (raw)
In-Reply-To: <20071014075511.GC3000@nd47.coderock.org>
Add masks and fix existing ones to match mpc5200b user's manual.
Signed-off-by: Domen Puncer <domen.puncer@telargo.com>
---
arch/powerpc/sysdev/bestcomm/fec.h | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
Index: linux.git/arch/powerpc/sysdev/bestcomm/fec.h
===================================================================
--- linux.git.orig/arch/powerpc/sysdev/bestcomm/fec.h
+++ linux.git/arch/powerpc/sysdev/bestcomm/fec.h
@@ -21,7 +21,20 @@ struct bcom_fec_bd {
};
#define BCOM_FEC_TX_BD_TFD 0x08000000ul /* transmit frame done */
-#define BCOM_FEC_TX_BD_INT 0x04000000ul /* interrupt */
+#define BCOM_FEC_TX_BD_TC 0x04000000ul /* transmit CRC */
+#define BCOM_FEC_TX_BD_ABC 0x02000000ul /* append bad CRC */
+
+#define BCOM_FEC_RX_BD_L 0x08000000ul /* buffer is last in frame */
+#define BCOM_FEC_RX_BD_BC 0x00800000ul /* DA is broadcast */
+#define BCOM_FEC_RX_BD_MC 0x00400000ul /* DA is multicast and not broadcast */
+#define BCOM_FEC_RX_BD_LG 0x00200000ul /* Rx frame length violation */
+#define BCOM_FEC_RX_BD_NO 0x00100000ul /* Rx non-octet aligned frame */
+#define BCOM_FEC_RX_BD_CR 0x00040000ul /* Rx CRC error */
+#define BCOM_FEC_RX_BD_OV 0x00020000ul /* overrun */
+#define BCOM_FEC_RX_BD_TR 0x00010000ul /* Rx frame truncated */
+#define BCOM_FEC_RX_BD_LEN_MASK 0x000007fful /* mask for length of received frame */
+#define BCOM_FEC_RX_BD_ERRORS (BCOM_FEC_RX_BD_LG | BCOM_FEC_RX_BD_NO | \
+ BCOM_FEC_RX_BD_CR | BCOM_FEC_RX_BD_OV | BCOM_FEC_RX_BD_TR)
extern struct bcom_task *
next prev parent reply other threads:[~2007-10-14 7:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 7:55 [PATCH v3 0/4] FEC - fast ethernet controller for mpc52xx Domen Puncer
2007-10-14 7:57 ` [PATCH v3 1/4] FEC mpc52xx: device tree changes Domen Puncer
2007-10-14 7:58 ` Domen Puncer [this message]
2007-10-14 7:59 ` [PATCH v3 3/4] FEC mpc52xx: the driver Domen Puncer
2007-10-14 21:43 ` Grant Likely
2007-10-14 7:59 ` [PATCH v3 4/4] FEC mpc52xx: phy part of " Domen Puncer
2007-10-14 22:05 ` Grant Likely
2007-10-15 10:56 ` [PATCH v3 4/4] FEC mpc52xx: phy part of the driver\ Domen Puncer
2007-10-15 14:30 ` Grant Likely
2007-10-15 19:06 ` [PATCH v3 0/4] FEC - fast ethernet controller for mpc52xx Jeff Garzik
2007-10-15 19:19 ` Grant Likely
2007-10-18 14:15 ` Grant Likely
2007-10-18 19:14 ` Jeff Garzik
2007-10-19 11:27 ` [PATCH v4] " Domen Puncer
2007-10-21 18:32 ` Grant Likely
2007-10-25 9:29 ` Jeff Garzik
2007-10-25 14:10 ` Domen Puncer
2007-10-25 18:57 ` Dale Farnsworth
2007-10-25 19:41 ` Domen Puncer
2007-10-25 20:29 ` Dale Farnsworth
2007-10-25 22:46 ` Jeff Garzik
2007-10-25 23:50 ` Stephen Hemminger
2007-10-26 11:59 ` [PATCH v4.2] " Domen Puncer
2007-10-26 14:18 ` Dale Farnsworth
2007-10-26 16:07 ` [PATCH v4.3] " Domen Puncer
2007-10-29 9:59 ` Jeff Garzik
2007-10-29 15:37 ` Grant Likely
2007-11-01 11:31 ` [PATCH v4] " tnt
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=20071014075834.GE3000@nd47.coderock.org \
--to=domen.puncer@telargo.com \
--cc=galak@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).