| /freebsd/contrib/wpa/wpa_supplicant/ |
| H A D | driver_i.h | 2 * wpa_supplicant - Internal driver interface wrappers
12 #include "drivers/driver.h"
18 if (wpa_s->driver->init2) in wpa_drv_init()
19 return wpa_s->driver->init2(wpa_s, ifname, in wpa_drv_init()
21 if (wpa_s->driver->init) { in wpa_drv_init()
22 return wpa_s->driver->init(wpa_s, ifname); in wpa_drv_init()
29 if (wpa_s->driver->deinit) in wpa_drv_deinit()
30 wpa_s->driver->deinit(wpa_s->drv_priv); in wpa_drv_deinit()
36 if (wpa_s->driver->set_param) in wpa_drv_set_param()
37 return wpa_s->driver->set_param(wpa_s->drv_priv, param); in wpa_drv_set_param()
[all …]
|
| /freebsd/contrib/wpa/src/ap/ |
| H A D | ap_drv_ops.h | 2 * hostapd - Driver operations
122 if (!hapd->driver || !hapd->driver->send_action_cancel_wait || in hostapd_drv_send_action_cancel_wait()
125 hapd->driver->send_action_cancel_wait(hapd->drv_priv); in hostapd_drv_send_action_cancel_wait()
153 #include "drivers/driver.h"
173 if (hapd->driver == NULL || in hostapd_drv_set_countermeasures()
174 hapd->driver->hapd_set_countermeasures == NULL) in hostapd_drv_set_countermeasures()
176 return hapd->driver->hapd_set_countermeasures(hapd->drv_priv, enabled); in hostapd_drv_set_countermeasures()
184 if (hapd->driver == NULL || hapd->driver->set_sta_vlan == NULL) in hostapd_drv_set_sta_vlan()
186 return hapd->driver->set_sta_vlan(hapd->drv_priv, addr, ifname, in hostapd_drv_set_sta_vlan()
193 if (hapd->driver == NULL || hapd->driver->get_inact_sec == NULL) in hostapd_drv_get_inact_sec()
[all …]
|
| H A D | ap_drv_ops.c | 2 * hostapd - Driver operations
243 if (hapd->driver == NULL || hapd->driver->set_ap_wps_ie == NULL) in hostapd_reset_ap_wps_ie()
246 return hapd->driver->set_ap_wps_ie(hapd->drv_priv, NULL, NULL, NULL); in hostapd_reset_ap_wps_ie()
255 if (hapd->driver == NULL || hapd->driver->set_ap_wps_ie == NULL) in hostapd_set_ap_wps_ie()
262 ret = hapd->driver->set_ap_wps_ie(hapd->drv_priv, beacon, proberesp, in hostapd_set_ap_wps_ie()
290 * MLD peers). Thus, do not propagate the change to the driver for the in hostapd_set_authorized()
326 * driver for the link stations. in hostapd_set_sta_flags()
389 if (hapd->driver == NULL || hapd->driver->set_wds_sta == NULL) in hostapd_set_wds_sta()
395 return hapd->driver->set_wds_sta(hapd->drv_priv, addr, aid, val, in hostapd_set_wds_sta()
403 if (hapd->driver == NULL || hapd->driver->add_sta_node == NULL) in hostapd_add_sta_node()
[all …]
|
| H A D | wpa_auth_kay.c | 29 if (!hapd->driver->macsec_init) in hapd_macsec_init()
31 return hapd->driver->macsec_init(hapd->drv_priv, params); in hapd_macsec_init()
39 if (!hapd->driver->macsec_deinit) in hapd_macsec_deinit()
41 return hapd->driver->macsec_deinit(hapd->drv_priv); in hapd_macsec_deinit()
49 if (!hapd->driver->macsec_get_capability) in hapd_macsec_get_capability()
51 return hapd->driver->macsec_get_capability(hapd->drv_priv, cap); in hapd_macsec_get_capability()
59 if (!hapd->driver->enable_protect_frames) in hapd_enable_protect_frames()
61 return hapd->driver->enable_protect_frames(hapd->drv_priv, enabled); in hapd_enable_protect_frames()
69 if (!hapd->driver->enable_encrypt) in hapd_enable_encrypt()
71 return hapd->driver->enable_encrypt(hapd->drv_priv, enabled); in hapd_enable_encrypt()
[all …]
|
| /freebsd/sys/kern/ |
| H A D | device_if.m | 77 * @brief Probe to see if a device matches a driver.
80 * is called via device_probe_and_attach() to select a driver
82 * the winning driver (if any) to the device.
85 * Typically, the driver will examine the device to see if
86 * it is suitable for this driver. This might include checking
90 * In some cases, there may be more than one driver available
92 * be a generic driver which works for a set of many types of
93 * device and a more specific driver which works for a subset
94 * of devices). Because of this, a driver should not assume
95 * that it will be the driver that attaches to the device even
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | bce.4 | 30 .Nd "QLogic NetXtreme II (BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapter driver"
32 To compile this driver into the kernel,
40 Alternatively, to load the driver as a
49 driver supports QLogic's NetXtreme II product family, including the
59 driver under
79 driver supports the following media types:
125 driver supports the following media options:
138 driver provides support for various NICs based on the QLogic NetXtreme II
209 Set the number of memory pages assigned to receive packets by the driver.
214 by the driver.
[all …]
|
| H A D | sym.4 | 2 .\" Device driver optimized for the Symbios/LSI 53C896/53C895A/53C1010
7 .\" This driver also supports the following Symbios/LSI PCI SCSI chips:
12 .\" This driver for FreeBSD-CAM is derived from the Linux sym53c8xx driver.
15 .\" The sym53c8xx driver is derived from the ncr53c8xx driver that had been
16 .\" a port of the FreeBSD ncr driver to Linux-1.2.13.
18 .\" The original ncr driver has been written for 386bsd and FreeBSD by
24 .\" FreeBSD-CAM services is based on the aic7xxx driver for FreeBSD-CAM
62 .Nd NCR/Symbios/LSI Logic 53C8XX PCI SCSI host adapter driver
64 To compile this driver into the kernel,
76 To control driver probing against HVD buses:
[all …]
|
| H A D | mrsas.4 | 43 .Nd Broadcom/LSI MegaRAID 6/12Gb/s SAS+SATA RAID controller driver
62 driver will detect Broadcom/LSI's 6Gb/s and 12Gb/s
68 driver will be visible to the user through
80 substantially different than the old "MegaRAID" Driver
84 layer and thus requires a new driver which attaches targets to the
102 driver's behavior for LSI MegaRAID SAS 2208/2308/3008/3108 controllers.
105 driver will detect these controllers.
108 section to know more about driver priority for MR-Fusion devices.
128 driver supports the following LSI/Broadcom SATA/SAS RAID controllers:
158 driver instance, set the
[all …]
|
| H A D | iwx.4 | 25 .Nd Intel WiFi 6 IEEE 802.11ax wireless network driver
27 To compile this driver into the kernel,
35 Alternatively, to load the driver as a
44 driver supports the Intel Wi-Fi 6 series of M.2
50 the driver will be automatically loaded with
54 driver can be configured at runtime with
61 driver can operate in:
70 In this mode the driver is able to receive packets without
79 driver supports the following M.2 wireless network adapters:
94 driver supports the following
[all …]
|
| H A D | cxgbev.4 | 37 .Nd "Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet VF driver"
39 To compile this driver into the kernel,
47 To load the driver as a
56 driver provides support for Virtual Functions on PCI Express Ethernet adapters
59 The driver supports Jumbo Frames, Transmit/Receive checksum offload,
69 driver uses different names for devices based on the associated ASIC:
78 The Physical Function driver for Chelsio Terminator adapters shares these
80 The driver provides sysctl MIBs for both ports and parent devices using
92 driver supports Virtual Functions on 100Gb and 25Gb Ethernet adapters
110 driver supports Virtual Functions on 40Gb, 10Gb and 1Gb Ethernet adapters
[all …]
|
| H A D | psm.4 | 32 .Nd PS/2 mouse style pointing device driver
47 driver provides support for the PS/2 mouse style pointing device.
53 the keyboard controller driver,
71 driver allows the user to initially set the resolution
72 via the driver flag
74 .Sx "DRIVER CONFIGURATION" )
93 driver has three levels of operation.
96 At the level zero the basic support is provided; the device driver will report
102 This is the default level of operation and the driver is initially
118 the driver at this level.
[all …]
|
| /freebsd/lib/libdevctl/ |
| H A D | devctl.3 | 72 .Fn devctl_set_driver "const char *device" "const char *driver" "bool force"
113 function probes a device and attaches a suitable device driver if one is
118 function detaches a device from its current device driver.
119 The device is left detached until either a new driver for its parent
125 the current device driver will be detached even if the device is busy.
139 If the device is currently attached to a device driver,
140 the device driver will be detached from the device,
145 the current device driver will be detached even if the device is busy.
153 The device will probe and attach if a suitable device driver is found.
159 but any device driver currently attached to the device will remain attached.
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | DRIVER_MODULE.9 | 37 .Nd kernel driver declaration macro
43 .Fn DRIVER_MODULE name busname "driver_t driver" "modeventhand_t evh" "void *arg"
44 .Fn DRIVER_MODULE_ORDERED name busname "driver_t driver" "modeventhand_t evh" "void *arg" "int orde…
45 .Fn EARLY_DRIVER_MODULE name busname "driver_t driver" "modeventhand_t evh" "void *arg" "int pass"
46 .Fn EARLY_DRIVER_MODULE_ORDERED name busname "driver_t driver" "modeventhand_t evh" "void *arg" "en…
50 macro declares a kernel driver.
52 expands to the real driver declaration, where the phrase
54 is used as the naming prefix for the driver and its functions.
61 is the parent bus of the driver (PCI, ISA, PPBUS and others), e.g.\&
69 can be different from the driver name.
[all …]
|
| H A D | crypto_driver.9 | 86 submitted to sessions associated with the driver.
95 methods are defined in the method table for the device driver attached to
98 specifies the size of a driver-specific per-session structure allocated by
101 is a bitmask of properties about the driver.
117 returns an opaque driver id.
120 unregisters a driver from the cryptographic framework.
130 is invoked by the cryptographic framework on each active driver to
131 determine the best driver to use for the session.
134 If a driver does not support requests described by
137 If the driver does support requests described by
[all …]
|
| /freebsd/sys/contrib/edk2/Include/Protocol/ |
| H A D | PciHotPlugRequest.h | 2 Provides services to notify the PCI bus driver that some events have happened
4 PCI bus driver to create or destroy handles for PCI-like devices.
6 A hot-plug capable PCI bus driver should produce the EFI PCI Hot Plug Request
8 is installed after PCI bus does the enumeration, the PCI bus driver can be
10 into the PC Card socket, the PC Card bus driver can call interface of this
11 protocol to notify PCI bus driver to allocate resource and create handles for
14 The EFI_PCI_HOTPLUG_REQUEST_PROTOCOL is installed by the PCI bus driver on a
15 separate handle when PCI bus driver starts up. There is only one instance in
16 the system. Any driver that wants to use this protocol must locate it globally.
17 The EFI_PCI_HOTPLUG_REQUEST_PROTOCOL allows the driver of hot-plug controller,
[all …]
|
| H A D | DriverBinding.h | 4 This protocol is produced by every driver that follows the UEFI Driver Model,
16 /// The global ID for the ControllerHandle Driver Protocol.
26 Tests to see if this driver supports a given controller. If a child device is provided,
27 it further tests to see if this driver supports creating a handle for the specified child device.
29 This function checks to see if the driver specified by This supports the device specified by
32 ControllerHandle to determine if the driver supports ControllerHandle. This function
36 device specified by ControllerHandle may already be managed by the same driver or a
37 different driver. This function must match its calls to AllocatePages() with FreePages(),
39 Because ControllerHandle may have been previously started by the same driver, if a protocol is
46 an I/O abstraction to the driver.
[all …]
|
| H A D | Ip4Config.h | 57 Starts running the configuration policy for the EFI IPv4 Protocol driver.
60 configuration policy by the EFI IPv4 Protocol driver. This determination may
62 driver configuration policy. It may be as involved as loading some defaults
71 Until the configuration completes successfully, EFI IPv4 Protocol driver instances
73 Once the configuration is complete, the EFI IPv4 Configuration Protocol driver
75 Note that in this case the EFI IPv4 Configuration Protocol driver must signal
76 ReconfigEvent, and all EFI IPv4 Protocol driver instances that are using default
82 Protocol driver configuration policy completes
85 Protocol driver configuration needs to be updated.
89 driver is now running.
[all …]
|
| H A D | PciPlatform.h | 3 the PCI bus driver/PCI Host Bridge Resource Allocation driver and a platform-specific
4 driver to describe the unique features of a platform.
44 /// resources. If a PCI device driver asks for these resources, the request
54 /// The PCI bus driver will not allocate I/O addresses out of the ISA I/O
61 /// In this case, the PCI bus driver will ask the PCI host bridge driver for
62 /// larger I/O ranges. The PCI host bridge driver is not aware of the ISA
74 /// 3FF), but not if it also asks for the ISA aliases. The PCI bus driver will
77 /// driver asks for the ISA I/O ranges, including aliases, the request will be
97 /// bus driver will not allocate I/O addresses out of the legacy ISA I/O
98 /// range (0x100-0x3FF). If a PCI device driver asks for the ISA I/O
[all …]
|
| H A D | IdeControllerInit.h | 5 to the driver entity. This protocol is mandatory for IDE controllers if the
6 IDE devices behind the controller are to be enumerated by a driver entity.
10 IDE controller. A driver entity that wishes to manage an IDE bus and possibly
48 /// The driver entity is about to begin enumerating the devices
54 /// The driver entity has completed enumerating the devices
60 /// The driver entity is about to reset the devices behind the
66 /// The driver entity has completed resetting the devices behind
72 /// The driver entity is about to detect the presence of devices
79 /// The driver entity is done with detecting the presence of
85 /// The IDE bus is requesting the IDE controller driver to
[all …]
|
| /freebsd/contrib/wpa/src/drivers/ |
| H A D | driver.h | 2 * Driver interface definition
8 * This file defines a driver interface used by both %wpa_supplicant and
10 * driver operations. This is followed by the struct wpa_driver_ops that each
11 * driver wrapper will beed to define with callback functions for requesting
12 * driver operations. After this, there are definitions for driver event
154 * channel (used internally in src/ap/acs.c; driver wrappers do not
354 * scan result processing if left zero by the driver wrapper)
364 * driver. Each driver interface implementation is responsible for converting
365 * the driver or OS specific scan results into this format.
367 * If the driver does not support reporting all IEs, the IE data structure is
[all …]
|
| /freebsd/sys/dev/ice/ |
| H A D | ice_rdma.c | 34 * @brief RDMA client driver interface
36 * Functions to interface with the RDMA client driver, for enabling RMDA
37 * functionality for the ice driver.
42 * The ice device driver provides the rmda_di_if.m interface methods, while
43 * the client RDMA driver provides the irdma_if.m interface methods as an
46 * The initial connection between drivers is done via the RDMA client driver
58 * @brief global RDMA driver state
60 * Contains global state the driver uses to connect to a client RDMA interface
61 * driver.
91 * @brief RDMA driver interfac
[all...] |
| H A D | irdma_if.m | 35 * KOBject methods implemented by the RDMA client driver. These functions will
36 * be called from the ice driver to notify the RDMA client driver of device
37 * driver events.
44 * probe - Notify the RDMA client driver that a peer device has been created
47 * Called by the ice driver during attach to notify the RDMA client driver
56 * open - Notify the RDMA client driver that a peer device has been opened
59 * Called by the ice driver during the if_init routine to notify the RDMA
60 * client driver tha
[all...] |
| /freebsd/contrib/llvm-project/clang/lib/Driver/ToolChains/ |
| H A D | Flang.h | 12 #include "clang/Driver/Tool.h"
13 #include "clang/Driver/Action.h"
14 #include "clang/Driver/Compilation.h"
15 #include "clang/Driver/ToolChain.h"
20 namespace driver {
27 /// Extract fortran dialect options from the driver arguments and add them to
30 /// \param [in] Args The list of input driver arguments
35 /// Extract preprocessing options from the driver arguments and add them to
38 /// \param [in] Args The list of input driver arguments
43 /// Extract PIC options from the driver arguments and add them to
[all …]
|
| /freebsd/usr.sbin/devctl/ |
| H A D | devctl.8 | 36 .Cm clear driver
57 .Cm set driver
59 .Ar device driver
101 If a suitable driver is found,
107 Detach the device from its current device driver.
111 the device driver will be detached even if the device is busy.
117 If the device is currently attached to a device driver,
118 the device driver will be detached from the device,
123 the device driver will be detached even if the device is busy.
126 The device will probe and attach if a suitable device driver is found.
[all …]
|
| /freebsd/sys/contrib/dev/athk/ath10k/ |
| H A D | trace.h | 54 __string(driver, dev_driver_string(ar->dev))
59 __assign_str(driver, dev_driver_string(ar->dev));
64 __get_str(driver),
90 __string(driver, dev_driver_string(ar->dev))
96 __assign_str(driver, dev_driver_string(ar->dev));
102 __get_str(driver),
116 __string(driver, dev_driver_string(ar->dev))
125 __assign_str(driver, dev_driver_string(ar->dev));
134 __get_str(driver),
148 __string(driver, dev_driver_string(ar->dev))
[all …]
|