Lines Matching +full:on +full:- +full:device
21 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
38 .Bd -ragged -offset indent
39 .Cd "device proto"
45 .Bd -literal -offset indent
49 To have the driver attach to a device instead of its regular driver,
51 .Bd -ragged -offset indent
58 device driver attaches to PCI or ISA devices when no other device drivers
59 are present for those devices and it creates device special files for all
60 resources associated with the device.
61 The driver itself has no knowledge of the device it attaches to.
62 Programs can open these device special files and perform register-level
66 device driver is nothing but a conduit or gateway between user space
67 programs and the hardware device.
72 Especially hardware diagnostics requires a somewhat user-friendly interface
76 Device special files created for I/O port resources allow
82 operations to be performed on them.
87 system calls are used to perform input and output (resp.) on the port.
98 region being represented by the device special file.
99 If, for example, the device special file corresponds to an I/O port region
101 whence value of SEEK_SET will target port 0x3fc on the next read or write
109 device special file.
111 .Bd -literal
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
131 Alignment and access width constraints put forth by the underlying device
136 A device special file named
144 This device special file does not support
152 .Bd -literal
194 .Bl -tag -width XXXX
199 field is set on output with the key of the DMA tag.
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.
261 The behaviour of this operation banks heavily on how
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.
348 device special file.
349 The device special file supports
356 All device special files corresponding to a PCI device are located under
360 representing the location of the PCI device in the PCI hierarchy.
363 .Bl -tag -width XXXXXX -compact -offset indent
369 The PCI slot or device number
374 Every PCI device has a device special file called
376 This device special file gives access to the PCI configuration space.
377 A device special file called
380 This device special file provides the interfaces needed for doing DMA.
381 For each valid base address register (BAR), a device special file is created
392 Consequently, all device special files corresponding to an ISA device are
398 For each I/O port or memory mapped I/O address, a device special file is
406 When the device has a DMA channel assigned to it, a device special file
410 This device special file provides the interfaces needed for doing DMA.
412 If the ISA device is not a Plug-and-Play device nor present in the ACPI
413 device tree, it must have the appropriate hints so that the kernel can
417 A single function PCI device in domain 0, on bus 1, in slot 2 and having a
418 single memory mapped I/O region will have the following device special files:
420 .Bl -tag -width XXXXXX -compact -offset indent
425 A legacy floppy controller will have the following device files:
427 .Bl -tag -width XXXXXX -compact -offset indent
446 device driver and this manual page were written by
452 It is not advisable to use this driver on a production machine.
459 At the very least, an operation is needed on the DMA pseudo resource