10d66548aSOliver Hartkopp# 20d66548aSOliver Hartkopp# Controller Area Network (CAN) network layer core configuration 30d66548aSOliver Hartkopp# 40d66548aSOliver Hartkopp 50d66548aSOliver Hartkoppmenuconfig CAN 60d66548aSOliver Hartkopp depends on NET 70d66548aSOliver Hartkopp tristate "CAN bus subsystem support" 80d66548aSOliver Hartkopp ---help--- 90d66548aSOliver Hartkopp Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial 100d66548aSOliver Hartkopp communications protocol which was developed by Bosch in 110d66548aSOliver Hartkopp 1991, mainly for automotive, but now widely used in marine 120d66548aSOliver Hartkopp (NMEA2000), industrial, and medical applications. 130d66548aSOliver Hartkopp More information on the CAN network protocol family PF_CAN 140d66548aSOliver Hartkopp is contained in <Documentation/networking/can.txt>. 150d66548aSOliver Hartkopp 160d66548aSOliver Hartkopp If you want CAN support you should say Y here and also to the 170d66548aSOliver Hartkopp specific driver for your controller(s) below. 18*c18ce101SOliver Hartkopp 19*c18ce101SOliver Hartkoppconfig CAN_RAW 20*c18ce101SOliver Hartkopp tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" 21*c18ce101SOliver Hartkopp depends on CAN 22*c18ce101SOliver Hartkopp default N 23*c18ce101SOliver Hartkopp ---help--- 24*c18ce101SOliver Hartkopp The raw CAN protocol option offers access to the CAN bus via 25*c18ce101SOliver Hartkopp the BSD socket API. You probably want to use the raw socket in 26*c18ce101SOliver Hartkopp most cases where no higher level protocol is being used. The raw 27*c18ce101SOliver Hartkopp socket has several filter options e.g. ID masking / error frames. 28*c18ce101SOliver Hartkopp To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. 29