More separation of kernel- and user-memory management
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3468 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
parent
e08b22d33c
commit
2e9ca12bcc
@ -96,8 +96,8 @@ $(BOARD_INCLUDE)/user_map.h: $(TOPDIR)/User.map
|
||||
@echo "" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_MMINIT 0x`grep \" mm_initialize$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_MMADDREGION 0x`grep \" mm_addregion$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_TRYSEM 0x`grep \" mm_trysemaphore$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_GIVSEM 0x`grep \" mm_givesemaphore$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_MMTRYSEM 0x`grep \" mm_trysemaphore$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_MMGIVESEM 0x`grep \" mm_givesemaphore$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_MALLOC 0x`grep \" malloc$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
@echo "#define CONFIG_USER_REALLOC 0x`grep \" realloc$\" $(TOPDIR)/User.map | cut -d' ' -f1`" >> $(BOARD_INCLUDE)/user_map.h
|
||||
|
@ -62,13 +62,14 @@ MEMORY
|
||||
sram2 (rwx) : ORIGIN = 0x20080000, LENGTH = 16K
|
||||
}
|
||||
|
||||
# Force user_start into the link. This is the application entry point
|
||||
/* Force user_start into the link. This is the application entry point */
|
||||
|
||||
EXTERN(user_start)
|
||||
|
||||
# Make sure that the critical memory management functions are in user-space.
|
||||
# Currently, the plan is that the memory manager will reside in user-space
|
||||
# but be usable both by kernel- and user-space code
|
||||
/* Make sure that the critical memory management functions are in user-space.
|
||||
* Currently, the plan is that the memory manager will reside in user-space
|
||||
* but be usable both by kernel- and user-space code
|
||||
*/
|
||||
|
||||
EXTERN(mm_initialize)
|
||||
EXTERN(mm_addregion)
|
||||
|
Loading…
Reference in New Issue
Block a user