summaryrefslogtreecommitdiffstats
path: root/configs/fedora/generic/CONFIG_CAN_ISOTP
diff options
context:
space:
mode:
Diffstat (limited to 'configs/fedora/generic/CONFIG_CAN_ISOTP')
-rw-r--r--configs/fedora/generic/CONFIG_CAN_ISOTP25
1 files changed, 0 insertions, 25 deletions
diff --git a/configs/fedora/generic/CONFIG_CAN_ISOTP b/configs/fedora/generic/CONFIG_CAN_ISOTP
deleted file mode 100644
index 58dd572e7..000000000
--- a/configs/fedora/generic/CONFIG_CAN_ISOTP
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_CAN_ISOTP:
-#
-# CAN Transport Protocols offer support for segmented Point-to-Point
-# communication between CAN nodes via two defined CAN Identifiers.
-# As CAN frames can only transport a small amount of data bytes
-# (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
-# segmentation is needed to transport longer PDUs as needed e.g. for
-# vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
-# This protocol driver implements data transfers according to
-# ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
-# If you want to perform automotive vehicle diagnostic services (UDS),
-# say 'y'.
-#
-# Symbol: CAN_ISOTP [=n]
-# Type : tristate
-# Defined at net/can/Kconfig:58
-# Prompt: ISO 15765-2:2016 CAN transport protocol
-# Depends on: NET [=y] && CAN [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> CAN bus subsystem support (CAN [=m])
-#
-#
-#
-# CONFIG_CAN_ISOTP is not set