Root/
1 | # |
2 | # Controller Area Network (CAN) network layer core configuration |
3 | # |
4 | |
5 | menuconfig CAN |
6 | depends on NET |
7 | tristate "CAN bus subsystem support" |
8 | ---help--- |
9 | Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial |
10 | communications protocol which was developed by Bosch in |
11 | 1991, mainly for automotive, but now widely used in marine |
12 | (NMEA2000), industrial, and medical applications. |
13 | More information on the CAN network protocol family PF_CAN |
14 | is contained in <Documentation/networking/can.txt>. |
15 | |
16 | If you want CAN support you should say Y here and also to the |
17 | specific driver for your controller(s) below. |
18 | |
19 | if CAN |
20 | |
21 | config CAN_RAW |
22 | tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" |
23 | default y |
24 | ---help--- |
25 | The raw CAN protocol option offers access to the CAN bus via |
26 | the BSD socket API. You probably want to use the raw socket in |
27 | most cases where no higher level protocol is being used. The raw |
28 | socket has several filter options e.g. ID masking / error frames. |
29 | To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. |
30 | |
31 | config CAN_BCM |
32 | tristate "Broadcast Manager CAN Protocol (with content filtering)" |
33 | default y |
34 | ---help--- |
35 | The Broadcast Manager offers content filtering, timeout monitoring, |
36 | sending of RTR frames, and cyclic CAN messages without permanent user |
37 | interaction. The BCM can be 'programmed' via the BSD socket API and |
38 | informs you on demand e.g. only on content updates / timeouts. |
39 | You probably want to use the bcm socket in most cases where cyclic |
40 | CAN messages are used on the bus (e.g. in automotive environments). |
41 | To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM. |
42 | |
43 | config CAN_GW |
44 | tristate "CAN Gateway/Router (with netlink configuration)" |
45 | default y |
46 | ---help--- |
47 | The CAN Gateway/Router is used to route (and modify) CAN frames. |
48 | It is based on the PF_CAN core infrastructure for msg filtering and |
49 | msg sending and can optionally modify routed CAN frames on the fly. |
50 | CAN frames can be routed between CAN network interfaces (one hop). |
51 | They can be modified with AND/OR/XOR/SET operations as configured |
52 | by the netlink configuration interface known e.g. from iptables. |
53 | |
54 | source "drivers/net/can/Kconfig" |
55 | |
56 | endif |
57 |
Branches:
ben-wpan
ben-wpan-stefan
javiroman/ks7010
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9