1 menu "CAN Device Drivers"
5 tristate "Virtual Local CAN Interface (vcan)"
9 Similar to the network loopback devices, vcan offers a
10 virtual local CAN interface.
12 This driver can also be built as a module. If so, the module
16 tristate "Serial / USB serial CAN Adaptors (slcan)"
20 CAN driver for several 'low cost' CAN interfaces that are attached
21 via serial lines or via USB-to-serial adapters using the LAWICEL
22 ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
24 As only the sending and receiving of CAN frames is implemented, this
25 driver should work with the (serial/USB) CAN hardware from:
26 www.canusb.com / www.can232.com / www.mictronics.de / www.canhack.de
28 Userspace tools to attach the SLCAN line discipline (slcan_attach,
29 slcand) can be found in the can-utils at the SocketCAN SVN, see
30 http://developer.berlios.de/projects/socketcan for details.
32 The slcan driver supports up to 10 CAN netdevices by default which
33 can be changed by the 'maxdev=xx' module option. This driver can
34 also be built as a module. If so, the module will be called slcan.
36 config CAN_OLD_DRIVERS
37 tristate "Prompt for old CAN drivers (e.g. no sysfs support)"
41 The old drivers do not support sysfs nor proper platform device
42 support. Some of the old drivers might only be configured by
43 module commandline options.
46 source "drivers/net/can/old/Kconfig"
50 tristate "Platform CAN drivers with Netlink support"
54 Enables the common framework for platform CAN drivers with Netlink
55 support. This is the standard library for CAN drivers.
59 bool "Support for sysfs interface (deprecated)"
60 depends on CAN_DEV && SYSFS
63 Adds support for the legacy sysfs interface to configure CAN
64 devices. If possible, please use the new netlink interface
68 config CAN_CALC_BITTIMING
69 bool "CAN bit-timing calculation"
73 If enabled, CAN bit-timing parameters will be calculated for the
74 bit-rate specified via Netlink argument "bitrate" when the device
75 get started. This works fine for the most common CAN controllers
76 with standard bit-rates but may fail for exotic bit-rates or CAN
77 source clock frequencies. Disabling saves some space, but then the
78 bit-timing parameters must be specified directly using the Netlink
79 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
83 tristate "ESD CAN 331 Cards"
84 depends on PCI && CAN_DEV
86 This driver supports the PCI/331, CPCI/331 and PMC/331 CAN cards
87 from the esd system design gmbh (http://www.esd.eu).
90 tristate "Softing Gmbh CAN generic support"
93 generic softing CAN cards
94 Sofing CAN cards come with 1 or 2 physical busses.
95 The API of the card does not allow fine control per bus, but
96 controls the 2 busses on the card together.
97 As such, some actions (start/stop/busoff recovery) on 1 bus
98 must bring down the other bus too temporarily.
100 This driver is written on safe on 64bit, but not on big endian.
102 config CAN_SOFTING_CS
103 tristate "Softing CAN pcmcia cards"
104 depends on CAN_SOFTING && PCMCIA
106 Support for PCMCIA cards from Softing Gmbh & some cards
108 You need firmware for these, which you can get at
109 http://developer.berlios.de/projects/socketcan/
110 This version of the driver is written against
114 tristate "Atmel AT91 onchip CAN controller"
115 depends on CAN_DEV && ARCH_AT91SAM9263
118 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
121 tristate "Microchip MCP251x SPI CAN controllers"
122 depends on CAN_DEV && SPI
124 Driver for the Microchip MCP251x SPI CAN controllers.
126 source "drivers/net/can/cc770/Kconfig"
128 source "drivers/net/can/mscan/Kconfig"
130 source "drivers/net/can/sja1000/Kconfig"
132 source "drivers/net/can/usb/Kconfig"
134 config CAN_DEBUG_DEVICES
135 bool "CAN devices debugging messages"
139 Say Y here if you want the CAN device drivers to produce a bunch of
140 debug messages to the system log. Select this if you are having
141 a problem with CAN support and want to see more of what is going