pussuw commented on code in PR #12041:
URL: https://github.com/apache/nuttx/pull/12041#discussion_r1549668874
##########
arch/Kconfig:
##########
@@ -801,6 +801,28 @@ config ARCH_KMAP_NPAGES
maximum number of pages per region, and the configured size of
each page.
+config ARCH_UDEV_MAPPING
+ bool "Support mapping devices memory into user space"
Review Comment:
That is a detail of shmfs, you can map any memory to user virtual memory
with up_shmat()
The intent of the shared memory area was to hold any dynamic mappings for
the user, like shared memory objects, ad-hoc mappings, shared libraries and so
forth. User devices can go there as well, just remember to reserve the space
from the shared memory pool i.e. calling vm_alloc_region().
Why is it called "shared memory area" ? That is the name we came up with,
there is no really good / descriptive name for it IMO.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
