RTEMS | Draft: bsps/riscv: add Smrnmi extension support (!1391)

[Lucian Silistru (@lsilistr)]

Lucian Silistru commented on a discussion on bsps/riscv/riscv/irq/rnmi.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1391#note_158079

 > + */
 > +
 > +#include <bsp/fatal.h>
 > +#include <bsp/irq-generic.h>
 > +#include <bsp/riscv-rnmi.h>
 > +#include <bsp/rnmi.h>
 > +
 > +#include <inttypes.h>
 > +#include <rtems/bspIo.h>
 > +#include <rtems/score/cpu.h>
 > +#include <rtems/score/percpu.h>
 > +#include <rtems/score/riscv-utility.h>
 > +#include <rtems/score/smpimpl.h>
 > +
 > +/* Per-core deferred RNMI contexts */
 > +static RISCV_RNMI_Context _RISCV_RNMI_context[CPU_MAXIMUM_PROCESSORS];

This is I guess also more related to just moving everything specification defined into cpukit rather than bsp. It's one of the things I'm not certain on.

The only reason I put everything in bsps/riscv and below is because the only thing we change related to cpukit is add our own bsps to RTEMS_SMP enabled-by. Makes porting more contained.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1391#note_158079
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-blnsh3qdyd8v0kldiq0x2seas-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/20260826/c95522c3/attachment.htm>