/freebsd/lib/libdevctl/ |
H A D | devctl.3 | 139 If the device is currently attached to a device driver, 159 but any device driver currently attached to the device will remain attached. 170 If the device is already attached and 174 If the device is already attached and 178 attached to the new device driver. 182 function resets a device so that it can be attached to any valid device 186 If the device is already attached and 190 If the device is already attached and 195 it is reprobed and attached to a suitable device driver if one is found. 230 the reset, and re-attached afterwards. [all …]
|
/freebsd/share/man/man9/ |
H A D | device.9 | 38 The device object represents a piece of hardware attached to the 40 into, disk drives attached to the expansion card etc. 46 the system (ISA, PCI etc.) will be attached directly to 55 In addition, any device can have children attached to it (see 63 A device which has been successfully probed and attached to the 88 the device probe succeeded but not yet attached 90 the device has been successfully attached
|
H A D | bpf.9 | 87 attached to an interface. 121 instances to be attached to a single interface, 128 on the interface for any data link-layer types attached. 142 instance attached. 258 Last argument indicates listener is attached (1) or detached (0).
|
H A D | swi.9 | 53 Software interrupt handlers are attached to a software interrupt thread, just 54 as hardware interrupt handlers are attached to a hardware interrupt thread. 55 Multiple handlers can be attached to the same thread. 74 interrupt handlers, then this handler will be attached to that event. 85 handler is attached to.
|
/freebsd/contrib/opencsd/decoder/include/common/ |
H A D | comp_attach_pt_t.h | 85 …// detach current first if anything attached, connect supplied pointer, remain unattached if point… 94 * Return the current (first) attached interface pointer. 95 * Will return 0 if nothing attached or the attachment point is disabled. 102 * Return the next attached interface. 110 * Returns the number of interface pointers attached to this attachment point. 112 * @return int : number of component interfaces attached. 118 * a component is attached or detached. 146 bool m_hasAttached; /**< Flag indicating at least one attached interface */ 148 T *m_comp; /**< pointer to the single attached interface */
|
/freebsd/sys/dev/bhnd/bhndb/ |
H A D | bhndb_bus_if.m | 30 # Parent bus interface required by attached bhndb bridge devices. 78 * the bhndb bridge device to enumerate attached devices. 81 * @param child The attached bhndb device. 97 * @param child The attached bhndb device. 109 * @param child The attached bhndb device. 121 * @param child The attached bhndb device. 137 * @param child The attached bhndb device.
|
/freebsd/usr.sbin/devctl/ |
H A D | devctl.8 | 102 it is attached to the device. 117 If the device is currently attached to a device driver, 140 If the device is already attached to a device driver and the 144 attached to the new device driver. 145 If the device is already attached to a device driver and the 160 If the device is currently attached to a device driver and the 218 do a reset, the child device will end up attached.
|
/freebsd/share/man/man4/ |
H A D | geom.4 | 176 A consumer can be attached to zero or one providers. 178 A provider can have zero or more consumers attached. 187 A geom with no attached consumers has rank=1. 189 A geom with attached consumers has a rank one higher than the 191 attached to. 242 consumers attached to the provider will receive notification about 254 immediate change in the topology: any attached consumers are still 255 attached, any opened paths are still open, any outstanding I/O 266 Providers which are not attached to will typically self-destruct 327 all attached consumer [all...] |
H A D | hwpmc.4 | 92 to a process it is attached to is scheduled on a CPU. 119 These PMCs count hardware events whenever a thread in their attached process is 131 The PMCs only count events when a thread belonging to their attached 178 Process-private PMCs need to be attached to a target process before 183 An already attached PMC may be detached from its target process 189 operation on an as yet unattached PMC will cause it to be attached 238 will maintain per-process counts for each target process attached to 266 attached target processes. 360 attached to all current and future descendants of the target process. 394 modifier flag, and should be attached only to its owner process at the [all …]
|
H A D | kbdmux.4 | 24 acts as a master keyboard consuming input from all slave keyboards attached to 27 Slave keyboards can be attached to or detached from the 51 Thus all slave keyboards attached to the
|
H A D | devctl.4 | 99 + Device node in tree attached. 112 .It Ar dev Ta "The device name that was attached/detached." 113 .It Ar parent Ta "The device name of the parent bus that attached the device." 120 attached message.
|
/freebsd/usr.sbin/sesutil/ |
H A D | sesutil.8 | 82 to indicate all disks attached to SES controllers. 87 must be the element ID of a valid item attached to the controller. 90 command to list the elements attached to a controller. 99 to indicate all disks attached to SES controllers. 104 must be the element ID of a valid item attached to the controller. 107 command to list the elements attached to a controller.
|
/freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
H A D | DiagnosticCommentKinds.td | 75 "'%select{\\|@}0param' command used in a comment that is not attached to " 81 "command should be used in a comment attached to " 88 "command should not be used in a comment attached to a " 95 "command should not be used in a comment attached to a non-container declaration">, 115 "'%select{\\|@}0tparam' command used in a comment that is not attached to " 136 "'%select{\\|@}0%1' command used in a comment that is not attached to " 141 "'%select{\\|@}0%1' command used in a comment that is attached to a "
|
/freebsd/lib/libsys/ |
H A D | shmat.2 | 51 is attached is determined as follows: 60 is 0, the segment is attached at an address selected by the 69 the segment is attached the specified address. 87 cleared before the segment is attached. 106 returns the address where the segment is attached; otherwise, -1
|
/freebsd/lib/libpmc/pmu-events/arch/x86/cascadelakex/ |
H A D | uncore-other.json | 776 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 788 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… 800 …rd slot of a PCIe riser card, but it could refer to any x4 or x8 device attached to the IIO unit a… 812 …he fourth slot of a PCIe riser card, but it could brefer to any device attached to the IIO unit u… 824 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 836 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… 848 …rd slot of a PCIe riser card, but it could refer to any x4 or x8 device attached to the IIO unit a… 860 …the fourth slot of a PCIe riser card, but it could brefer to any device attached to the IIO unit u… 872 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 884 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… [all …]
|
/freebsd/lib/libpmc/pmu-events/arch/x86/skylakex/ |
H A D | uncore-other.json | 755 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 767 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… 779 …rd slot of a PCIe riser card, but it could refer to any x4 or x8 device attached to the IIO unit a… 791 …he fourth slot of a PCIe riser card, but it could brefer to any device attached to the IIO unit u… 803 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 815 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… 827 …rd slot of a PCIe riser card, but it could refer to any x4 or x8 device attached to the IIO unit a… 839 …the fourth slot of a PCIe riser card, but it could brefer to any device attached to the IIO unit u… 851 … device plugged into the first slot of a PCIe riser card or to a device attached to the IIO unit w… 863 …e second slot of a PCIe riser card, but it could refer to any x4 device attached to the IIO unit u… [all …]
|
/freebsd/lib/libpmc/pmu-events/arch/x86/sapphirerapids/ |
H A D | other.json | 44 … fetches and L1 instruction cache prefetches that were supplied by DRAM attached to this socket, u… 88 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to this socket, … 99 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to another socke… 110 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to another socket… 154 …efetches for exclusive ownership (PREFETCHW) that were supplied by DRAM attached to this socket, u… 231 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, u… 242 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, w… 253 … and prefetches to the core caches (L1 or L2) that were supplied by PMM attached to this socket, w… 275 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to another socket… 286 …fetches to the core caches (L1 or L2) that were supplied by DRAM or PMM attached to another socket… [all …]
|
/freebsd/sys/dev/ocs_fc/ |
H A D | ocs_device.c | 180 if (node->attached) { in __ocs_d_initiate_shutdown() 182 * or sometime later, will check node->attached later in in __ocs_d_initiate_shutdown() 277 * State waits for a domain-attached completion while in loop topology. 771 /* only send if we have initiator capability, and domain is attached */ in __ocs_d_init() 772 if (node->sport->enable_ini && node->sport->domain->attached) { in __ocs_d_init() 777 node_printf(node, "not sending plogi sport.ini=%d, domain attached=%d\n", in __ocs_d_init() 778 node->sport->enable_ini, node->sport->domain->attached); in __ocs_d_init() 790 /* domain already attached */ in __ocs_d_init() 791 if (node->sport->domain->attached) { in __ocs_d_init() 800 /* domain not attached; several possibilities: */ in __ocs_d_init() [all …]
|
/freebsd/lib/libpmc/pmu-events/arch/x86/icelakex/ |
H A D | other.json | 145 … fetches and L1 instruction cache prefetches that were supplied by DRAM attached to this socket, u… 189 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to this socket, … 200 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to this socket, u… 222 …"BriefDescription": "Counts demand data reads that were supplied by DRAM attached to another socke… 233 …"BriefDescription": "Counts demand data reads that were supplied by PMM attached to another socket… 288 …efetches for exclusive ownership (PREFETCHW) that were supplied by DRAM attached to this socket, u… 299 …refetches for exclusive ownership (PREFETCHW) that were supplied by PMM attached to this socket, u… 321 …refetches for exclusive ownership (PREFETCHW) that were supplied by PMM attached to another socket… 365 …s and software prefetches (except PREFETCHW) that were supplied by DRAM attached to this socket, u… 453 …and prefetches to the core caches (L1 or L2) that were supplied by DRAM attached to this socket, u… [all …]
|
/freebsd/sys/dev/isci/scil/ |
H A D | scu_bios_definitions.h | 220 * This field specifies the maximum number of direct attached 316 * used if a SATA 1.5Gbs or SATA 3.0Gbs device is direct-attached. 323 * be used if a SATA 6.0Gbs device is direct-attached. 330 * be used if a SAS 1.5Gbs or SAS 3.0Gbs device is direct-attached. 337 * be used if a SAS 6.0Gbs device is direct-attached. 384 * This field specifies the maximum number of direct attached 513 * used if a SATA 1.5Gbs or SATA 3.0Gbs device is direct-attached. 520 * be used if a SATA 6.0Gbs device is direct-attached. 527 * be used if a SAS 1.5Gbs or SAS 3.0Gbs device is direct-attached. 534 * be used if a SAS 6.0Gbs device is direct-attached. [all …]
|
/freebsd/contrib/llvm-project/llvm/lib/Target/SPIRV/ |
H A D | SPIRVMetadata.cpp | 22 "Kernel attributes are attached/belong only to OpenCL kernel functions"); in getOCLKernelArgAttribute() 24 // Lookup the argument attribute in metadata attached to the kernel function. in getOCLKernelArgAttribute() 29 // Sometimes metadata containing kernel attributes is not attached to the in getOCLKernelArgAttribute() 74 "Kernel attributes are attached/belong only to OpenCL kernel functions"); in getOCLKernelArgAccessQual() 81 "Kernel attributes are attached/belong only to OpenCL kernel functions"); in getOCLKernelArgTypeQual()
|
/freebsd/sys/dev/ata/ |
H A D | ata-isa.c | 105 if (ch->attached) in ata_isa_attach() 107 ch->attached = 1; in ata_isa_attach() 152 if (!ch->attached) in ata_isa_detach() 154 ch->attached = 0; in ata_isa_detach() 170 if (!ch->attached) in ata_isa_suspend() 181 if (!ch->attached) in ata_isa_resume()
|
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/vdev_zaps/ |
H A D | vdev_zaps_004_pos.ksh | 26 # 4. Verify that the newly-attached disk has a leaf ZAP. 73 # Ensure attached disk got a leaf-level ZAP but not a top-level ZAP. 76 [[ -n "$dsk2_top" ]] && log_fail "Attached disk $disk2 has top ZAP." 77 [[ -z "$dsk2_leaf" ]] && log_fail "Attached disk $disk2 has no leaf ZAP."
|
/freebsd/lib/geom/eli/ |
H A D | geli.8 | 408 Multiple providers can only be attached with a single 570 The User Key can be changed at any time: for an attached provider, 572 When a provider is attached, the user does not have to provide 597 If the provider is attached and no key number is given, the key 615 If one is destroying keys for an attached provider, the provider 632 If the provider is attached and no key number is given, the key 640 detach it forcibly (if it is attached). 643 In case the provider was attached with the 650 If specified, all currently attached providers will be killed. 661 partition or slice is attached [all...] |
/freebsd/tests/sys/geom/class/eli/ |
H A D | delkey_test.sh | 27 # Remove key 0 for attached provider. 38 # We cannot remove last key without -f option (for attached provider). 42 # Remove last key for attached provider. 45 # If there are no valid keys, but provider is attached, we can save situation.
|