summaryrefslogtreecommitdiff
path: root/net/can/Kconfig
diff options
context:
space:
mode:
authorOliver Hartkopp <oliver.hartkopp@volkswagen.de>2007-11-16 15:53:52 -0800
committerDavid S. Miller <davem@davemloft.net>2008-01-28 14:54:11 -0800
commitffd980f976e7fd666c2e61bf8ab35107efd11828 (patch)
tree78ac4c20961ad5607b162cf0bc43a8cfc0a009ee /net/can/Kconfig
parentc18ce101f2e47d97ace125033e2896895a6db3dd (diff)
[CAN]: Add broadcast manager (bcm) protocol
This patch adds the CAN broadcast manager (bcm) protocol. Signed-off-by: Oliver Hartkopp <oliver.hartkopp@volkswagen.de> Signed-off-by: Urs Thuermann <urs.thuermann@volkswagen.de> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/can/Kconfig')
-rw-r--r--net/can/Kconfig13
1 files changed, 13 insertions, 0 deletions
diff --git a/net/can/Kconfig b/net/can/Kconfig
index 4718d1f50ab3..182b96b80ebc 100644
--- a/net/can/Kconfig
+++ b/net/can/Kconfig
@@ -26,3 +26,16 @@ config CAN_RAW
most cases where no higher level protocol is being used. The raw
socket has several filter options e.g. ID masking / error frames.
To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
+
+config CAN_BCM
+ tristate "Broadcast Manager CAN Protocol (with content filtering)"
+ depends on CAN
+ default N
+ ---help---
+ The Broadcast Manager offers content filtering, timeout monitoring,
+ sending of RTR frames, and cyclic CAN messages without permanent user
+ interaction. The BCM can be 'programmed' via the BSD socket API and
+ informs you on demand e.g. only on content updates / timeouts.
+ You probably want to use the bcm socket in most cases where cyclic
+ CAN messages are used on the bus (e.g. in automotive environments).
+ To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.