Hi Sebastian !
You have suggested me following i2c drivers which follows /dev/i2c framwork :
https://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/atsam/i2c/atsam_i2c_bus.c
https://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/xilinx-zynq/i2c/cadence-i2c.c
Can you please provide link to the
Hello Gedare and Sebastian,
as the clock_nanosleep is in the place now, I am trying to
analyze consequences and I have some questions.
The first one, why is _Nanosleep_Pseudo_queue required
there. nanosleep is critical function for realtime and
it is quite possible that many threads on more CPUs
It makes sense to me. Chris identified some mmap capabilities that could be
implemented on normal Barr metal RTEMS but when paravirtualized, we can use
kernel or hypervisor services to support the actual dirty work. But our
code still needs to properly track mmaps and shm_open regions so the unmap
