userspace: remove APPLICATION_MEMORY feature
This was never a long-term solution, more of a gross hack to get test cases working until we could figure out a good end-to-end solution for memory domains that generated appropriate linker sections. Now that we have this with the app shared memory feature, and have converted all tests to remove it, delete this feature. To date all userspace APIs have been tagged as 'experimental' which sidesteps deprecation policies. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
This commit is contained in:
parent
525065dd8b
commit
41f6011c36
52 changed files with 152 additions and 701 deletions
|
@ -20,11 +20,6 @@
|
|||
MMU_BOOT_REGION((u32_t)&_image_rom_start, (u32_t)&_image_rom_size,
|
||||
MMU_ENTRY_READ | MMU_ENTRY_USER);
|
||||
|
||||
#ifdef CONFIG_APPLICATION_MEMORY
|
||||
/* User threads by default can read/write app-level memory. */
|
||||
MMU_BOOT_REGION((u32_t)&__app_ram_start, (u32_t)&__app_ram_size,
|
||||
MMU_ENTRY_WRITE | MMU_ENTRY_USER | MMU_ENTRY_EXECUTE_DISABLE);
|
||||
#endif
|
||||
#ifdef CONFIG_APP_SHARED_MEM
|
||||
MMU_BOOT_REGION((u32_t)&_app_smem_start, (u32_t)&_app_smem_size,
|
||||
MMU_ENTRY_WRITE | MMU_ENTRY_USER | MMU_ENTRY_EXECUTE_DISABLE);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue