| /development/host/windows/usb/api/ |
| adb_helper_routines.h | 48 @param[in] class_id Device class ID how it is specified by our USB driver.
68 @param[in] class_id Device class ID how it is specified by our USB driver
126 /** \brief Checks if given interface is available via custom USB driver.
129 be supported by the custom driver. If IOCTL fails, we make a conclusion that
130 this interface is available via WinUsb, and not via custom USB driver.
132 @return true if interface is available via custom USB driver, or false
|
| /external/clang/www/ |
| performance-2009-03-02.html | 53 compilers; gcc is run both with and without the new clang driver (ccc)
54 in order to evaluate the overhead of the driver itself.</p>
66 <li><tt>+ driver</tt>: Add execution of the driver, but do not execute any
67 commands (by using the -### driver option).</li>
88 parse</tt> (for clang) or <tt>+ driver</tt> with gcc. This amounts to
|
| /external/mesa3d/docs/ |
| RELNOTES-6.1 | 56 Driver / context changes
63 functions they implement. In particular, the ctx->Driver.NewTextureObject
69 ctx->Driver.Accum to point to _swrast_Accum). Adding new functions to
79 depending on the device driver's capabilities. For example, if the
80 driver enables all the ARB extensions which are part of OpenGL 1.5
89 Driver Status
|
| xlibdriver.html | 3 <TITLE>Xlib Software Driver</TITLE>
9 <H1>Xlib Software Driver</H1>
12 Mesa's Xlib driver provides an emulation of the GLX interface so that
15 Effectively, the Xlib driver converts all OpenGL rendering into Xlib calls.
19 The Xlib driver is the oldest Mesa driver and the most mature of Mesa's
24 Since the Xlib driver <em>emulates</em> the GLX extension, it's not
30 The unique features of the Xlib driver follows.
174 Hardware overlay planes are supported by the Xlib driver. To
194 The following MESA-specific extensions are implemented in the Xlib driver
[all...] |
| VERSIONS | 46 faster X device driver functions
97 - Preliminary Microsoft Windows driver
163 - Improved device driver interface
165 - Dithering support moved from core into device driver
178 - updated MS Windows driver
196 - preliminary Linux SVGA driver
215 - updated Macintosh driver
216 - new NeXT driver
220 - gamma correction code moved into the X driver for better performance
241 - driver for prototype Cirrus Mondello 3-D boar
[all...] |
| RELNOTES-4.1 | 92 Device Driver Status
100 Driver Status
163 If you're porting a DRI or other driver from Mesa 4.0.x to Mesa 4.1 here
202 target is enabled and complete. This spares the driver writer from
231 - Removed ctx->Driver.SetDrawBuffer()
232 - Removed swrast->Driver.SetReadBuffer().
237 - Added ctx->Driver.DrawBuffer() and ctx->Driver.ReadBuffer().
239 Many drivers will set ctx->Driver.DrawBuffer = _swrast_DrawBuffer and
241 DRI drivers should implement their own function for ctx->Driver.DrawBuffe
[all...] |
| faq.html | 54 the 3Dfx Glide/Voodoo driver, an old S3 driver, etc) but the DRI drivers
107 protocol encoder, and a device driver loader.
108 <li>The device driver modules (such as r200_dri.so) contain a built-in
253 driver).
256 <a name="part3">What you really want is a DRI or NVIDIA (or another vendor's OpenGL) driver
267 <a name="part3">If your DRI-based driver isn't working, go to the
354 <h2>4.2 How do I write a new device driver?</h2>
356 Unfortunately, writing a device driver isn't easy.
362 The best way to get started is to use an existing driver as your startin
[all...] |
| /development/pdk/docs/porting/ |
| power_management.jd | 14 <a href="#androidPowerKernelRegistration">Registering Drivers with the PM Driver</a><br/>
40 <p>If the suspend operation has already started when locking a wakelock, the system will abort the suspend operation as long it has not already reached the <code>suspend_late</code> stage. This means that locking a wakelock from an interrupt handler or a freezeable thread always works, but if you lock a wakelock from a <code>suspend_late</code> handler, you must also return an error from that handler to abort suspend. You can use wakelocks to allow the user-space to decide which keys should wake the full system and turn on the screen. Use <code>set_irq_wake</code> or a platform-specific API to ensure that the keypad interrupt wakes up the CPU. Once the keypad driver has resumed, the sequence of events can look like this:</p>
42 <li> The Keypad driver receives an interrupt, locks the keypad-scan wakelock,
45 driver. </li>
46 <li>The input-event driver sees the key change, enqueues an event, and locks
52 <li>The input-event driver dequeues the key-event and, since the queue is now
67 <a name="driverAPI"></a><h3>Driver API</h3>
68 <p>A driver can use the wakelock API by adding a wakelock variable to its state and calling <code>wake_lock_init</code>, as illustrated in the snippet below:</p>
81 <p> When the driver determines that it needs to run (usually in an interrupt handler), it calls <code>wake_lock</code>:</p>
93 <p> This works whether or not the wakelock is already held. It is useful if the driver woke up other parts of the system that do not use wakelocks but still need to run. Avoid this when (…)
[all...] |
| display_drivers.jd | 14 <li><a href="#androidDisplayDriversSourceTemplate">Implementing Your Own Driver (Driver Template)</a></li>
20 <p>This section describes how the display driver functions and offers a functional template designed to help you build your own device-specific driver.</p>
21 <p>Android relies on the standard frame buffer device (<code>/dev/fb0</code> or <code>/dev/graphics/fb0</code>) and driver as described in the <code>linux/fb.h</code> kernel header file. For more information regarding the standard Linux frame buffer, please see <a href="http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.24.y.git;a=blob;f=Documentation/fb/framebuffer.txt">The Frame Buffer Device</a> at <a href="http://kernel.org">http://kernel.org</a>.
29 <p>Android makes two requirements of the driver: a linear address space of mappable memory that it can write to directly and support for the rgb_565 pixel format. A typical frame display includes:</p>
31 <li>accessing the driver by calling open on <code>/dev/fb0</code></li>
35 <p>When a page flip is required, Android makes another <code>FBIOPUT_VSCREENINFO</code> ioctl call with a new y-offset pointing to the other buffer in video memory. This ioctl, in turn, invokes the driver's <code>.fb_pan_display</code> function in order to do the actual flip. If there isn't sufficient video memory, regular memory is used and is just copied into the video memory when it is time do the flip. After allocating the video memory and setting the pixel format, Android uses <code>mmap()</code> to map the memory into the process's address space. All writes to the frame buffer are done through this mmaped memory.</p>
39 <a name="androidDisplayDriversSourceTemplate"></a><h3>Implementing Your Own Driver (Driver Template)</h3
[all...] |
| /frameworks/compile/slang/ |
| llvm-rs-cc.cpp | 24 #include "clang/Driver/Arg.h"
25 #include "clang/Driver/ArgList.h"
26 #include "clang/Driver/DriverDiagnostic.h"
27 #include "clang/Driver/Option.h"
28 #include "clang/Driver/OptTable.h"
49 // Class under clang::driver used are enumerated here.
50 using clang::driver::arg_iterator;
51 using clang::driver::options::DriverOption;
52 using clang::driver::Arg;
53 using clang::driver::ArgList
[all...] |
| /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/ |
| ipmi.h | 40 * This file describes an interface to an IPMI driver. You have to
44 * With that said, this driver provides a multi-user interface to the
45 * IPMI driver, and it allows multiple IPMI physical interfaces below
46 * the driver. The physical interfaces bind as a lower layer on the
47 * driver. They appear as interfaces to the application using this
50 * Multi-user means that multiple applications may use the driver,
51 * send commands, receive responses, etc. The driver keeps track of
54 * response doesn't come back in time, the driver will return a
56 * from the BMC event queue will go to all users bound to the driver.
59 * anything is in it. Incoming commands to the driver will ge
[all...] |
| ethtool.h | 33 /* these strings are set to whatever the driver author decides... */
36 char driver[32]; /* driver short name, "tulip", "eepro100" */ member in struct:ethtool_drvinfo
37 char version[32]; /* driver version string */
68 __u32 version; /* driver-specific, indicates different chips/revs */
141 * not implemented by the driver causes these values to be
183 * of pending RX/TX ring entries the driver will allow the
211 * then {rx,tx}_pause force the driver to use/not-use pause
264 * or not the driver should turn on (set) or off (clear) a behavior.
278 #define ETHTOOL_GDRVINFO 0x00000003 /* Get driver info. *
[all...] |
| /system/extras/tests/wifi/stress/ |
| wifiLoadScanAssoc.c | 23 * 1. Load WiFi driver
28 * 6. Unload WiFi driver
34 * may be performed while the WiFi driver is still performing a scan
119 * 4. Restore state of WiFi driver to state it was at the
277 // Load WiFi Driver
333 // If needed restore WiFi driver to state it was in at the
334 // start of the test. It is assumed that it the driver
337 // Load driver
339 testPrintE("main load driver failed, rv: %i", rv);
382 * 4. Determine whether WiFi driver is loaded and if s
[all...] |
| /external/wpa_supplicant_8/src/ap/ |
| hostapd.c | 21 #include "drivers/driver.h"
73 "the kernel driver.");
88 wpa_printf(MSG_ERROR, "Could not set SSID for kernel driver");
312 * When IEEE 802.1X is not enabled, the driver may need to know how to
346 wpa_printf(MSG_WARNING, "Could not connect to kernel driver.");
439 wpa_printf(MSG_ERROR, "Driver did not accept BSSID mask "
581 /* Set SSID for the kernel driver (to be used in beacon and probe
585 wpa_printf(MSG_ERROR, "Could not set SSID for kernel driver");
642 if (hapd->driver && hapd->driver->set_operstate
[all...] |
| /external/clang/include/clang/Driver/ |
| Option.h | 1 //===--- Option.h - Abstract Driver Options ---------------------*- C++ -*-===//
13 #include "clang/Driver/OptSpecifier.h"
18 namespace driver { namespace in namespace:clang
23 /// Option - Abstract representation for a single form of driver
26 /// An Option class represents a form of option that the driver
31 /// flags. At runtime the driver parses the command line into
85 /// This option is only consumed by the driver.
169 /// by the driver.
184 /// InputOption - Dummy option class for representing driver inputs.
315 } // end namespace driver
[all...] |
| /external/qemu/distrib/sdl-1.2.12/src/video/ |
| SDL_sysvideo.h | 32 /* This file prototypes the video driver implementation.
40 /* The SDL video driver */
43 /* Define the SDL video driver structure */
50 /* The name of this video driver */
179 /* Make the context associated with this driver current */
262 driver can place the mouse in relative mode, which may result
270 /* Initialize keyboard mapping for this driver */
289 /* Driver information flags */
290 int handles_any_size; /* Driver handles any size video mode */
318 /* Data private to this driver */
[all...] |
| /hardware/libhardware_legacy/include/hardware_legacy/ |
| AudioHardwareInterface.h | 46 * It provides information about various properties of the audio output hardware driver.
75 * return the audio hardware driver latency in milli seconds.
88 /** write audio buffer to driver. Returns number of bytes written */
117 * It defines the various properties of the audio hardware input driver.
126 /** return the input buffer size allowed by audio driver */
143 /** set the input gain for the audio driver. This method is for
147 /** read audio buffer in from audio driver */
169 // Return the amount of input frames lost in the audio driver since the last call of this function.
170 // Audio driver is expected to reset the value to 0 and restart counting upon returning the current value by this function call.
171 // Such loss typically occurs when the user space process is blocked longer than the capacity of audio driver buffers
[all...] |
| /external/clang/tools/driver/ |
| cc1_main.cpp | 16 #include "clang/Driver/Arg.h"
17 #include "clang/Driver/ArgList.h"
18 #include "clang/Driver/CC1Options.h"
19 #include "clang/Driver/DriverDiagnostic.h"
20 #include "clang/Driver/OptTable.h"
37 // Main driver
52 using namespace clang::driver;
|
| /external/qemu/distrib/sdl-1.2.12/src/audio/mint/ |
| SDL_mintaudio_stfa.c | 25 MiNT audio driver
26 using XBIOS functions (STFA driver)
72 /*--- Audio driver functions ---*/
83 /*--- Audio driver bootstrap functions ---*/
89 /* Check if user asked a different audio driver */
91 DEBUG_PRINT((DEBUG_NAME "user asked a different audio driver\n"));
154 MINT_AUDIO_DRIVER_NAME, "MiNT STFA audio driver",
|
| /external/webkit/Tools/Scripts/webkitpy/layout_tests/layout_package/ |
| worker_mixin.py | 157 thread_timeout_sec: time to wait before killing the driver process.
163 driver = worker._port.create_driver(worker._worker_number)
164 driver.start()
168 self.result = worker._run_single_test(driver, test_input)
185 driver.stop()
206 def _run_single_test(self, driver, test_input):
208 test_input, driver, self._name)
|
| /external/wpa_supplicant/ |
| todo.txt | 22 - if driver/hw is not WPA2 capable, must remove WPA_PROTO_RSN flag from
23 ssid->proto fields to avoid detecting downgrade attacks when the driver
28 for unicast); worked also with Host AP driver and madwifi
44 - test wait-for-interface and daemonize combinations with number of driver
73 * global options (ap_scan, ctrl_interfaces) based on OS/driver
78 * "configuration wizard" (step 1: select OS, step 2: select driver, ...) to
118 (subdirs: eap_common, eap_peer, eap_server, driver, driver_ap, ...)
|
| /external/wpa_supplicant_8/wpa_supplicant/ |
| main.c | 34 " -i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] "
38 " [-o<override driver>] [-O<override ctrl>] \\\n"
40 "[-D<driver>] \\\n"
60 " -D = driver name (can be multiple drivers: nl80211,wext)\n"
73 " -o = override driver parameter for new interfaces\n"
75 " -p = driver parameters\n"
165 iface->driver = optarg;
|
| /frameworks/base/opengl/specs/ |
| EGL_ANDROID_blob_cache.txt | 183 2. When a client API driver gets updated, that may need to invalidate
184 previously cached entries. How can the driver handle this situation?
186 RESPONSE: There are a number of ways the driver can handle this situation.
187 The recommended way is to include the driver version in all cache keys.
188 That way each driver version will use a set of cache keys that are unique
189 to that version, and conflicts should never occur. Updating the driver
192 values in some way, but the driver does not need to take any special
|
| /external/clang/lib/Driver/ |
| Driver.cpp | 1 //===--- Driver.cpp - Clang GCC Compatible Driver -------------------------===//
14 #include "clang/Driver/Driver.h"
16 #include "clang/Driver/Action.h"
17 #include "clang/Driver/Arg.h"
18 #include "clang/Driver/ArgList.h"
19 #include "clang/Driver/Compilation.h"
20 #include "clang/Driver/DriverDiagnostic.h"
21 #include "clang/Driver/HostInfo.h
[all...] |
| /external/clang/utils/ABITest/ |
| Makefile.test.common | 92 temps/test.%.ref: temps/test.%.driver.ref.o temps/test.%.a.ref.o temps/test.%.b.ref.o
95 temps/test.%.xx: temps/test.%.driver.ref.o temps/test.%.a.x.o temps/test.%.b.x.o
98 temps/test.%.xy: temps/test.%.driver.ref.o temps/test.%.a.x.o temps/test.%.b.y.o
101 temps/test.%.yx: temps/test.%.driver.ref.o temps/test.%.a.y.o temps/test.%.b.x.o
104 temps/test.%.yy: temps/test.%.driver.ref.o temps/test.%.a.y.o temps/test.%.b.y.o
142 test.%.top: inputs/test.%.a.c inputs/test.%.b.c inputs/test.%.driver.c
145 .PRECIOUS: inputs/test.%.a.c inputs/test.%.b.c inputs/test.%.driver.c
150 inputs/test.%.driver.c: test.%.generate
156 $(Verb) $(ABITESTGEN) $(TESTARGS) -o inputs/test.$*.a.c -T inputs/test.$*.b.c -D inputs/test.$*.driver.c --min=$(shell expr $* '*' $(COUNT)) --count=$(COUNT)
|
