6e4cb2b9ab
CAN stands for Controller Area Network, a broadcast network used in automation and automotive fields. For example, the NMEA2000 standard developped for marine devices uses a CAN network as the link layer. This is an implementation of the linux socketcan API: https://www.kernel.org/doc/Documentation/networking/can.txt you can also see can(4). This adds a new socket family (AF_CAN) and protocol (PF_CAN), as well as the canconfig(8) utility, used to set timing parameter of CAN hardware. Also inclued is a driver for the CAN controller found in the allwinner A20 SoC (I tested it with an Olimex lime2 board, connected with PIC18-based CAN devices). There is also the canloop(4) pseudo-device, which allows to use the socketcan API without CAN hardware. At this time the CANFD part of the linux socketcan API is not implemented. Error frames are not implemented either. But I could get the cansend and canreceive utilities from the canutils package to build and run with minimal changes. tcpudmp(8) can also be used to record frames, which can be decoded with etherreal.
22 lines
541 B
Makefile
22 lines
541 B
Makefile
# $NetBSD: Makefile,v 1.80 2017/05/27 21:02:55 bouyer Exp $
|
|
|
|
.include <bsd.own.mk>
|
|
|
|
SUBDIR= altq arch compat dev fs miscfs \
|
|
net net80211 netatalk netbt netcan netipsec netinet netinet6 \
|
|
netisdn netkey netmpls netnatm netsmb \
|
|
nfs opencrypto sys ufs uvm
|
|
|
|
# interrupt implementation depends on the kernel within the port
|
|
#.if (${MACHINE} != "evbppc")
|
|
.if make(obj) || make(cleandir) || ${MKKMOD} != "no"
|
|
SUBDIR+=modules
|
|
.endif
|
|
#.endif
|
|
|
|
.if make(includes) || make(obj) || make(cleandir)
|
|
SUBDIR+= rump
|
|
.endif
|
|
|
|
.include <bsd.kinc.mk>
|