X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=net%2Fcan%2FKconfig;h=89395b2c8bcaf6d41b4f84b37d02beec643f2fee;hb=00e9028a95fb8a4d79f2fb695a853f33ea7d3b57;hp=4718d1f50ab39554bc3063f612053138cdafb9ee;hpb=c18ce101f2e47d97ace125033e2896895a6db3dd;p=linux-2.6

diff --git a/net/can/Kconfig b/net/can/Kconfig
index 4718d1f50a..89395b2c8b 100644
--- a/net/can/Kconfig
+++ b/net/can/Kconfig
@@ -26,3 +26,19 @@ 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.
+
+
+source "drivers/net/can/Kconfig"