| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/sysroot/usr/include/linux/ |
| wimax.h | 147 * is ok to have drivers move directly to %WIMAX_ST_UNINITIALIZED
193 * referred to by drivers or userspace. They look ugly, but that's the
|
| cdrom.h | 3 * General header file for linux CD-ROM drivers
21 * device drivers that actually talk to the drives. There may still be
37 * can be found at: ftp://ftp.gwdg.de/pub/linux/cdrom/drivers/cm206/
50 * all the various cdrom drivers. For the CD-ROM ioctls, we
116 * They _will_ be adopted by all CD-ROM drivers, when all the CD-ROM
117 * drivers are eventually ported to the uniform CD-ROM driver interface.
|
| /prebuilts/misc/windows/sdl2/test/ |
| testautomation_audio.c | 72 /* Loop over all available audio drivers */
75 SDLTest_AssertCheck(iMax > 0, "Validate number of audio drivers; expected: >0 got: %d", iMax);
129 /* Loop over all available audio drivers */
132 SDLTest_AssertCheck(iMax > 0, "Validate number of audio drivers; expected: >0 got: %d", iMax);
309 /* Get number of drivers */
312 SDLTest_AssertCheck(n>=0, "Verify number of audio drivers >= 0, got: %i", n);
314 /* List drivers. */
873 { (SDLTest_TestCaseFp)audio_initQuitAudio, "audio_initQuitAudio", "Init and quit audio drivers directly.", TEST_DISABLED };
[all...] |
| /test/vts-testcase/hal/script/build/ |
| build_rule_gen.py | 77 """Updates build rules for vts drivers/profilers.
79 Updates vts drivers/profilers for each pair of (hal_name, hal_version)
|
| /device/linaro/bootloader/edk2/EmulatorPkg/EmuBlockIoDxe/ |
| EmuBlockIo.c | 377 ControllerHandle. Drivers will typically use the device path attached to
395 parameter is ignored by device drivers, and is optional for bus
396 drivers. For bus drivers, if this parameter is not NULL, then
479 parameter is ignored by device drivers, and is optional for bus
480 drivers. For a bus driver, if this parameter is NULL, then handles
|
| /device/linaro/bootloader/edk2/EmulatorPkg/EmuSimpleFileSystemDxe/ |
| EmuSimpleFileSystem.c | 566 ControllerHandle. Drivers will typically use the device path attached to
584 parameter is ignored by device drivers, and is optional for bus
585 drivers. For bus drivers, if this parameter is not NULL, then
670 parameter is ignored by device drivers, and is optional for bus
671 drivers. For a bus driver, if this parameter is NULL, then handles
|
| /device/linaro/bootloader/edk2/EmulatorPkg/EmuSnpDxe/ |
| EmuSnpDxe.c | 562 order to make drivers as small as possible, there are a few calling
671 drivers as small as possible, there are a few calling restrictions for
847 make drivers as small as possible, there are a few calling
954 the same for UEFI Applications, UEFI OS Loaders, and UEFI Drivers including
955 both device drivers and bus drivers.
[all...] |
| /device/linaro/bootloader/edk2/MdeModulePkg/Universal/Network/Ip4Dxe/ |
| Ip4Driver.c | 54 the same for UEFI Applications, UEFI OS Loaders, and UEFI Drivers including
55 both device drivers and bus drivers.
97 order to make drivers as small as possible, there are a few calling
489 drivers as small as possible, there are a few calling restrictions for
596 make drivers as small as possible, there are a few calling
|
| /device/linaro/bootloader/edk2/OvmfPkg/VirtioNetDxe/ |
| DriverBinding.c | 292 device specified by ControllerHandle. Drivers will typically use the device
316 device drivers, and is optional for bus
317 drivers. For bus drivers, if this parameter
409 device drivers, and is optional for bus
410 drivers. For a bus driver, if this parameter
|
| /device/linaro/bootloader/edk2/Vlv2TbltDevicePkg/Include/Protocol/ |
| I2cMasterMcg.h | 153 \section ThirdPartyI2cDrivers Third Party I2C Drivers
176 third party I2C driver writer may choose to write two drivers, one
201 the maximum slave address value. All other drivers and
437 prevent confusing the third party I2C drivers due to a state
438 change at the I2C device which the third party I2C drivers did
439 not initiate. I2C platform drivers may use this API within
|
| /docs/source.android.com/en/security/bulletin/ |
| 2016-08-01.html | [all...] |
| /external/kernel-headers/original/uapi/linux/ |
| cdrom.h | 3 * General header file for linux CD-ROM drivers
21 * device drivers that actually talk to the drives. There may still be
37 * can be found at: ftp://ftp.gwdg.de/pub/linux/cdrom/drivers/cm206/
50 * all the various cdrom drivers. For the CD-ROM ioctls, we
116 * They _will_ be adopted by all CD-ROM drivers, when all the CD-ROM
117 * drivers are eventually ported to the uniform CD-ROM driver interface.
|
| /external/libdrm/man/ |
| drm-memory.xml | 61 <para>Almost all in-kernel DRM hardware drivers support an API called
118 pitch (or stride) of the new buffer. Most drivers use 32bit or 64bit
181 different drivers. Gem is designed to manage graphics memory,
192 provides many functions that are shared between many drivers, but
196 drivers that use gem.</para>
216 the overhead. Newer kernel drivers also support the
|
| /external/ltp/testcases/kernel/device-drivers/v4l/user_space/doc/spec/ |
| x6570.htm | 117 capturing and overlay. This must be supported by all drivers capable
118 of simultaneous capturing and overlay. Optionally these drivers may
513 >. Drivers may have to choose
858 this is the last rectangle. Drivers ignore this field, it cannot be
998 backup routines to be compatible with all drivers, which is
1001 each logical stream. Hence as a complexity trade-off drivers
|
| /external/mesa3d/docs/relnotes/ |
| 9.2.html | 28 Some drivers don't support all the features required in OpenGL 3.1. OpenGL
45 Note: some of the new features are only available with certain drivers.
49 <li>GL_ARB_shading_language_420pack in all drivers that support GLSL 1.30.</li>
55 <li>GL_EXT_discard_framebuffer in all OpenGL ES (all versions) drivers</li>
58 <li>OSMesa interface for gallium llvmpipe/softpipe drivers</li>
218 <li>GL_EXT_separate_shader_objects has been removed from all Gallium drivers,
|
| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/sysroot/usr/include/linux/ |
| cdrom.h | 3 * General header file for linux CD-ROM drivers
21 * device drivers that actually talk to the drives. There may still be
37 * can be found at: ftp://ftp.gwdg.de/pub/linux/cdrom/drivers/cm206/
50 * all the various cdrom drivers. For the CD-ROM ioctls, we
116 * They _will_ be adopted by all CD-ROM drivers, when all the CD-ROM
117 * drivers are eventually ported to the uniform CD-ROM driver interface.
|
| /external/wpa_supplicant_8/wpa_supplicant/ |
| ChangeLog | 292 * extended P2P and GAS query operations to support drivers that have
618 frames (only with drivers using wpa_supplicant AP mode SME/MLME)
[all...] |
| Android.mk | 65 INCLUDES += $(LOCAL_PATH)/src/drivers
361 include $(LOCAL_PATH)/src/drivers/drivers.mk
1537 OBJS += src/drivers/driver_common.c
1550 OBJS_priv += $(OBJS_d) src/drivers/drivers.c
1562 OBJS += src/drivers/driver_privsep.c
1565 OBJS += $(OBJS_d) src/drivers/drivers.c
1571 OBJS += src/drivers/ndis_events.
[all...] |
| /docs/source.android.com/ja/security/bulletin/ |
| 2016-10-01.html | 1030 * ????????????????????????????? <a href="https://developers.google.com/android/nexus/drivers">Google ?????? ???</a>??????? Nexus ????????? ?????????????
[all...] |
| /docs/source.android.com/ko/security/bulletin/ |
| 2016-10-01.html | 1175 <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>?? ???? Nexus ??? ?? ????
[all...] |
| 2016-05-01.html | 468 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
509 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
563 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
776 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
810 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
844 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
891 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
1041 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
1073 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>??
1184 <p>* ? ??? ???? ?? ??? AOSP? ???? ?? ????. ????? <a href="https://developers.google.com/android/nexus/drivers">Google ??? ???</a>?
[all...] |
| /docs/source.android.com/ru/security/bulletin/ |
| 2016-10-01.html | [all...] |
| /docs/source.android.com/zh-cn/security/bulletin/ |
| 2016-10-01.html | 1022 * ????????????????<a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>???? Nexus ????????????????????
1092 * ????????????????<a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>???? Nexus ????????????????????
1146 * ????????????????<a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>???? Nexus ????????????????????
[all...] |
| /docs/source.android.com/zh-tw/security/bulletin/ |
| 2016-10-01.html | 1026 <p>* ???????????????????????? Nexus ??????????????????? <a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>?????????
1094 <p>* ???????????????????????? Nexus ??????????????????? <a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>?????????
1148 <p>* ???????????????????????? Nexus ??????????????????? <a href="https://developers.google.com/android/nexus/drivers">Google Developers ??</a>?????????
[all...] |
| /device/linaro/bootloader/edk2/MdeModulePkg/Bus/I2c/I2cDxe/ |
| I2cBus.c | 184 drivers. It will also be NULL for a bus drivers
344 ControllerHandle. Drivers will typically use the device path attached to
362 parameter is ignored by device drivers, and is optional for bus
363 drivers. For bus drivers, if this parameter is not NULL, then
533 parameter is ignored by device drivers, and is optional for bus
534 drivers. For a bus driver, if this parameter is NULL, then handles
[all...] |
