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".
40 tristate "Philips SJA1000"
42 Driver for the SJA1000 CAN controllers from Philips or NXP
44 config CAN_SJA1000_PLATFORM
45 depends on CAN_SJA1000
46 tristate "Generic Platform Bus based SJA1000 driver"
48 This driver adds support for the SJA1000 chips connected to
49 the "platform bus" (Linux abstraction for directly to the
50 processor attached devices). Which can be found on various
51 boards from Phytec (http://www.phytec.de) like the PCM027,
55 tristate "EMS CPC-PCI and CPC-PCIe Card"
56 depends on PCI && CAN_SJA1000
58 This driver is for the one or two channel CPC-PCI and CPC-PCIe
59 cards from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
61 config CAN_DEBUG_DEVICES
62 bool "CAN devices debugging messages"
66 Say Y here if you want the CAN device drivers to produce a bunch of
67 debug messages to the system log. Select this if you are having
68 a problem with CAN support and want to see more of what is going