Lines Matching full:mapping

8 devmap_devmem_setup, devmap_umem_setup \- set driver memory mapping parameters
40 An opaque mapping handle that the system uses to describe the mapping.
60 mapping. The framework will copy the structure to the system private memory.
87 Length (in bytes) of the mapping to be mapped.
96 Maximum protection flag possible for attempted mapping. Some combinations of
131 User-level access is allowed. The mapping is done as a result of a
215 An opaque data structure that the system uses to describe the mapping.
235 mapping.
262 Length (in bytes) of the mapping to be mapped.
271 Maximum protection flag possible for attempted mapping. Some combinations of
306 User-level access is allowed (the mapping is being done as a result of a
342 used in the \fBdevmap\fR(9E) entry point to pass mapping parameters from the
346 The \fIdhp\fR argument specifies a device mapping handle that the system uses
347 to store all mapping parameters of a physical contiguous memory. The system
357 \fBMapping Setup\fR
360 User has called \fBmmap\fR(2) to create a mapping to the device memory.
369 User has accessed an address in the mapping that has no translations.
378 User has duplicated the mapping. Mappings are duplicated when the process calls
388 User has called \fBmunmap\fR(2) on the mapping or is exiting, \fBexit\fR(2).
398 manage events on a device mapping. For example, the \fBdevmap_access\fR(9E)
400 mappings of other processes and to load the mapping of the calling process.
405 The maximum protection allowed for the mapping is specified in \fImaxprot\fR.
432 cache incoherence if the mapping is not \fBMAP_FIXED.\fR