config CAN_VCAN
tristate "Virtual Local CAN Interface (vcan)"
- depends on CAN
+ depends on CAN
default N
- ---help---
+ ---help---
Similar to the network loopback devices, vcan offers a
virtual local CAN interface.
config CAN_SLCAN
tristate "Serial / USB serial CAN Adaptors (slcan)"
- depends on CAN
+ depends on CAN && EXPERIMENTAL
default N
---help---
CAN driver for several 'low cost' CAN interfaces that are attached
This driver can also be built as a module. If so, the module
will be called slcan.
-config CAN_DEBUG_DEVICES
- bool "CAN devices debugging messages"
+config CAN_OLD_DRIVERS
+ tristate "Prompt for old CAN drivers (e.g. no sysfs support)"
depends on CAN
default N
---help---
- Say Y here if you want the CAN device drivers to produce a bunch of
- debug messages to the system log. Select this if you are having
- a problem with CAN support and want to see more of what is going
- on.
+ The old drivers do not support sysfs nor proper platform device
+ support. Some of the old drivers might only be configured by
+ module commandline options.
+
+if CAN_OLD_DRIVERS
+source "drivers/net/can/old/Kconfig"
+endif
+
+config CAN_DEV
+ tristate "Prompt for platform CAN drivers with netlink support"
+ depends on CAN && SYSFS
+ default Y
+ ---help---
+ Enables the common framework for platform CAN drivers with sysfs
+ support. This is the standard library for CAN drivers.
+ If unsure, say Y.
+
+config CAN_DEV_SYSFS
+ bool "Support for sysfs interface (deprecated)"
+ depends on CAN_DEV && SYSFS
+ default N
+ ---help---
+ Adds support for the legacy sysfs interface to configure CAN
+ devices. If possible, please use the new netlink interface
+ instead.
+ If unsure, say N.
+
+config CAN_CALC_BITTIMING
+ bool "CAN bit-timing calculation"
+ depends on CAN_DEV
+ default Y
+ ---help---
+ If enabled, CAN bit-timing parameters will be calculated for the
+ bit-rate specified via SYSFS file "bitrate" when the device gets
+ started. This works fine for the most common CAN controllers
+ with standard bit-rates but may fail for exotic bit-rates or CAN
+ source clock frequencies. Disabling saves some space, but then the
+ bit-timing parameters must be specified directly using the SYSFS
+ files "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
+ If unsure, say Y.
+
+config CAN_CC770
+ depends on HAS_IOMEM && CAN_DEV
+ tristate "Bosch CC770 and Intel AN82527"
+ ---help---
+ Driver for the Bosch CC770 and the compatible Intel AN82527
+ CAN controllers.
+
+config CAN_CC770_ISA
+ depends on CAN_CC770 && ISA
+ tristate "ISA Bus based legacy CC770 driver"
+ ---help---
+ This driver adds legacy support for CC770 and AN82527 chips
+ connected to the ISA bus using I/O port, memory mapped or
+ indirect access.
+
+config CAN_CC770_OF_PLATFORM
+ depends on CAN_CC770 && PPC_OF
+ tristate "Generic OF Platform Bus based CC770 driver"
+ ---help---
+ This driver adds support for the CC770 and other AN82527
+ compatible chips connected to the OpenFirmware "platform bus"
+ found on embedded systems with OpenFirmware bindings, e.g. if
+ you have a PowerPC based system you may want to enable this
+ option.
config CAN_SJA1000
- depends on CAN
+ depends on CAN_DEV
tristate "Philips SJA1000"
---help---
- The SJA1000 is one of the top CAN controllers out there. As it
- has a multiplexed interface it fits directly to 8051
- microcontrollers or into the PC I/O port space. The SJA1000
- is a full CAN controller, with shadow registers for RX and TX.
- It can send and receive any kinds of CAN frames (SFF/EFF/RTR)
- with a single (simple) filter setup.
+ Driver for the SJA1000 CAN controllers from Philips or NXP
-config CAN_I82527
- depends on CAN
- tristate "Intel 82527"
- ---help---
- The i82527 is a complex CAN controller that can handle RTR
- frame replies on it's own. This feature (and diffent RX filters)
- lead to an amount of 15 message objects (for RX & TX). Message
- object 15 has (as only) a shadow register for a reliable
- receiption of EFF or(!) SFF frames at high CAN traffic.
- This driver can send each type of CAN frames (SFF/EFF/RTR).
- Using 4 message objects it can also receive each type of CAN
- frames. But due to the onchip filter matching trigger method
- it is not possible to determine the received RTR CAN-ID.
- The reliable message object 15 receives SFF frames by default.
- This message object 15 usage maybe changed with the mo15 param.
+config CAN_SJA1000_ISA
+ depends on CAN_SJA1000 && ISA
+ tristate "ISA Bus based legacy SJA1000 driver"
+ ---help---
+ This driver adds legacy support for SJA1000 chips connected to
+ the ISA bus using I/O port, memory mapped or indirect access.
+
+config CAN_SJA1000_PLATFORM
+ depends on CAN_SJA1000
+ tristate "generic Platform Bus based SJA1000 driver"
+ ---help---
+ This driver adds support for the SJA1000 chips connected to
+ the "platform bus" (Linux abstraction for directly to the
+ processor attached devices). Which can be found on various
+ boards from Phytec (http://www.phytec.de) like the PCM027,
+ PCM038.
+
+config CAN_SJA1000_OF_PLATFORM
+ depends on CAN_SJA1000 && PPC_OF
+ tristate "Generic OF Platform Bus based SJA1000 driver"
+ ---help---
+ This driver adds support for the SJA1000 chips connected to
+ the OpenFirmware "platform bus" found on embedded systems with
+ OpenFirmware bindings, e.g. if you have a PowerPC based system
+ you may want to enable this option.
+
+config CAN_EMS_PCI
+ tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
+ depends on PCI && CAN_SJA1000
+ ---help---
+ This driver is for the one, two or four channel CPC-PCI,
+ CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
+ (http://www.ems-wuensche.de).
+
+config CAN_EMS_PCMCIA
+ tristate "EMS CPC-CARD Card"
+ depends on PCMCIA && CAN_SJA1000
+ ---help---
+ This driver is for the one or two channel CPC-CARD cards from
+ EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
+
+config CAN_EMS_104M
+ tristate "EMS CPC-104M Card"
+ depends on ISA && CAN_SJA1000
+ ---help---
+ This driver is for the one, two or four channel CPC-104M cards
+ from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de).
+
+config CAN_ESD_PCI
+ tristate "ESD PCI Cards"
+ depends on PCI && CAN_SJA1000
+ ---help---
+ This driver supports the esd PCI CAN cards CAN-PCI/200,
+ CAN-PCI/266, CAN-PMC/266 (PMC), CAN-CPCI/200 (CompactPCI),
+ CAN-PCIe2000 (PCI Express) and CAN-PCI104/200 (PCI104)
+ from the esd electronic system design gmbh (http://www.esd.eu).
+
+config CAN_IXXAT_PCI
+ tristate "IXXAT PCI Card"
+ depends on PCI && CAN_SJA1000
+ ---help---
+ This driver is for the IXXAT PC-I 04/PCI card (1 or 2 channel)
+ from the IXXAT Automation GmbH (http://www.ixxat.de).
+
+config CAN_PEAK_PCI
+ tristate "PEAK PCAN PCI Card"
+ depends on PCI && CAN_SJA1000
+ ---help---
+ This driver is for the PCAN PCI, the PC-PCI CAN plug-in card (1 or
+ 2 channel) from PEAK Systems (http://www.peak-system.com).
+
+config CAN_PIPCAN
+ depends on CAN_SJA1000
+ tristate "MPL PIPCAN CAN module driver (SJA1000)"
+ ---help---
+ This driver adds support for the PIPCAN module used on some SBC
+ boards from MPL AG (http://www.mpl.ch).
+
+config CAN_KVASER_PCI
+ tristate "Kvaser PCIcanx and Kvaser PCIcan PCI Cards"
+ depends on PCI && CAN_SJA1000
+ ---help---
+ This driver is for the the PCIcanx and PCIcan cards (1, 2 or
+ 4 channel) from Kvaser (http://www.kvaser.com).
+
+config CAN_ESD_PCI331
+ tristate "ESD CAN 331 Cards"
+ depends on PCI && CAN_DEV
+ ---help---
+ This driver supports the PCI/331, CPCI/331 and PMC/331 CAN cards
+ from the esd system design gmbh (http://www.esd.eu).
+
+config CAN_SOFTING
+ tristate "Softing Gmbh CAN generic support"
+ depends on CAN_DEV
+ ---help---
+ generic softing CAN cards
+ Sofing CAN cards come with 1 or 2 physical busses.
+ The API of the card does not allow fine control per bus, but
+ controls the 2 busses on the card together.
+ As such, some actions (start/stop/busoff recovery) on 1 bus
+ must bring down the other bus too temporarily.
+ You have been warned.
+ This driver is written on safe on 64bit, but not on big endian.
+
+config CAN_SOFTING_CS
+ tristate "Softing CAN pcmcia cards"
+ depends on CAN_SOFTING && PCMCIA
+ ---help---
+ Support for PCMCIA cards from Softing Gmbh & some cards
+ from Vector Gmbh.
+ You need firmware for these, which you can get at
+ http://developer.berlios.de/projects/socketcan/
+ This version of the driver is written against
+ firmware version 4.6
config CAN_MSCAN
- depends on CAN && (PPC || M68K || M68KNOMMU)
+ depends on CAN_DEV && (PPC || M68K || M68KNOMMU)
tristate "Support for a Freescale MSCAN based chips"
---help---
The Motorola Scalable Controller Area Network (MSCAN) definition
This driver can also be built as a module. If so, the module
will be called mpc52xx_can.
-endmenu
+config CAN_AT91
+ tristate "Atmel AT91 onchip CAN controller"
+ depends on CAN && ARCH_AT91SAM9263
+ default N
+ ---help---
+ This is a driver for the SoC CAN controller in Atmel's AT91SAM9263.
+config CAN_MCP251X
+ tristate "Microchip MCP251x SPI CAN controllers"
+ depends on CAN_DEV && SPI
+ ---help---
+ Driver for the Microchip MCP251x SPI CAN controllers.
+
+config CAN_DEBUG_DEVICES
+ bool "CAN devices debugging messages"
+ depends on CAN
+ default N
+ ---help---
+ Say Y here if you want the CAN device drivers to produce a bunch of
+ debug messages to the system log. Select this if you are having
+ a problem with CAN support and want to see more of what is going
+ on.
+
+endmenu
projects / socketcan-devel.git / blobdiff