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)"
17 depends on CAN && EXPERIMENTAL
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 This driver can also be built as a module. If so, the module
27 config CAN_OLD_DRIVERS
28 tristate "Prompt for old CAN drivers (e.g. no sysfs support)"
32 The old drivers do not support sysfs nor proper platform device
33 support. Some of the old drivers might only be configured by
34 module commandline options.
37 source "drivers/net/can/old/Kconfig"
41 tristate "Prompt for platform CAN drivers with sysfs support"
42 depends on CAN && SYSFS
45 Enables the common framework for platform CAN drivers with sysfs
46 support. This is the standard library for CAN drivers.
49 config CAN_CALC_BITTIMING
50 bool "CAN bit-timing calculation"
54 If enabled, CAN bit-timing parameters will be calculated for the
55 bit-rate specified via SYSFS file "bitrate" when the device gets
56 started. This works fine for the most common CAN controllers
57 with standard bit-rates but may fail for exotic bit-rates or CAN
58 source clock frequencies. Disabling saves some space, but then the
59 bit-timing parameters must be specified directly using the SYSFS
60 files "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
65 tristate "Philips SJA1000"
67 The SJA1000 is one of the top CAN controllers out there. As it
68 has a multiplexed interface it fits directly to 8051
69 microcontrollers or into the PC I/O port space. The SJA1000
70 is a full CAN controller, with shadow registers for RX and TX.
71 It can send and receive any kinds of CAN frames (SFF/EFF/RTR)
72 with a single (simple) filter setup.
74 This driver will use the new device interface.
76 config CAN_SJA1000_PLATFORM
77 depends on CAN_SJA1000
78 tristate "generic Platform Bus based SJA1000 driver"
80 This driver adds support for the SJA1000 chips connected to
81 the "platform bus" (Linux abstraction for directly to the
82 processor attached devices). Which can be found on various
83 boards from Phytec (http://www.phytec.de) like the PCM027,
86 config CAN_SJA1000_OF_PLATFORM
87 depends on CAN_SJA1000 && PPC_OF
88 tristate "generic OF Platform Bus based SJA1000 driver"
90 This driver adds support for the SJA1000 chips connected to
91 the OpenFirmware "platform bus" found on embedded systems with
92 OpenFirmware bindings, e.g. if you have a PowerPC based system
93 you should enable this option.
96 tristate "EMS CPC-PCI and CPC-PCIe Card"
97 depends on PCI && CAN_SJA1000
99 This driver is for the one or two channel CPC-PCI and CPC-PCIe
100 cards from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
102 config CAN_EMS_PCMCIA
103 tristate "EMS CPC-CARD Card"
104 depends on PCMCIA && CAN_SJA1000
106 This driver is for the one or two channel CPC-CARD cards from
107 EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
110 tristate "ESD PCI Cards"
111 depends on PCI && CAN_SJA1000
113 This driver supports the esd PCI CAN cards CAN-PCI/200,
114 CAN-PCI/266, CAN-PMC/266 (PMC), CAN-CPCI/200 (CompactPCI),
115 CAN-PCIe2000 (PCI Express) and CAN-PCI104/200 (PCI104)
116 from the esd electronic system design gmbh (http://www.esd.eu).
119 tristate "IXXAT PCI Card"
120 depends on PCI && CAN_SJA1000
122 This driver is for the IXXAT PC-I 04/PCI card (1 or 2 channel)
123 from the IXXAT Automation GmbH (http://www.ixxat.de).
126 tristate "PEAK PCAN PCI Card"
127 depends on PCI && CAN_SJA1000
129 This driver is for the PCAN PCI, the PC-PCI CAN plug-in card (1 or
130 2 channel) from PEAK Systems (http://www.peak-system.com).
133 depends on CAN_SJA1000
134 tristate "MPL PIPCAN CAN module driver (SJA1000)"
136 This driver adds support for the PIPCAN module used on some SBC
137 boards from MPL AG (http://www.mpl.ch).
139 config CAN_KVASER_PCI
140 tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
141 depends on PCI && CAN_SJA1000
143 This driver is for the the PCIcanx and PCIcan cards (1, 2 or
144 4 channel) from Kvaser (http://www.kvaser.com).
147 tristate "Softing Gmbh CAN generic support"
150 generic softing CAN cards
152 config CAN_SOFTING_CS
153 tristate "Softing CAN pcmcia cards"
154 depends on CAN_SOFTING && PCMCIA
157 depends on CAN_DEV && (PPC || M68K || M68KNOMMU)
158 tristate "Support for a Freescale MSCAN based chips"
160 The Motorola Scalable Controller Area Network (MSCAN) definition
161 is based on the MSCAN12 definition which is the specific
162 implementation of the Motorola Scalable CAN concept targeted for
163 the Motorola MC68HC12 Microcontroller Family.
166 tristate "Freescale MPC5200 onboard CAN controller"
167 depends on CAN_MSCAN && (PPC_MPC52xx || PPC_52xx)
170 If you say yes here you get support for Freescale MPC5200
171 onboard dualCAN controller.
173 This driver can also be built as a module. If so, the module
174 will be called mpc52xx_can.
177 tristate "Atmel AT91 onchip CAN controller"
178 depends on CAN && ARCH_AT91SAM9263
181 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
184 tristate "Microchip MCP251x SPI CAN controllers"
185 depends on CAN_DEV && SPI
187 Driver for the Microchip MCP251x SPI CAN controllers.
189 config CAN_DEBUG_DEVICES
190 bool "CAN devices debugging messages"
194 Say Y here if you want the CAN device drivers to produce a bunch of
195 debug messages to the system log. Select this if you are having
196 a problem with CAN support and want to see more of what is going