at91_can: errata "Contents of Mailbox 0 can be sent"

* at91_can: errata "Contents of Mailbox 0 can be sent"
@ 2011-01-05 23:41 Marc Kleine-Budde
  0 siblings, 0 replies; only message in thread
From: Marc Kleine-Budde @ 2011-01-05 23:41 UTC (permalink / raw)
  To: SocketCAN Core Mailing List; +Cc: Netdev-u79uwXL29TY76Z2rM5mHXA

[-- Attachment #1.1: Type: text/plain, Size: 977 bytes --]

Moin,

the at91_can core has the following problem:
"50.3.5.3 CAN: 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 a unused can_id that will not disturb the bus.

I'm going to implement the workaround. As the unused identifier is
probably application specific my question is: What's the best way to
configure this identifier?

- sysfs
- netlink
- ioctl
- ethtool
- peek/poke :P

What will be a good default can_id?

regards, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 188 bytes --]

_______________________________________________
Socketcan-core mailing list
Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
https://lists.berlios.de/mailman/listinfo/socketcan-core

^ permalink raw reply	[flat|nested] only message in thread