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 This driver can also be built as a module. If so, the module
27 config CAN_DEBUG_DEVICES
28 bool "CAN devices debugging messages"
32 Say Y here if you want the CAN device drivers to produce a bunch of
33 debug messages to the system log. Select this if you are having
34 a problem with CAN support and want to see more of what is going
39 tristate "Philips SJA1000"
41 The SJA1000 is one of the top CAN controllers out there. As it
42 has a multiplexed interface it fits directly to 8051
43 microcontrollers or into the PC I/O port space. The SJA1000
44 is a full CAN controller, with shadow registers for RX and TX.
45 It can send and receive any kinds of CAN frames (SFF/EFF/RTR)
46 with a single (simple) filter setup.
50 tristate "Intel 82527"
52 The i82527 is a complex CAN controller that can handle RTR
53 frame replies on it's own. This feature (and diffent RX filters)
54 lead to an amount of 15 message objects (for RX & TX). Message
55 object 15 has (as only) a shadow register for a reliable
56 receiption of EFF or(!) SFF frames at high CAN traffic.
57 This driver can send each type of CAN frames (SFF/EFF/RTR).
58 Using 4 message objects it can also receive each type of CAN
59 frames. But due to the onchip filter matching trigger method
60 it is not possible to determine the received RTR CAN-ID.
61 The reliable message object 15 receives SFF frames by default.
62 This message object 15 usage maybe changed with the mo15 param.
65 depends on CAN && (PPC || M68K || M68KNOMMU)
66 tristate "Support for a Freescale MSCAN based chips"
68 The Motorola Scalable Controller Area Network (MSCAN) definition
69 is based on the MSCAN12 definition which is the specific
70 implementation of the Motorola Scalable CAN concept targeted for
71 the Motorola MC68HC12 Microcontroller Family.
74 tristate "Freescale MPC5200 onboard CAN controller"
75 depends on CAN_MSCAN && (PPC_MPC52xx || PPC_52xx)
78 If you say yes here you get support for Freescale MPC5200
79 onboard dualCAN controller.
81 This driver can also be built as a module. If so, the module
82 will be called mpc52xx_can.