| Oliver Hartkopp | 0d66548 | 2007-11-16 15:52:17 -0800 | [diff] [blame] | 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. |
| Oliver Hartkopp | c18ce10 | 2007-11-16 15:53:09 -0800 | [diff] [blame^] | 18 | |
| 19 | config CAN_RAW |
| 20 | tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" |
| 21 | depends on CAN |
| 22 | default N |
| 23 | ---help--- |
| 24 | The raw CAN protocol option offers access to the CAN bus via |
| 25 | the BSD socket API. You probably want to use the raw socket in |
| 26 | most cases where no higher level protocol is being used. The raw |
| 27 | socket has several filter options e.g. ID masking / error frames. |
| 28 | To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. |