Kconfig (429da1cc841bc9f2e762fd7272fc2b80314b890a) Kconfig (f534e52f091a7b9f51fb6726710bdf731b663e94)
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---

--- 27 unchanged lines hidden (view full) ---

36 If unsure, say Y.
37
38config CAN_SJA1000
39 depends on CAN_DEV
40 tristate "Philips SJA1000"
41 ---help---
42 Driver for the SJA1000 CAN controllers from Philips or NXP
43
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---

--- 27 unchanged lines hidden (view full) ---

36 If unsure, say Y.
37
38config CAN_SJA1000
39 depends on CAN_DEV
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
44config CAN_DEBUG_DEVICES
45 bool "CAN devices debugging messages"
46 depends on CAN
47 default N
48 ---help---
49 Say Y here if you want the CAN device drivers to produce a bunch of
50 debug messages to the system log. Select this if you are having
51 a problem with CAN support and want to see more of what is going
52 on.
53
54endmenu
54config CAN_DEBUG_DEVICES
55 bool "CAN devices debugging messages"
56 depends on CAN
57 default N
58 ---help---
59 Say Y here if you want the CAN device drivers to produce a bunch of
60 debug messages to the system log. Select this if you are having
61 a problem with CAN support and want to see more of what is going
62 on.
63
64endmenu