# # Controller Area Network (CAN) network layer core configuration # menuconfig CAN depends on NET tristate "CAN bus subsystem support" ---help--- Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial communications protocol which was developed by Bosch in 1991, mainly for automotive, but now widely used in marine (NMEA2000), industrial, and medical applications. More information on the CAN network protocol family PF_CAN is contained in . If you want CAN support you should say Y here and also to the specific driver for your controller(s) below. if CAN config CAN_RAW tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" default y ---help--- The raw CAN protocol option offers access to the CAN bus via the BSD socket API. You probably want to use the raw socket in 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)" default y ---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. config CAN_GW tristate "CAN Gateway/Router (with netlink configuration)" default y ---help--- The CAN Gateway/Router is used to route (and modify) CAN frames. It is based on the PF_CAN core infrastructure for msg filtering and msg sending and can optionally modify routed CAN frames on the fly. CAN frames can be routed between CAN network interfaces (one hop). They can be modified with AND/OR/XOR/SET operations as configured by the netlink configuration interface known e.g. from iptables. source "drivers/net/can/Kconfig" endif
path: root/drivers/scsi/eata_pio.c
17-02-07
AgeCommit message (Expand)AuthorFilesLines
net: pending_confirm is not used anymoreJulian Anastasov1-1/+0
2017-02-07net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TPJulian Anastasov9-19/+44
2017-02-07net: add confirm_neigh method to dst_opsJulian Anastasov3-0/+54
2017-02-07tcp: replace dst_confirm with sk_dst_confirmJulian Anastasov3-14/+7
2017-02-07sctp: add dst_pending_confirm flagJulian Anastasov7-12/+31
2017-02-07net: add dst_pending_confirm flag to skbuffJulian Anastasov2-1/+5
2017-02-07sock: add sk_dst_pending_confirm flagJulian Anastasov1-0/+2
2017-02-07ipv6: sr: fix non static symbol warningsWei Yongjun1-4/+4
2017-02-07net/sched: act_mirred: remove duplicated include from act_mirred.cWei Yongjun1-2/+0
2017-02-07net: dsa: Add support for platform dataFlorian Fainelli1-18/+84
2017-02-07net: dsa: Rename and export dev_to_net_device()Florian Fainelli1-2/+3
2017-02-06bridge: fdb: write to used and updated at most once per jiffyNikolay Aleksandrov2-2/+4
2017-02-06bridge: move write-heavy fdb members in their own cache lineNikolay Aleksandrov1-4/+6
2017-02-06bridge: move to workqueue gcNikolay Aleksandrov10-23/+29
2017-02-06bridge: modify bridge and port to have often accessed fields in one cache lineNikolay Aleksandrov1-23/+20
2017-02-06net: dsa: introduce bridge notifierVivien Didelot2-11/+61
2017-02-06net: dsa: add switch notifierVivien Didelot5-0/+70
2017-02-06net: dsa: change state setter scopeVivien Didelot1-6/+9
2017-02-06net: dsa: rollback bridging on errorVivien Didelot1-1/+13
2017-02-06net: dsa: simplify netdevice events handlingVivien Didelot1-28/+16
2017-02-06net: dsa: move netdevice notifier registrationVivien Didelot3-10/+26
2017-02-06net-next: treewide use is_vlan_dev() helper function.Parav Pandit1-1/+2
2017-02-06sctp: process fwd tsn chunk only when prsctp is enabledXin Long1-0/+6
2017-02-06net: remove ndo_neigh_{construct, destroy} from stacked devicesIdo Schimmel