CVS log for src/sys/rump/net/lib/libnetcan/netcan_component.c

Up to [cvs.NetBSD.org] / src / sys / rump / net / lib / libnetcan

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

Garbage-collect the remaining vestiges of netisr.

Convert CAN from a legacy netisr to pktqueue.

Remove spurious call to canloopinit() in an attempt to fix kern/55489

This attempt at fixing is a result of IRC discussions with martin@ and
riastradh@

update from HEAD

Sync with HEAD

file netcan_component.c was added on branch tls-maxphys on 2017-12-03 11:39:18 +0000

file netcan_component.c was added on branch nick-nhusb on 2017-08-28 17:53:15 +0000

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.

Initial commit of a CAN socket layer, compatible with linux SoccketCAN
(but incomplete). Based on work from Robert Swindells.

file netcan_component.c was initially added on branch bouyer-socketcan.