Файловый менеджер - Редактировать - /var/www/xthruster/html/wp-content/uploads/flags/can.tar
Назад
Kconfig 0000644 00000004547 14722071505 0006064 0 ustar 00 # SPDX-License-Identifier: GPL-2.0-only # # Controller Area Network (CAN) network layer core configuration # menuconfig CAN depends on NET tristate "CAN bus subsystem support" ---help--- Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial communications protocol. Development of the CAN bus started in 1983 at Robert Bosch GmbH, and the protocol was officially released in 1986. The CAN bus was originally mainly for automotive, but is now widely used in marine (NMEA2000), industrial, and medical 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 specific driver for your controller(s) below. if CAN config CAN_RAW tristate "Raw CAN Protocol (raw access with CAN-ID filtering)" default y ---help--- The raw CAN protocol option offers access to the CAN bus via the BSD socket API. You probably want to use the raw socket in most cases where no higher level protocol is being used. The raw socket has several filter options e.g. ID masking / error frames. To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW. config CAN_BCM tristate "Broadcast Manager CAN Protocol (with content filtering)" default y ---help--- The Broadcast Manager offers content filtering, timeout monitoring, sending of RTR frames, and cyclic CAN messages without permanent user interaction. The BCM can be 'programmed' via the BSD socket API and informs you on demand e.g. only on content updates / timeouts. You probably want to use the bcm socket in most cases where cyclic CAN messages are used on the bus (e.g. in automotive environments). To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM. config CAN_GW tristate "CAN Gateway/Router (with netlink configuration)" default y ---help--- The CAN Gateway/Router is used to route (and modify) CAN frames. It is based on the PF_CAN core infrastructure for msg filtering and msg sending and can optionally modify routed CAN frames on the fly. CAN frames can be routed between CAN network interfaces (one hop). They can be modified with AND/OR/XOR/SET operations as configured by the netlink configuration interface known e.g. from iptables. source "net/can/j1939/Kconfig" source "drivers/net/can/Kconfig" endif j1939/Kconfig 0000644 00000000612 14722071505 0006630 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # SAE J1939 network layer core configuration # config CAN_J1939 tristate "SAE J1939" depends on CAN help SAE J1939 Say Y to have in-kernel support for j1939 socket type. This allows communication according to SAE j1939. The relevant parts in kernel are SAE j1939-21 (datalink & transport protocol) & SAE j1939-81 (network management). j1939/Makefile 0000644 00000000237 14722071505 0006770 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_CAN_J1939) += can-j1939.o can-j1939-objs := \ address-claim.o \ bus.o \ main.o \ socket.o \ transport.o Makefile 0000644 00000000566 14722071505 0006216 0 ustar 00 # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux Controller Area Network core. # obj-$(CONFIG_CAN) += can.o can-y := af_can.o can-$(CONFIG_PROC_FS) += proc.o obj-$(CONFIG_CAN_RAW) += can-raw.o can-raw-y := raw.o obj-$(CONFIG_CAN_BCM) += can-bcm.o can-bcm-y := bcm.o obj-$(CONFIG_CAN_GW) += can-gw.o can-gw-y := gw.o obj-$(CONFIG_CAN_J1939) += j1939/
| ver. 1.4 |
Github
|
.
| PHP 7.4.3-4ubuntu2.24 | Генерация страницы: 0 |
proxy
|
phpinfo
|
Настройка