RTEMS | Fix SJA1000 driver to use proper PCI/PCIe I/O access routines (i.e. inb, outb, ioread8, iowrite8) (#5563)

[Chris Johns (@chris)]

Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5563#note_149354


Code under `cpukit/dev` provides wider access. The `bsp/shared/dev` implies the BSP hardware has the device or access to the device so the BSP has to include the code to build it. The `cpukit` option means everyone always gets the support.

If you think this driver can be used on target hardware you do not know about then the model used by SPI and I2C under `cpukit/dev`of indirect pointers to read and write calls may be better. A user can make use of the code on target hardware RTEMS does not have access too.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5563#note_149354
You're receiving this email because of your account on gitlab.rtems.org.


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