Re: xlinix_can: bug when sending two RTR frames

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

 



On 07.02.2023 21:45:20, 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.

More info:

| Also, this is with a kernel/rootfs created using Petalinux 2020.2.
| Linux s6 5.4.0-xilinx-v2020.2 #1 SMP PREEMPT Fri Feb 3 17:27:45 UTC 2023 armv7l GNU/Linux

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

Attachment: signature.asc
Description: PGP signature


[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