RTEMS | CAN updates, sja1000 prepare for Kvaser PCI and ESP32C3 and Tx same prio round-robin fix (!1364)

[Pavel Pisa (@ppisa)]

Pavel Pisa created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1364

Project:Branches: ppisa/rtems:can-updates to rtems/rtos/rtems:main
Author:   Pavel Pisa



## Summary

bsps/shared/dev/can/sja1000: reenable I/O mapped support for i386 target

   The I/O mapped SJA1000 is required to support Kvaser CanS/D/Q boards
   which have emulation in mainline QEMU.

   The I/O space mapping is enabled by RTEMS_CAN_SJA1000_ARCH_WITH_IO_PORTS
   option set in hw_options during initialization.

bsps/shared/dev/can/sja1000: option to enforce 32-bit access

    On the ESP32C3, when registers are access by 8-bits
    then writes to (at least some) registers are ignored.

cpukit/dev/can: correct round-robin on same priority Tx

    When the device is open multiple times and data
    are sent to driver by multiple FIFOs/edges then
    round-robin between same priority prevents
    one application blocking whole bandwidth.

    The problem has been introduced during switch
    from original uLUt/LinCAN to NewLib provided TAILQ

As the change is only small correction and the re-enablement
of I/O access which has been disabled due unavailability
of i386_io.h after initial submission of the SJA1000 driver
the cpukit, I think that changes could be accepted
into prepared 7.x release.

## Generative AI

A brain and hands have been used only.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1364
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-4776lbqwn9sr56mdwybr9o46f-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260722/ed493ee3/attachment-0001.htm>