Oliver Hartkopp

> Guess not. But still probably a bug in the xilinx driver. This could be either a bug in the driver - or even in the xilinx CAN IP core....

Nothing looks wrong here. You get traffic from can0 that is routed to vcan0 and you get traffic from vcan1 that is routed to can1. There is no connection between...

So what is your problem then? There are different filters too.

So you want an example to configure the Linux isotp socket (in your C code) to provide a padding with 0x00 as shown on stackoverflow?

Please send the output of `uname -a` and `cat /sys/module/can_isotp/parameters/max_pdu_size`

Please send the output of `uname -a`

> we are currently trying to use a bootloader (https://github.com/qnx425/PIC18FXXK80-CAN-Bootloader) with one of our microcontrollers. Since we have a physical CAN module on our RPI (5.4.65-v7 custom kernel) compatible solution...

Hi David, the cangw kernel module only supports ONE filter that _may_ be inverse. The can_raw sockets support MULTIPLE filters that can be passed to the kernel with the `CAN_RAW_FILTER`...

this commit should be "canlogserver: fix termination after signal" Because before that there was a proper exit of the application. Also please add a "Fixes:" tag into the commit message.

This might be correct. Can you post the section of the log file that led to this output?