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 "Platform CAN drivers with Netlink support"
20 Enables the common framework for platform CAN drivers with Netlink
21 support. This is the standard library for CAN drivers.
24 config CAN_CALC_BITTIMING
25 bool "CAN bit-timing calculation"
29 If enabled, CAN bit-timing parameters will be calculated for the
30 bit-rate specified via Netlink argument "bitrate" when the device
31 get started. This works fine for the most common CAN controllers
32 with standard bit-rates but may fail for exotic bit-rates or CAN
33 source clock frequencies. Disabling saves some space, but then the
34 bit-timing parameters must be specified directly using the Netlink
35 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
39 depends on CAN_DEV && HAS_IOMEM
40 tristate "Philips SJA1000"
42 Driver for the SJA1000 CAN controllers from Philips or NXP
44 config CAN_SJA1000_ISA
45 depends on CAN_SJA1000 && ISA
46 tristate "ISA Bus based legacy SJA1000 driver"
48 This driver adds legacy support for SJA1000 chips connected to
49 the ISA bus using I/O port, memory mapped or indirect access.
51 config CAN_SJA1000_PLATFORM
52 depends on CAN_SJA1000
53 tristate "Generic Platform Bus based SJA1000 driver"
55 This driver adds support for the SJA1000 chips connected to
56 the "platform bus" (Linux abstraction for directly to the
57 processor attached devices). Which can be found on various
58 boards from Phytec (http://www.phytec.de) like the PCM027,
61 config CAN_SJA1000_OF_PLATFORM
62 depends on CAN_SJA1000 && PPC_OF
63 tristate "Generic OF Platform Bus based SJA1000 driver"
65 This driver adds support for the SJA1000 chips connected to
66 the OpenFirmware "platform bus" found on embedded systems with
67 OpenFirmware bindings, e.g. if you have a PowerPC based system
68 you may want to enable this option.
71 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
72 depends on PCI && CAN_SJA1000
74 This driver is for the one, two or four channel CPC-PCI,
75 CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
76 (http://www.ems-wuensche.de).
79 tristate "EMS CPC-USB/ARM7 CAN/USB interface"
80 depends on USB && CAN_DEV
82 This driver is for the one channel CPC-USB/ARM7 CAN/USB interface
83 from from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
86 tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
87 depends on PCI && CAN_SJA1000
89 This driver is for the the PCIcanx and PCIcan cards (1, 2 or
90 4 channel) from Kvaser (http://www.kvaser.com).
93 tristate "Atmel AT91 onchip CAN controller"
94 depends on CAN && CAN_DEV && ARCH_AT91SAM9263
96 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
99 depends on CAN_DEV && ARCH_OMAP3
100 tristate "TI High End CAN Controller"
102 Driver for TI HECC (High End CAN Controller) module found on many
103 TI devices. The device specifications are available from www.ti.com
106 tristate "Microchip MCP251x SPI CAN controllers"
107 depends on CAN_DEV && SPI
109 Driver for the Microchip MCP251x SPI CAN controllers.
112 depends on CAN_DEV && (PPC || M68K || M68KNOMMU)
113 tristate "Support for Freescale MSCAN based chips"
115 The Motorola Scalable Controller Area Network (MSCAN) definition
116 is based on the MSCAN12 definition which is the specific
117 implementation of the Motorola Scalable CAN concept targeted for
118 the Motorola MC68HC12 Microcontroller Family.
121 tristate "Freescale MPC5xxx onboard CAN controller"
122 depends on CAN_MSCAN && PPC_MPC52xx
124 If you say yes here you get support for Freescale's MPC52xx
125 onboard dualCAN controller.
127 This driver can also be built as a module. If so, the module
128 will be called mpc5xxx_can.
130 config CAN_DEBUG_DEVICES
131 bool "CAN devices debugging messages"
135 Say Y here if you want the CAN device drivers to produce a bunch of
136 debug messages to the system log. Select this if you are having
137 a problem with CAN support and want to see more of what is going