can: Kconfig: correct history of the CAN protocol
Current history of CAN protocol is wrong, fix it in the Kconfig file. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Acked-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
This commit is contained in:
parent
64d6ce8fe4
commit
26bca9fe5f
|
@ -8,11 +8,12 @@ menuconfig CAN
|
||||||
tristate "CAN bus subsystem support"
|
tristate "CAN bus subsystem support"
|
||||||
---help---
|
---help---
|
||||||
Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
|
Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
|
||||||
communications protocol which was developed by Bosch in
|
communications protocol. Development of the CAN bus started in
|
||||||
1991, mainly for automotive, but now widely used in marine
|
1983 at Robert Bosch GmbH, and the protocol was officially
|
||||||
(NMEA2000), industrial, and medical applications.
|
released in 1986. The CAN bus was originally mainly for automotive,
|
||||||
More information on the CAN network protocol family PF_CAN
|
but is now widely used in marine (NMEA2000), industrial, and medical
|
||||||
is contained in <Documentation/networking/can.rst>.
|
applications. More information on the CAN network protocol family
|
||||||
|
PF_CAN is contained in <Documentation/networking/can.rst>.
|
||||||
|
|
||||||
If you want CAN support you should say Y here and also to the
|
If you want CAN support you should say Y here and also to the
|
||||||
specific driver for your controller(s) below.
|
specific driver for your controller(s) below.
|
||||||
|
|
Loading…
Reference in New Issue