Re: xlinix_can: bug when sending two RTR frames

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

 



Hi,

On 2/9/23 18:53, Oliver Hartkopp wrote:

+ Michael Simek

Missed Michael when checking the responsible people with
scripts/get_maintainer.pl

Best regards,
Oliver

On 2/7/23 21:45, Oliver Hartkopp wrote:
Hi xilinx_can maintainers,

Hartley Sweeten reported a bug when sending RTR frames with the
xilinx_can driver here:

https://github.com/linux-can/can-utils/issues/405#

The problem: When sending a single RTR frame (e.g. with 'cansend can0
001#R') nothing happens.

Only after sending a *second* RTR frame with 'cansend can0 001#R' the
two (pending) RTR-frames are sent directly after each other.

This faulty behavior of RTR frame sending is independent of the time gap
between the two cansend attempts.

I read that thread and I am missing details about Zynq board.
Are you using any custom zynq board or any xilinx standard evaluation board?

Can you please c&p dt fragment you use?

You are using 5.4 kernel which is quite old. Can you please switch to the latest upstream or 5.15 xilinx?

Thanks,
Michal





[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