Re: can-isotp: TX stmin violations

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

 



Hi Maik,

On 20.04.22 11:34, Maik Allgöwer wrote:

so I hoped I would not have to bother anyone with this issue again,
but our customer wants this fixed.

I am wondering whether someone could point me into the right direction?

In the upcoming Linux 5.18 I reworked the consecutive frame transmission flow in a way that the next CF is only started after the last frame has been sent successfully:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4b7fe92c06901f4563af0e36d25223a5ab343782

This new concept will not be back ported to the out-of-tree implementation on GitHub.

Are you able to build you own kernel for $CUSTOMER to probably use this latest implementation?

I had to go back in the mail thread to check your issue and this improvement could probably fix it.

Best,
Oliver



[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