On 01/11/2011 12:57 PM, Wolfram Sang wrote: > On Tue, Jan 11, 2011 at 11:28:08AM +0100, Marc Kleine-Budde wrote: >> Due to a chip bug (errata 50.2.6.3 & 50.3.5.3 in >> "AT91SAM9263 Preliminary 6249H-ATARM-27-Jul-09") the contents of mailbox >> 0 may be send under certain conditions (even if disabled or in rx mode). >> >> The workaround in the errata suggests not to use the mailbox and load it >> with a unused identifier. >> >> This patch implements the second part of the workaround. A sysfs entry >> "mb0_id" is introduced. While the interface is down it can be used to >> configure the can_id of mailbox 0. The default value id 0x7ff. >> >> In order to use an extended can_id add the CAN_EFF_FLAG (0x80000000U) >> to the can_id. Example: >> >> - standard id 0x7ff: >> echo 0x7ff > /sys/class/net/can0/mb0_id >> >> - extended if 0x1fffffff: >> echo 0x9fffffff > /sys/class/net/can0/mb0_id > > Maybe put something like this also in Documentation/ABI/testing? Perhaps
Good point. > a bit more explicit: Can this interface be used? Should it be used? Must > it be used? It can be used if your aren't satisfied with with default id of 0x7ff. 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 |
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
