1menu "CAN Device Drivers" 2 depends on CAN 3 4config CAN_VCAN 5 tristate "Virtual Local CAN Interface (vcan)" 6 depends on CAN 7 default N 8 ---help--- 9 Similar to the network loopback devices, vcan offers a 10 virtual local CAN interface. 11 12 This driver can also be built as a module. If so, the module 13 will be called vcan. 14 15config CAN_DEV 16 tristate "Platform CAN drivers with Netlink support" 17 depends on CAN 18 default Y 19 ---help--- 20 Enables the common framework for platform CAN drivers with Netlink 21 support. This is the standard library for CAN drivers. 22 If unsure, say Y. 23 24config CAN_CALC_BITTIMING 25 bool "CAN bit-timing calculation" 26 depends on CAN_DEV 27 default Y 28 ---help--- 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". 36 If unsure, say Y. 37 38config CAN_SJA1000 39 depends on CAN_DEV && HAS_IOMEM 40 tristate "Philips SJA1000" 41 ---help--- 42 Driver for the SJA1000 CAN controllers from Philips or NXP 43 44config CAN_SJA1000_PLATFORM 45 depends on CAN_SJA1000 46 tristate "Generic Platform Bus based SJA1000 driver" 47 ---help--- 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, 52 PCM038. 53 54config CAN_SJA1000_OF_PLATFORM 55 depends on CAN_SJA1000 && PPC_OF 56 tristate "Generic OF Platform Bus based SJA1000 driver" 57 ---help--- 58 This driver adds support for the SJA1000 chips connected to 59 the OpenFirmware "platform bus" found on embedded systems with 60 OpenFirmware bindings, e.g. if you have a PowerPC based system 61 you may want to enable this option. 62 63config CAN_EMS_PCI 64 tristate "EMS CPC-PCI and CPC-PCIe Card" 65 depends on PCI && CAN_SJA1000 66 ---help--- 67 This driver is for the one or two channel CPC-PCI and CPC-PCIe 68 cards from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). 69 70config CAN_KVASER_PCI 71 tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards" 72 depends on PCI && CAN_SJA1000 73 ---help--- 74 This driver is for the the PCIcanx and PCIcan cards (1, 2 or 75 4 channel) from Kvaser (http://www.kvaser.com). 76 77config CAN_DEBUG_DEVICES 78 bool "CAN devices debugging messages" 79 depends on CAN 80 default N 81 ---help--- 82 Say Y here if you want the CAN device drivers to produce a bunch of 83 debug messages to the system log. Select this if you are having 84 a problem with CAN support and want to see more of what is going 85 on. 86 87endmenu 88