Lines Matching +full:ahci +full:- +full:compatible
37 of physical hardware, there are also pseudo-device drivers which are device
43 are both pseudo-device drivers.
47 .Bd -literal
48 +--------------------+
52 +--------------------+
53 | +--------------+ +------------+
55 +------------------------->| Cryptography | ... | Scheduling | ...
57 | +--------------+ +------------+
58 | +----------------+ +--------------+ +--------------+
60 +-->| Device Drivers | ... | File Systems | ... | System Calls | ...
62 +----------------+ +--------------+ +--------------+
64 +-----------+
66 | +------------+ +---------+ +-----------+ +-----------+
67 +-->| Networking |->| igb(4D) | ... | mlxcx(4D) | ... | cxgbe(4D) | ...
68 | +------------+ +---------+ +-----------+ +-----------+
70 | +-------+ +----------+ +-------------+ +----------+
71 +-->| HBA |------>| smrt(4D) | ... | mpt_sas(4D) | ... | ahci(4D) | ...
72 | +-------+ +----------+ +-------------+ +----------+
74 | +-------+ +--------------+ +----------+ +---------+
75 +-->| USB |------>| scsa2usb(4D) | ... | ccid(4D) | ... | hid(4D) | ...
76 | +-------+ +--------------+ +----------+ +---------+
78 | +---------+ +-------------+ +-------------+
79 +-->| Sensors |---->| smntemp(4D) | ... | pchtemp(4D) | ...
80 | +---------+ +-------------+ +-------------+
82 +-------+-------------+-----------+----------+
84 v +-----------+ +-----+ v
85 +-------+ | Character | | USB | +-------+
87 +-------+ | Devices | +-----+ +-------+
88 +-----------+
166 .Bd -literal
214 is the USB host controller, which itself may be under a PCI-PCI bridge, and this
223 built-in mechanisms and through operations on other nexus drivers.
231 .Dq compatible
233 For example, PCI and PCIe drivers automatically set up the compatible property
265 .Bd -literal
328 The actions taken here are generally device-specific, while certain classes of
336 There is generally a per-instance data structure that a driver creates.
362 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
379 For pseudo-device drivers or drivers which do not perform I/O, they can use the
387 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
398 .Bd -literal
466 entry point for supporting memory-mapping.
470 structure and there was one per-instance, character and block operations work
496 For example, many pseudo-device drivers like DTrace will use this so each client
512 .Bl -tag -width Ds
550 non-blocking request.
553 to create some kind of file-like abstraction for a device.
618 .Bl -tag -width Ds
630 HBA or blkdev-based drivers do not usually end up implementing this interface.
648 .Bd -literal
713 They may interface to the host via PCIe, USB, be a pseudo-device, or use
730 networking-specific entry points that take care of things like getting and
752 but it then pushes on additional modules like the pseudo-terminal emulation
777 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
800 .Xr mt-streams 9F
817 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
830 This has the unique effect of causing the driver's top-level
847 .Bl -enum
889 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
912 which allows for multiple, typed name-value pairs to be part of the stat.
925 .Bl -column -offset -indent "mac_capab_transceiver" "mac_capab_transceiver"
966 .Bl -column -offset -indent "ddi_ufm_op_fill_image(9E)" "ddi_ufm_op_fill_image(9E)"
1021 .Pq the primary exception being for some hand-written assembler .
1037 .Pq Sq - .
1041 .Sq hello-world
1043 .Ql sdt:::hello-world .
1046 from 0-8.
1053 .Ql sdt:::igc-context-desc :
1054 .Bd -literal -offset indent