merge of bouyer-socketcan

[Manuel Bouyer]

Hello,
I'd like to merge the bouyer-socketcan branch to HEAD in the next few
days (hopefully early next week, or maybe sunday), unless someone objects
to the idea of a socketcan implementation in NetBSD.

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) in the branch.

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. The branch also includes 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.

A review of the code in src/sys/netcan/ is welcome, especially for possible
locking issues.

[Darren Reed]

Post by Manuel Bouyer
...
I'd like to merge the bouyer-socketcan branch to HEAD in the next few
days (hopefully early next week, or maybe sunday), unless someone objects
to the idea of a socketcan implementation in NetBSD.
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.
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4) in the branch.

...

As per the Google-Oracle Java fight in court whereupon APIs
were deemedas being copyright-able, it would seem to me that
implementing a Linuxcompatible interface that is GPL without
making the copy also GPL wouldbe a copyright violation of
the original work.Do you have permission from the original
authors to implement a non-GPL artifact of their interfaces?

Cheers,
Darren


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Manuel Bouyer]

Post by Darren Reed

Post by Manuel Bouyer
...
I'd like to merge the bouyer-socketcan branch to HEAD in the next few
days (hopefully early next week, or maybe sunday), unless someone objects
to the idea of a socketcan implementation in NetBSD.
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.
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4) in the branch.

...
As per the Google-Oracle Java fight in court whereupon APIs
were deemedas being copyright-able, it would seem to me that
implementing a Linuxcompatible interface that is GPL without
making the copy also GPL wouldbe a copyright violation of
the original work.Do you have permission from the original
authors to implement a non-GPL artifact of their interfaces?

I though only the implementation was copyrighted. I wrote the code
from the can.txt file, which doesn't have any reference to GPL.

[Christos Zoulas]

Post by Manuel Bouyer

Post by Darren Reed

Post by Manuel Bouyer
...
I'd like to merge the bouyer-socketcan branch to HEAD in the next few
days (hopefully early next week, or maybe sunday), unless someone objects
to the idea of a socketcan implementation in NetBSD.
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.
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4) in the branch.

...
As per the Google-Oracle Java fight in court whereupon APIs
were deemedas being copyright-able, it would seem to me that
implementing a Linuxcompatible interface that is GPL without
making the copy also GPL wouldbe a copyright violation of
the original work.Do you have permission from the original
authors to implement a non-GPL artifact of their interfaces?

I though only the implementation was copyrighted. I wrote the code
from the can.txt file, which doesn't have any reference to GPL.

1. https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google,_Inc.
Google's use of the API's was deemed fair use. Much of the lawsuit
was to determine if the implementation was copied too.
2. These kinds of text specifications are not under the GPL explicitly
to allow alternative commercial and opensource implementations in
order to foster interoperability.
3. It would set a horrible precedence for a GPL entity to fight against
other opensource entities for re-implementing API's. There is nothing
to be gained but lawyer fees and bad blood.

christos


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de