driver (full) in projects: openbsd-src - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:driver (Results 1 – 25 of 3080) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...124

/openbsd-src/gnu/llvm/clang/docs/
H A D	DriverInternals.rst	2 Driver Design & Internals 11 This document describes the Clang driver. The purpose of this document 12 is to describe both the motivation and design goals for the driver, as 18 The Clang driver is intended to be a production quality compiler driver 20 interface which is compatible with the gcc driver. 22 Although the driver is part of and driven by the Clang project, it is 31 The number one goal of the driver is to ease the adoption of Clang by 33 call GCC. Although this makes the driver much more complicated than 41 The driver was designed to be flexible and easily accommodate new uses 42 as we grow the clang and LLVM infrastructure. As one example, the driver [all …]
/openbsd-src/usr.sbin/pkg_add/OpenBSD/
H A D	FwUpdate.pm	`57 '[-adinv] [-D keyword] [-p path] [driver...]'); 93 sub is_installed($self, $driver) 95 return $self->{installed_drivers}{$driver}; 108 sub is_needed($self, $driver) 110 my ($self, $driver) = @_; 111 return $self->{machine_drivers}{$driver}; 150 for my $driver (keys %$search) { 151 next unless $_ =~ $match{$driver}; 152 $found->{$driver} = 1; 153 delete $search->{$driver}; [all …]`
/openbsd-src/sys/dev/pci/drm/include/drm/
H A D	drm_module.h	17 * parameters that control DRM driver registration. 19 * Below is an example of initializing a DRM driver for a device on the 30 * the PCI driver my_pci_drv. For more complex module initialization, you 31 * can still use module_init() and module_exit() in your driver. 47 * drm_module_pci_driver - Register a DRM driver for PCI-based devices 48 * @__pci_drv: the PCI driver structure 50 * Registers a DRM driver for devices on the PCI bus. The helper 79 * drm_module_pci_driver_if_modeset - Register a DRM driver for PCI-based devices 80 * @__pci_drv: the PCI driver structure 81 * @__modeset: an additional parameter that disables the driver [all …]
H A D	drm_drv.h	60 * Driver use the GEM memory manager. This should be set for all modern 67 * Driver supports mode setting interfaces (KMS). 73 * Driver supports dedicated render nodes. See also the :ref:`section on 80 * Driver supports the full atomic modesetting userspace API. Drivers 90 * Driver supports &drm_syncobj for explicit synchronization of command 97 * Driver supports the timeline flavor of &drm_syncobj for explicit 104 * Driver supports compute acceleration devices. This flag is mutually exclusive with 112 * Driver supports user defined GPU VA bindings for GEM objects. 118 * Driver supports and requires cursor hotspot information in the 137 * Denote a legacy driver using shadow attach. Do not use. [all …]
H A D	drm_audio_component.h	14 * struct drm_audio_component_ops - Ops implemented by DRM driver, called by hda driver 47 * Called from audio driver. After audio driver sets the 54 * Called from audio driver to get the HDMI/DP audio state of the given 68 * struct drm_audio_component_audio_ops - Ops implemented by hda driver, called by DRM driver 76 * @pin_eld_notify: Notify the HDA driver that pin sense and/or ELD information has changed 78 * Called when the DRM driver has set up audio pipeline or has just 79 * begun to tear it down. This allows the HDA driver to update its 87 * Called by HDA driver to check and convert from the pin widget node 116 * @ops: Ops implemented by DRM driver, called by hda driver 120 * @audio_ops: Ops implemented by hda driver, called by DRM driver
/openbsd-src/gnu/llvm/lldb/utils/lui/
H A D	lui.py	`38 def handle_args(driver, argv): argument 58 driver.attachProcess(ui, pid) 66 driver.loadCore(options.core) 70 driver.createTarget(args[1]) 74 driver.createTarget(args[1], args[2:]) 84 def __init__(self, screen, event_queue, driver): argument 87 self.driver = driver 97 driver, 0, h - command_win_height, w, command_win_height) 99 self.source_win = sourcewin.SourceWin(driver, 0, 0, 101 self.break_win = breakwin.BreakWin(driver, w - break_win_width, 0, [all …]`
/openbsd-src/gnu/llvm/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 …]
H A D	CommonArgs.h	`12 #include "clang/Driver/Driver.h" 13 #include "clang/Driver/InputInfo.h" 14 #include "clang/Driver/Multilib.h" 15 #include "clang/Driver/Tool.h" 16 #include "clang/Driver/ToolChain.h" 23 namespace driver { 26 void addPathIfExists(const Driver &D, const Twine &Path, 51 void AddRunTimeLibs(const ToolChain &TC, const Driver &D, 62 void AddStaticDeviceLibsPostLinking(const Driver &D, 68 const InputInfoList *Inputs, const Driver &D, [all …]`
/openbsd-src/share/man/man4/
H A D	iwx.4	28 driver provides support for Intel Wireless AX200/AX210 M.2 network adapters, 34 driver can operate in: 43 In this mode the driver is able to receive packets without 52 driver can be configured to use 68 driver offloads both encryption and decryption of unicast data frames to the 71 In BSS mode the driver supports background scanning; 77 driver can be configured at runtime with 82 The driver needs one of the following firmware files, 104 includes the driver, the firmware files cannot be included and 129 The driver will reset the hardware. [all …]
H A D	wpi.4	39 driver provides support for Intel 44 driver can operate in: 53 In this mode the driver is able to receive packets without 62 driver can be configured to use 78 driver offloads both encryption and decryption of unicast data frames to the 82 the driver supports powersave mode, 88 driver can be configured at runtime with 93 The driver needs at least version 3.1 of the following firmware file, 104 includes the driver, the firmware file cannot be included and 129 The driver will reset the hardware. [all …]
H A D	bwi.4	29 driver provides support for Broadcom AirForce based 34 driver can operate in: 43 In this mode the driver is able to receive packets without 52 driver can be configured to use 68 driver relies on the software 802.11 stack for both encryption and decryption 72 driver depending on the received signal strength and on the number of hardware 77 driver can be configured at runtime with 82 The driver needs a firmware file which is loaded when an interface is 93 .\"includes the driver, the firmware files cannot be included and 101 driver: [all …]
H A D	iwm.4	29 driver provides support for Intel Wireless 37 driver can operate in: 46 In this mode the driver is able to receive packets without 55 driver can be configured to use 71 driver offloads both encryption and decryption of unicast data frames to the 74 In BSS mode the driver supports background scanning; 80 driver can be configured at runtime with 85 The driver needs one of the following firmware files, 104 includes the driver, the firmware files cannot be included and 129 The driver will reset the hardware. [all …]
H A D	ath.4	58 driver provides support for wireless network devices based on 64 driver encapsulates all IP and ARP traffic as 802.11 frames, though 86 algorithm employed by the driver. 90 driver can operate in: 111 In this mode the driver is able to receive packets without 120 driver can be configured to use 136 operations required for WPA in hardware but at this time the driver 140 the driver supports powersave mode, 146 driver can be configured at runtime with 153 driver come in either CardBus or Mini PCI packages. [all …]
H A D	mtw.4	29 driver supports USB 2.0 wireless adapters based on the MediaTek 34 driver can operate in: 43 In this mode the driver is able to receive packets without 52 driver can be configured to use 68 driver offloads both encryption and decryption of data frames to the 73 driver can be configured at runtime with 78 The driver needs the following firmware files, 117 For some reason, the driver was unable to read the microcode file from the 125 The driver will reset the hardware. 139 driver first appeared in [all …]
H A D	rtwn.4	`30 driver supports PCIe wireless network devices based on the Realtek 45 driver can operate in: 54 In this mode the driver is able to receive packets without 63 driver can be configured to use 80 driver can be configured at runtime with 86 the driver when the device is attached: 114 For some reason, the driver was unable to read the microcode file from the 119 The driver will reset the hardware. 133 driver first appeared in 138 driver was written by [all …]`
H A D	iwn.4	29 driver provides support for Intel Wireless WiFi Link 4965/5000/1000 44 driver provides support for the 5100 (codenamed Shirley Peak 1x2), 79 driver can operate in: 88 In this mode the driver is able to receive packets without 97 driver can be configured to use 113 driver offloads both encryption and decryption of unicast data frames to the 116 In BSS mode the driver supports powersave mode 123 driver can be configured at runtime with 128 The driver needs at least version 5.6 of the following firmware files, 150 includes the driver, the firmware files cannot be included and [all …]
H A D	iwi.4	39 driver provides support for Intel 44 driver can operate in: 62 In this mode the driver is able to receive packets without 71 driver can be configured to use 87 driver relies on the software 802.11 stack for both encryption and decryption 92 driver can be configured at runtime with 97 The driver needs at least version 3.1 of the following firmware files, 110 includes the driver, the firmware files cannot be included and 136 The driver will reset the hardware. 139 For some reason, the driver was unable to read the firmware image from the [all …]
H A D	ipw.4	39 driver provides support for the Intel PRO/Wireless 2100 Mini PCI 44 driver can operate in: 62 In this mode the driver is able to receive packets without 71 driver can be configured to use 87 driver relies on the software 802.11 stack for both encryption and decryption 92 driver can be configured at runtime with 97 The driver needs at least version 1.3 of the following firmware files, 110 includes the driver, the firmware files cannot be included and 136 The driver will reset the hardware. 139 For some reason, the driver was unable to read the firmware image from the [all …]
H A D	an.4	48 driver provides support for the Aironet Communications 4500, 4800 68 driver has Plug and Play support and will work in either configuration, 69 however when using a hard-wired I/O address and IRQ, the driver 78 driver encapsulates all IP and ARP traffic as 802.11 frames, though 83 driver can operate in: 101 In this mode the driver is able to receive packets without 110 driver can be configured to use hardware 118 the driver supports powersave mode, 124 driver can be configured at runtime with 143 The driver was unable to allocate memory for transmit frames in the [all …]
H A D	puc.4	37 .Nd PCI universal communications card driver 46 driver provides support for PCI communications cards containing 52 The driver is called 57 The driver currently supports the following cards and controllers: 148 The driver does not support these cards: 163 hardware documentation, and the port numbers used by the driver 175 driver first appeared in 185 driver was written by 188 The current design of this driver keeps any 195 Some of the cards supported by this driver have jumper-selectable [all …]
/openbsd-src/gnu/llvm/clang/lib/Frontend/
H A D	CreateInvocationFromCommandLine.cpp	9 // Construct a compiler invocation object for command line driver arguments 14 #include "clang/Driver/Action.h" 15 #include "clang/Driver/Compilation.h" 16 #include "clang/Driver/Driver.h" 17 #include "clang/Driver/Options.h" 18 #include "clang/Driver/Tool.h" 39 // FIXME: Find a cleaner way to force the driver into restricted modes. in createInvocation() 46 driver::Driver TheDriver(Args[0], llvm::sys::getDefaultTargetTriple(), *Diags, in createInvocation() 53 std::unique_ptr<driver::Compilation> C(TheDriver.BuildCompilation(Args)); in createInvocation() 57 if (C->getArgs().hasArg(driver::options::OPT_fdriver_only)) in createInvocation() [all …]
/openbsd-src/sys/dev/pci/drm/
H A D	aperture.c	20 * driver can be active at any given time. Many systems load a generic 22 * During later boot stages, they replace the generic driver with a dedicated, 23 * hardware-specific driver. To take over the device, the dedicated driver 24 * first has to remove the generic driver. Aperture functions manage 29 * driver that is currently associated with the given framebuffer memory. 65 * output on the framebuffer. If successful, the new driver can take over 79 * driver is the owner of the framebuffer range. The function fails if the 80 * framebuffer is already owned by another driver. See below for an example. 119 * The similar to the previous example, the generic driver claims ownership 121 * memory range, or parts of it, is already owned by another driver. [all …]
/openbsd-src/share/man/man9/
H A D	crypto.9	99 Sessions are used to cache cryptographic information in a particular driver 132 the driver to establish the session. 134 hardware driver should be used (1) or not (0). 180 by the device driver processing the request. 199 essence, SID acts as an index in the session cache of the driver). 249 session migration (move a session from one driver to another, because 331 the driver used to perform the operation, whereas for decryption 381 .Sh DRIVER-SIDE API 393 function to acquire a driver identifier, specifying the 397 For each algorithm the driver supports, it must then call [all …]
/openbsd-src/games/hunt/hunt/
H A D	list.c	`28 struct driver drivers = NULL; 38 struct driver 45 struct driver * 51 struct driver driver; in next_driver_fd() local 90 return (struct driver )-1; in next_driver_fd() 102 2 * sizeof(driver)); in next_driver_fd() 106 drivers = calloc(sizeof driver, maxdrivers); in next_driver_fd() 111 driver = &drivers[numdrivers]; in next_driver_fd() 112 len = sizeof driver->addr; in next_driver_fd() 113 ret = recvfrom(s, &resp, sizeof resp, 0, &driver->addr, &len); in next_driver_fd() [all …]`
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Simple/lib/Test2/IPC/
H A D	Driver.pm	1 package Test2::IPC::Driver; 66 Test2::IPC::Driver - Base class for Test2 IPC drivers. 70 package Test2::IPC::Driver::MyDriver; 72 use base 'Test2::IPC::Driver'; 97 Test2::IPC::Driver has an C<import()> method. All drivers inherit this import 98 method. This import method registers the driver. 100 In most cases you just need to load the desired IPC driver to make it work. You 101 should load this driver as early as possible. A warning will be issued if you 104 use Test2::IPC::Driver::MyDriver; 109 package Test2::IPC::Driver [all...]

12 3 4 5 6 7 8 9 10 >>...124