Lines Matching +full:memory +full:- +full:mapped

38 .Bd -ragged -offset indent
45 .Bd -literal -offset indent
51 .Bd -ragged -offset indent
62 Programs can open these device special files and perform register-level
72 Especially hardware diagnostics requires a somewhat user-friendly interface
111 .Bd -literal
117 .Ss Memory mapped I/O resources
118 The device special files created for memory mapped I/O resources behave
120 Additionally, device special files for memory mapped I/O resources allow
121 the memory to be mapped into the process' address space using
123 Reads and writes to the memory address returned by
133 Also, make sure the compiler does not optimize memory accesses away or has
152 .Bd -literal
192 An object is either a tag or a memory descriptor (md).
194 .Bl -tag -width XXXX
202 sub-structure.
217 sub-structure.
220 sub-structure on return.
227 This means that derived tags that have this tag as a parent and memory
230 Allocate memory that satisfies the constraints put forth by the tag
235 sub-structure.
236 The key of the memory descriptor for this memory is returned in the
241 sub-structure is filled on return with details of the allocation.
242 The kernel virtual address and the size of the allocated memory are returned
248 The number of contiguous physical memory segments and the address of the first
254 Allocated memory is automatically loaded and thus mapped into bus space.
263 is implemented, which means that memory is currently always allocated as a
264 single contiguous region of physical memory.
268 Free previously allocated memory and destroy the memory descriptor.
271 driver is not in a position to track whether the memory has been mapped in
273 the memory before it is freed.
277 the memory, even after it has been freed.
278 When the memory is reused for other purposes it can be corrupted or cause
282 Create an empty memory descriptor with the tag specified in the
286 sub-structure.
287 The key of the memory descriptor is returned in the
291 Destroy the previously created memory descriptor specified by the
294 When the memory descriptor is still loaded, it is unloaded first.
296 Load a contiguous region of memory in the memory descriptor specified by the
307 sub-structure contains the result of the operation.
321 Unload the memory descriptor specified by the
325 Guarantee that all hardware components have a coherent view of the memory
326 tracked by the memory descriptor, specified by the
329 A sub-section of the memory can be targeted by specifying the relative
330 offset and size of the memory to make coherent.
337 sub-structure.
363 .Bl -tag -width XXXXXX -compact -offset indent
387 representing I/O port or memory mapped I/O space (resp.)
391 first I/O port address or first memory mapped I/O address.
398 For each I/O port or memory mapped I/O address, a device special file is
405 representing I/O port or memory mapped I/O space (resp.)
412 If the ISA device is not a Plug-and-Play device nor present in the ACPI
418 single memory mapped I/O region will have the following device special files:
420 .Bl -tag -width XXXXXX -compact -offset indent
427 .Bl -tag -width XXXXXX -compact -offset indent
457 driver does not fully support memory descriptors that need multiple
458 physical memory segments or multiple bus space segments.