History log of /netbsd-src/sys/rump/net/lib/libnetcan/netcan_component.c (Results 1 – 4 of 4)
Revision Date Author Comments
# 6ffff4f2 03-Sep-2022 thorpej <thorpej@NetBSD.org>

Garbage-collect the remaining vestiges of netisr.


# ca257ba4 03-Sep-2022 thorpej <thorpej@NetBSD.org>

Convert CAN from a legacy netisr to pktqueue.


# 95e145a8 21-Jul-2020 pgoyette <pgoyette@NetBSD.org>

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@


# 6e4cb2b9 27-May-2017 bouyer <bouyer@NetBSD.org>

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 mar

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.

show more ...