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.
via serial lines or via USB-to-serial adapters using the LAWICEL
ASCII protocol. The driver implements the tty linediscipline N_SLCAN.
- This driver can also be built as a module. If so, the module
- will be called slcan.
+ As only the sending and receiving of CAN frames is implemented, this
+ driver should work with the (serial/USB) CAN hardware from:
+ www.canusb.com / www.can232.com / www.mictronic.com / www.canhack.de
-config CAN_DEBUG_DEVICES
- bool "CAN devices debugging messages"
+ Userspace tools to attach the SLCAN line discipline (slcan_attach,
+ slcand) can be found in the can-utils at the SocketCAN SVN, see
+ http://developer.berlios.de/projects/socketcan for details.
+
+ The slcan driver supports up to 10 CAN netdevices by default which
+ can be changed by the 'maxdev=xx' module option. This driver can
+ also be built as a module. If so, the module will be called slcan.
+
+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.
-config CAN_SJA1000
+if CAN_OLD_DRIVERS
+source "drivers/net/can/old/Kconfig"
+endif
+
+config CAN_DEV
+ tristate "Platform CAN drivers with Netlink support"
depends on CAN
- tristate "Philips SJA1000"
+ default Y
---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.
-
-config CAN_I82527
- depends on CAN
- tristate "Intel 82527"
+ Enables the common framework for platform CAN drivers with Netlink
+ 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---
- 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_MSCAN
- depends on CAN && (PPC || M68K || M68KNOMMU)
- tristate "Support for a Freescale MSCAN based chips"
+ 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---
- The Motorola Scalable Controller Area Network (MSCAN) definition
- is based on the MSCAN12 definition which is the specific
- implementation of the Motorola Scalable CAN concept targeted for
- the Motorola MC68HC12 Microcontroller Family.
-
-config CAN_MPC52XX
- tristate "Freescale MPC5200 onboard CAN controller"
- depends on CAN_MSCAN && (PPC_MPC52xx || PPC_52xx)
- default LITE5200
+ If enabled, CAN bit-timing parameters will be calculated for the
+ bit-rate specified via Netlink argument "bitrate" when the device
+ get 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 Netlink
+ arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
+ If unsure, say Y.
+
+config CAN_ESD_PCI331
+ tristate "ESD CAN 331 Cards"
+ depends on PCI && CAN_DEV
---help---
- If you say yes here you get support for Freescale MPC5200
- onboard dualCAN controller.
+ This driver supports the PCI/331, CPCI/331 and PMC/331 CAN cards
+ from the esd system design gmbh (http://www.esd.eu).
- This driver can also be built as a module. If so, the module
- will be called mpc52xx_can.
+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.
-endmenu
+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_AT91
+ tristate "Atmel AT91 onchip CAN controller"
+ depends on CAN_DEV && 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.
+
+source "drivers/net/can/cc770/Kconfig"
+
+source "drivers/net/can/mscan/Kconfig"
+
+source "drivers/net/can/sja1000/Kconfig"
+
+source "drivers/net/can/usb/Kconfig"
+
+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