/freebsd/contrib/wpa/src/drivers/ |
H A D | drivers.mk | 13 ##### COMMON DRIVERS 17 DRV_OBJS += src/drivers/driver_wired.c 23 DRV_OBJS += src/drivers/driver_macsec_linux.c 30 DRV_OBJS += src/drivers/driver_wired_common.c 35 DRV_OBJS += src/drivers/driver_nl80211.c 36 DRV_OBJS += src/drivers/driver_nl80211_android.c 37 DRV_OBJS += src/drivers/driver_nl80211_capa.c 38 DRV_OBJS += src/drivers/driver_nl80211_event.c 39 DRV_OBJS += src/drivers/driver_nl80211_monitor.c 40 DRV_OBJS += src/drivers/driver_nl80211_scan.c [all …]
|
H A D | drivers.mak | 13 ##### COMMON DRIVERS 17 DRV_OBJS += ../src/drivers/driver_wired.o 23 DRV_OBJS += ../src/drivers/driver_macsec_linux.o 35 DRV_OBJS += ../src/drivers/driver_macsec_qca.o 40 DRV_OBJS += ../src/drivers/driver_wired_common.o 45 DRV_OBJS += ../src/drivers/driver_nl80211.o 46 DRV_OBJS += ../src/drivers/driver_nl80211_capa.o 47 DRV_OBJS += ../src/drivers/driver_nl80211_event.o 48 DRV_OBJS += ../src/drivers/driver_nl80211_monitor.o 49 DRV_OBJS += ../src/drivers/driver_nl80211_scan.o [all …]
|
/freebsd/contrib/kyua/drivers/ |
H A D | Makefile.am.inc | 36 libdrivers_a_SOURCES = drivers/debug_test.cpp 37 libdrivers_a_SOURCES += drivers/debug_test.hpp 38 libdrivers_a_SOURCES += drivers/list_tests.cpp 39 libdrivers_a_SOURCES += drivers/list_tests.hpp 40 libdrivers_a_SOURCES += drivers/report_junit.cpp 41 libdrivers_a_SOURCES += drivers/report_junit.hpp 42 libdrivers_a_SOURCES += drivers/run_tests.cpp 43 libdrivers_a_SOURCES += drivers/run_tests.hpp 44 libdrivers_a_SOURCES += drivers/scan_results.cpp 45 libdrivers_a_SOURCES += drivers/scan_results.hpp [all …]
|
H A D | report_junit_test.cpp | 29 #include "drivers/report_junit.hpp" 36 #include "drivers/scan_results.hpp" 171 ATF_REQUIRE_EQ("dir1.dir2.program", drivers::junit_classname(test_program)); in ATF_TEST_CASE_BODY() 179 drivers::junit_duration(datetime::delta(0, 456700))); in ATF_TEST_CASE_BODY() 181 drivers::junit_duration(datetime::delta(3, 120000))); in ATF_TEST_CASE_BODY() 182 ATF_REQUIRE_EQ("5.000", drivers::junit_duration(datetime::delta(5, 0))); in ATF_TEST_CASE_BODY() 192 + drivers::junit_metadata_header in ATF_TEST_CASE_BODY() 195 ATF_REQUIRE_EQ(expected, drivers::junit_metadata(metadata)); in ATF_TEST_CASE_BODY() 220 + drivers::junit_metadata_header in ATF_TEST_CASE_BODY() 236 ATF_REQUIRE_EQ(expected, drivers::junit_metadata(metadata)); in ATF_TEST_CASE_BODY() [all …]
|
H A D | report_junit.cpp | 29 #include "drivers/report_junit.hpp" 56 drivers::junit_classname(const model::test_program& test_program) in junit_classname() 71 drivers::junit_duration(const datetime::delta& delta) in junit_duration() 78 const char* const drivers::junit_metadata_header = 85 const char* const drivers::junit_timing_header = 93 const char* const drivers::junit_stderr_header = 107 drivers::junit_metadata(const model::metadata& metadata) in junit_metadata() 135 drivers::junit_timing(const datetime::timestamp& start_time, in junit_timing() 150 drivers::report_junit_hooks::report_junit_hooks(std::ostream& output_) : in report_junit_hooks() 160 drivers::report_junit_hooks::got_context(const model::context& context) in got_context() [all …]
|
H A D | report_junit.hpp | 29 /// \file drivers/report_junit.hpp 38 #include "drivers/scan_results.hpp" 43 namespace drivers { namespace 59 class report_junit_hooks : public drivers::scan_results::base_hooks { 69 void end(const drivers::scan_results::result&); 73 } // namespace drivers
|
/freebsd/contrib/ntp/html/ |
H A D | refclock.html | 24 <li class="inline"><a href="#list">List of Reference Clock Drivers</a></li> 28 …Drivers</a> and <a href="howto.html">How To Write a Reference Clock Driver</a> pages. Information … 30 …ients and use the same filter, select, cluster and combine algorithms. Drivers have addresses in… 31 …efer</tt> Keyword</a> page. Some of these options have meaning only for selected clock drivers.</p> 32 <p>The <tt>fudge</tt> command can be used to provide additional information for individual drivers… 34 <p>The <a href="audio.html">Audio Drivers</a> page describes three software drivers that process au… 35 <p>The <a href="drivers/driver1.html"> Undisciplined Local Clock</a> driver can simulate a referenc… 37 …drivers make use of the pulse-per-second (PPS) signal discipline, which is part of the gene… 38 <p>Some drivers depending on longwave or shortwave radio services need to know the radio propagatio… 39 … switching from one driver to the another, it is useful to calibrate the drivers to a common ensem… [all …]
|
H A D | audio.html | 6 <title>Reference Clock Audio Drivers</title> 10 <h3>Reference Clock Audio Drivers</h3> 21 <li class="inline"><a href="#sound">Sound Card Drivers</a></li> 22 <li class="inline"><a href="#short">Shortwave Radio Drivers</a></li> 26 <h4 id="sound">Sound Card Drivers</h4> 27 …drivers currently includes three drivers suitable for these applications. They include a driver fo… 28 <p>All three drivers make ample use of sophisticated digital signal processing 30 The radio station drivers in particular implement optimum linear demodulation 35 <p>Currently, the audio drivers work with with Sun operating systems and audio codecs, including Su… 36 <p>The audio drivers include a number of common features designed to groom input signals, suppress … [all …]
|
/freebsd/share/man/man9/ |
H A D | crypto_session.9 | 72 classes of drivers. 78 Request hardware drivers. 79 Hardware drivers do not use the host CPU to perform operations. 82 Request software drivers. 83 Software drivers use the host CPU to perform operations. 88 Additional software drivers may also be available on architectures which 92 If both hardware and software drivers are requested, 93 hardware drivers are preferred over software drivers. 94 Accelerated software drivers are preferred over the baseline software driver. 95 If multiple hardware drivers are available, [all …]
|
H A D | bus_attach_children.9 | 43 Note that most bus drivers do not use hints to identify child devices. 48 iterates over all eligible device drivers for children of 53 This allows device drivers to add child devices that are enumerated via 60 attaches device drivers to all children of 65 It makes a best-effort pass to attach device drivers to all children. 75 attaches device drivers to all children of 88 detaches device drivers from all children of
|
H A D | DEVICE_PROBE.9 | 92 possible other driver may exist (typically legacy drivers who don't follow 93 all the rules, or special needs drivers). 96 This is for source or binary drivers that are not yet integrated into the 103 the normal return value for drivers to use. 104 It is intended that nearly all of the drivers in the tree should return 109 The driver has special requirements like when there are two drivers 116 This allows drivers to match all serial ports generally, with specialized 117 drivers matching particular types of serial ports that need special
|
H A D | ieee80211.9 | 63 IEEE 802.11 device drivers are written to use the infrastructure provided 67 This software provides a support framework for drivers that includes 70 Most drivers depend on the 96 layer with drivers responsible purely for moving data between the host 103 instead drivers are notified of state changes that 108 layer means that drivers must be structured to follow specific rules. 109 Drivers that support only a single interface at any time must still 223 Drivers are expected to setup various shared state in these structures 264 structures also hold a collection of method pointers that drivers 266 These methods are the primary way drivers are bound to the [all …]
|
H A D | intro.9 | 198 Disk drivers connect themselves to GEOM using the 204 facility provides an interface for recording device statistics in disk drivers. 212 API, which has functions for drivers and consumers. 244 .Ss Device Drivers 254 Most drivers act as devices, and provide a set of methods implementing the 264 Bus drivers will implement additional methods, such as 275 Drivers can request and manage their resources (e.g. memory-space or IRQ 306 Most device drivers use the 401 This API provides an interface for both consumers and crypto drivers; 420 Device drivers register their interrupt handlers using the [all …]
|
H A D | crypto_driver.9 | 36 .Nd interface for symmetric cryptographic drivers 85 Symmetric cryptographic drivers process cryptographic requests 88 Cryptographic drivers call 108 should be used for drivers which process requests using host CPUs. 110 should be used for drivers which process requests on separate co-processors. 112 should be set for drivers which process requests synchronously in 115 should be set for software drivers which use accelerated CPU instructions. 140 The framework prefers drivers with the largest negative value,
|
/freebsd/share/man/man4/ |
H A D | mouse.4 | 32 .Nd mouse and pointing device drivers 36 The mouse drivers 42 Currently there are specific device drivers for bus, InPort, PS/2, and USB mice. 58 The mouse drivers may have ``non-blocking'' attribute which will make 61 Mouse device drivers often offer several levels of operation. 67 Most drivers provide horizontal and vertical movement of the mouse 133 Device drivers may offer operation levels higher than one. 134 Refer to manual pages of individual drivers for details. 138 commands are defined for the mouse drivers. 143 Refer to manual pages of individual drivers for specific details. [all …]
|
H A D | ppbus.4 | 43 system for the implementation of drivers to control various parallel devices, 45 .Sh DEVICE DRIVERS 46 In order to write new drivers or port existing drivers, the ppbus system 57 with kernel-in drivers. 59 .Ss Developing new drivers 69 .Ss Porting existing drivers 70 Another approach to the ppbus system is to port existing drivers. 71 Various drivers have already been ported: 86 parallel port bus, then initialize it and upper peripheral device drivers. 268 layer gathers the parallel peripheral device drivers. [all …]
|
H A D | intro.4 | 32 .Nd introduction to devices and device drivers 34 This section contains information related to devices, device drivers 62 Not all drivers implement all system calls; for example, calling 96 directly by the drivers in the kernel. 112 .Ss Drivers without device nodes 113 Drivers for network devices do not use device nodes in order to be 123 to select the facilities and drivers for that kernel, and to tune 135 Drivers need not be statically compiled into the kernel; they may also be
|
H A D | cpufreq.4 | 57 control drivers. 58 It combines multiple drivers offering different settings into a single 67 These settings may be overridden by kernel drivers requesting alternate 120 .Sh SUPPORTED DRIVERS 121 The following device drivers offer absolute frequency control via the 143 The following device drivers offer relative frequency control and 232 Kernel drivers offering hardware-specific CPU frequency control export 282 flag if the settings it provides are information for other drivers only 319 The following drivers have not yet been converted to the
|
H A D | scsi.4 | 54 of drivers to control various 66 host adapters through host adapter drivers. 68 appropriate drivers. 169 will suffice for any number of disk drivers. 212 Peripheral drivers can be wired to a specific bus, target, and lun as so: 270 The system allows common device drivers to work through many different 360 .Ss XPT drivers 363 It is also responsible for device discovery for those SIM drivers that do not 368 There are two types of SIM drivers: virtual and physical. 370 Virtual SIM drivers are for communicating with network or virtual machine hosts. [all …]
|
/freebsd/sys/compat/linuxkpi/common/src/ |
H A D | linux_aperture.c | 19 * A graphics device might be supported by different drivers, but only one 21 * graphics drivers, such as EFI-GOP or VESA, early during the boot process. 25 * ownership of framebuffer memory and hand-over between drivers. 27 * Graphics drivers should call aperture_remove_conflicting_devices() 63 * The call to aperture_remove_conflicting_devices() releases drivers that 70 * device drivers can also call aperture_remove_conflicting_pci_devices() and 71 * let the function detect the apertures automatically. Device drivers without 75 * Drivers that are susceptible to being removed by other drivers, such as 76 * generic EFI or VESA drivers, have to register themselves as owners of their 124 * another driver. This only works for platform drivers that support hot [all …]
|
/freebsd/lib/libkiconv/ |
H A D | kiconv_sysctl.c | 46 char *drivers, *drvp; in kiconv_lookupconv() local 48 drivers = malloc(size); in kiconv_lookupconv() 49 if (drivers == NULL) in kiconv_lookupconv() 51 if (sysctlbyname("kern.iconv.drvlist", drivers, &size, NULL, 0) == -1) { in kiconv_lookupconv() 52 free(drivers); in kiconv_lookupconv() 55 for (drvp = drivers; *drvp != '\0'; drvp += strlen(drvp) + 1) in kiconv_lookupconv() 57 free(drivers); in kiconv_lookupconv() 60 free(drivers); in kiconv_lookupconv()
|
/freebsd/sys/dev/igc/ |
H A D | igc_api.c | 15 * set of functions. Called by drivers or by igc_setup_init_funcs. 41 * set of functions. Called by drivers or by igc_setup_init_funcs. 67 * set of functions. Called by drivers or by igc_setup_init_funcs. 142 * of the 'shared' code files. Called by drivers only. 212 * function pointer entry point called by drivers. 227 * pointer entry point called by drivers. 242 * table. This is a function pointer entry point called by drivers. 286 * point called by drivers. 301 * entry point called by drivers. 316 * pointer entry point called by drivers. [all …]
|
/freebsd/sys/kern/ |
H A D | device_if.m | 31 * @defgroup DEVICE device - KObj methods for all device drivers 32 * @brief A basic set of methods required for all device drivers. 34 * The device interface is used to match devices to drivers during 35 * autoconfiguration and provides methods to allow drivers to handle 81 * calling the DEVICE_PROBE() of all candidate drivers and attach 84 * This function is used to match devices to device drivers. 162 * The DEVICE_IDENTIFY() method is used by some drivers (e.g. the ISA 166 * special drivers, including the isahint driver and the pnp driver to 170 * Many bus drivers which support true plug-and-play do not need to 172 * automatically without help from child drivers. [all …]
|
/freebsd/contrib/ntp/html/scripts/ |
H A D | audio.txt | 1 document.write("<p>Reference Clock Audio Drivers</p><ul>\ 2 <li class='inline'><a href='drivers/driver6.html'>IRIG Audio Decoder</a>\ 3 <li class='inline'><a href='drivers/driver7.html'>Radio CHU Audio Demodulator/Decoder</a></li>\ 4 <li class='inline'><a href='drivers/driver36.html'>Radio WWV/H Audio Demodulator/Decoder</a></li>\ 5 <li class='inline'><a href='audio.html'>Reference Clock Audio Drivers</a></li>\
|
/freebsd/sys/dev/e1000/ |
H A D | e1000_api.c | 42 * set of functions. Called by drivers or by e1000_setup_init_funcs. 68 * set of functions. Called by drivers or by e1000_setup_init_funcs. 94 * set of functions. Called by drivers or by e1000_setup_init_funcs. 120 * set of functions. Called by drivers or by e1000_setup_init_funcs. 448 * of the 'shared' code files. Called by drivers only. 581 * function pointer entry point called by drivers. 596 * pointer entry point called by drivers. 611 * table. This is a function pointer entry point called by drivers. 655 * point called by drivers. 670 * This is a function pointer entry point called by drivers. [all …]
|