RE: Suggestion to have a functional addressing/broadcast option for ISO-TP sockets

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Oliver,

On 03.12.20 21:32, Oliver Hartkopp wrote:
> On 02.12.20 16:42, Oliver Hartkopp wrote:
> > On 02.12.20 15:58, Thomas Wagner wrote:
> >> I would much prefer to work of the GitHub repo if possible, as I don't
> >> have a setup for newer kernels with CAN hardware.
> >
> > Ok. Will send a notification here when the RFC code is ready to test.
> 
> I added a branch sf_broadcast to the repo:
> https://github.com/hartkopp/can-isotp/commits/sf_broadcast

I pulled the branch and tested the flag by simply replacing my previous implementation
that used the RAW sockets. Works wonderfully loaded into the Ubuntu 5.4.0-56 and
a 2.6.31 custom kernel. I can ditch all the RX-path-settings and just use the flag without
any errors. EINVAL gets triggered as expected for too long messages.  All default ISO-TP 
sockets stay unharmed. Wonderful, thanks for the quick solution!

Regards
Thomas




[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux