Up to [cvs.NetBSD.org] / src / sys / kern
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: netbsd-8-base
Revision 1.255 / (download) - annotate - [select for diffs], Sat May 27 21:02:56 2017 UTC (6 years, 9 months ago) by bouyer
Branch: MAIN
CVS Tags: netbsd-8-base,
matt-nb8-mediatek-base,
matt-nb8-mediatek
Branch point for: netbsd-8
Changes since 1.254: +3 -2
lines
Diff to previous 1.254 (colored)
merge the bouyer-socketcan branch to HEAD. 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.