This seems OK. I would like to see progress toward somewhat uniform handling of different kinds of hw: MPU, MMU, nothing. I guess this doesn't really add an API for the user to define the region? Just some capability to hack it in?
On Thu, May 24, 2018 at 4:32 AM, Christian Mauderer <christian.maude...@embedded-brains.de> wrote: > This allows a user to overwrite some MPU settings. That can for example > be usefull for devices with special requirements that are connected to > the external bus interface. > --- > bsps/arm/atsam/include/libchip/include/mpu.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/bsps/arm/atsam/include/libchip/include/mpu.h > b/bsps/arm/atsam/include/libchip/include/mpu.h > index 06f70d5d62..a5d00a681b 100644 > --- a/bsps/arm/atsam/include/libchip/include/mpu.h > +++ b/bsps/arm/atsam/include/libchip/include/mpu.h > @@ -55,6 +55,10 @@ > #define MPU_NOCACHE_SRAM_REGION (11) > #endif > #define MPU_SYSTEM_REGION (12) > +#ifdef __rtems__ > +/* Reserve the region with highest priority for user applications */ > +#define MPU_USER_DEFINED_REGION (15) > +#endif /* __rtems__ */ > > #define MPU_REGION_VALID (0x10) > #define MPU_REGION_ENABLE (0x01) > -- > 2.13.6 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
