From: Daniel Hellstrom <daniel@gaisler.com>
To: netdev@vger.kernel.org
Subject: CRC endianess problem on DGE-510T
Date: Fri, 10 Jun 2011 10:03:14 +0200 [thread overview]
Message-ID: <4DF1CFC2.5080101@gaisler.com> (raw)
Hello,
I'm having problems with the PCI network board D-LINK DGE-510T on
SPARC32/LEON. The CRC calculated by ether_crc_le() does not match the
CRC, however after swapping the result it matches. This is the same
behaviour with the 3 boards I have. After applying the patch below
everything works.
Does anyone know if this is a correct patch or has had similar problems
on big endian machines?
Daniel
From: Daniel Hellstrom <daniel@gaisler.com>
Date: Wed, 6 Apr 2011 15:01:44 +0200
[PATCH] dl2k: EEPROM CRC calculation wrong endianess on bigendian machine
Signed-off-by: Daniel Hellstrom <daniel@gaisler.com>
---
drivers/net/dl2k.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/dl2k.c b/drivers/net/dl2k.c
index c445457..4bbbd7b 100644
--- a/drivers/net/dl2k.c
+++ b/drivers/net/dl2k.c
@@ -346,7 +346,7 @@ parse_eeprom (struct net_device *dev)
if (np->pdev->vendor == PCI_VENDOR_ID_DLINK) { /* D-Link Only */
/* Check CRC */
crc = ~ether_crc_le (256 - 4, sromdata);
- if (psrom->crc != crc) {
+ if (psrom->crc != cpu_to_le32(crc)) {q
printk (KERN_ERR "%s: EEPROM data CRC error.\n",
dev->name);
return -1;
--
1.5.4
next reply other threads:[~2011-06-10 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:03 Daniel Hellstrom [this message]
2011-06-10 12:35 ` CRC endianess problem on DGE-510T Ben Hutchings
2011-06-10 13:12 ` Daniel Hellstrom
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=4DF1CFC2.5080101@gaisler.com \
--to=daniel@gaisler.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.