[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1294741688-22699-1-git-send-email-mkl@pengutronix.de>
Date: Tue, 11 Jan 2011 11:28:05 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Socketcan-core@...ts.berlios.de
Cc: netdev@...r.kernel.org
Subject: [PATCH 0/3] can: at91_can: fix for errata 50.2.6.3 & 50.3.5.3
Hello,
as promised I've implemented the proposed workaround for the errata
50.2.6.3 & 50.3.5.3:
"Contents of Mailbox 0 can be sent Even if Mailbox is Disabled"
This means under high bus load it can happen that the mailbox 0 is send
to the bus. And it does happen, even with the mainline driver where
Mailbox 0 is a receive mailbox. The errata proposes not to use mailbox 0
and load it with an unused can_id that will not disturb the bus.
The first patch cleans up the driver without any functional changes, so
that the mailbox 0 can be disabled in the second patch. The third patch
adds a sysfs parameter to the driver, so that the identifier of mailbox 0
can configured.
This series applies to net-2.6/master. It has been tested on a ronetix pm9263
board against a PCI-SJA1000 card with the canfdtest utility.
regards, Marc
---
The following changes since commit b11a25aaeccc29d5090d1ce9776af20e3ee99ab9:
qlcnic: change module parameter permissions (2011-01-10 13:34:55 -0800)
are available in the git repository at:
git://git.pengutronix.de/git/mkl/linux-2.6.git can/at91_can-for-net-2.6
Marc Kleine-Budde (3):
can: at91_can: clean up usage of AT91_MB_RX_FIRST and AT91_MB_RX_NUM
can: at91_can: don't use mailbox 0
can: at91_can: make can_id of mailbox 0 configurable
drivers/net/can/at91_can.c | 138 +++++++++++++++++++++++++++++++++++--------
1 files changed, 112 insertions(+), 26 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists