Lines Matching +full:register +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
152 .Bd -literal
194 .Bl -tag -width XXXX
202 sub-structure.
217 sub-structure.
220 sub-structure on return.
235 sub-structure.
241 sub-structure is filled on return with details of the allocation.
254 Allocated memory is automatically loaded and thus mapped into bus space.
271 driver is not in a position to track whether the memory has been mapped in
286 sub-structure.
307 sub-structure contains the result of the operation.
329 A sub-section of the memory can be targeted by specifying the relative
337 sub-structure.
363 .Bl -tag -width XXXXXX -compact -offset indent
381 For each valid base address register (BAR), a device special file is created
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