This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author karlding
Recipients karlding
Date 2020-04-15.05:29:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586928559.09.0.469111314858.issue40291@roundup.psfhosted.org>
In-reply-to
Content
It would be nice to have support J1939 sockets.

Support for J1939 landed as part of the SAE J1939 SocketCAN patches, which are available after the Linux 5.4rc1 kernel. This is another protocol family for SocketCAN, much like the existing support for ISOTP and BCM.

Effectively, supporting this would hand off as much to the kernel as possible, which gives Python programs the ability deal with J1939 without having to implement the logic existing in the kernel in userspace.

This is provided to userspace [0] via the <linux/can/j1939.h> header.

I'd be happy to work on this and provide a PR.

[0] https://www.kernel.org/doc/html/latest/networking/j1939.html
History
Date User Action Args
2020-04-15 05:29:19karldingsetrecipients: + karlding
2020-04-15 05:29:19karldingsetmessageid: <1586928559.09.0.469111314858.issue40291@roundup.psfhosted.org>
2020-04-15 05:29:19karldinglinkissue40291 messages
2020-04-15 05:29:19karldingcreate