OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:drivers
(Results
501 - 525
of
2849
) sorted by null
<<
21
22
23
24
25
26
27
28
29
30
>>
/device/linaro/bootloader/edk2/Nt32Pkg/WinNtBlockIoDxe/
DriverConfiguration.c
88
for device
drivers
, and for a bus
drivers
that wish to set
203
drivers
. It will also be NULL for a bus
drivers
that wish
285
ChildHandle - The handle of the child controller to force default configuration options on This is an optional parameter that may be NULL. It will be NULL for device
drivers
. It will also be NULL for a bus
drivers
that wish to force default configuration options for the bus controller. It will not be NULL for a bus driver that wishes to force default configuration options for one of its child controllers.
/external/kernel-headers/original/uapi/linux/
media.h
50
*
Drivers
should change it to something useful
84
* It is a responsibility of the master/bridge
drivers
to create links
110
/* It is a responsibility of the entity
drivers
to add connectors and links */
131
*
Drivers
must change to the proper subdev type before
142
* It is a responsibility of the master/bridge
drivers
to add connectors
212
* actual
drivers
that use this. When the first real driver
/external/ltp/testcases/kernel/device-drivers/v4l/user_space/doc/spec/
c5742.htm
116
write to a device. All
drivers
exchanging data with applications must
161
>) and
drivers
permitting simultaneous video capturing
173
but for simplicity
drivers
need not support switching the I/O method
215
>
Drivers
may need the CPU to copy the data, but they may also
257
Drivers
must implement one I/O method if they
315
drivers
supporting all I/O interfaces, but as much as the complex
/external/mesa3d/docs/relnotes/
3.3
145
SetDrawBuffer(). All device
drivers
will have to be updated because
189
drivers
to have anywhere from 0 to 32-bit Z buffers without
221
drivers
for examples.
225
drivers
. In fact, it should simply the code. Be careful with
232
should be implemented in software. Mesa hardware
drivers
should
244
overridden by device
drivers
to reflect the limits of that driver's
7.0.4.html
57
<li>Enabled GL_EXT_multi_draw_arrays extension in R200/R300
drivers
71
DRI
drivers
varies with the driver
7.2.html
26
Some
drivers
don't support all the features required in OpenGL 2.1.
95
DRI
drivers
varies with the driver
7.4.2.html
25
Some
drivers
don't support all the features required in OpenGL 2.1.
65
DRI
drivers
varies with the driver
/external/parameter-framework/asio-1.10.6/include/asio/ip/
basic_resolver_query.hpp
56
* <tt>c:\\windows\\system32\\
drivers
\\etc\\services</tt>. Operating systems
93
* <tt>c:\\windows\\system32\\
drivers
\\etc\\services</tt>. Operating systems
135
* <tt>c:\\windows\\system32\\
drivers
\\etc\\hosts</tt>. Remote host name
141
* <tt>c:\\windows\\system32\\
drivers
\\etc\\services</tt>. Operating systems
186
* <tt>c:\\windows\\system32\\
drivers
\\etc\\hosts</tt>. Remote host name
192
* <tt>c:\\windows\\system32\\
drivers
\\etc\\services</tt>. Operating systems
/hardware/intel/common/libva/va/
va_backend.h
438
* This structure is intended for
drivers
that implement the
447
* This structure is intended for
drivers
that implement the
456
* This structure is intended for
drivers
that implement the
480
*
drivers
. This structure is allocated from libva with
486
*
drivers
that use the DRM protocol.
505
* This structure is intended for
drivers
that implement the
/docs/source.android.com/en/security/bulletin/
2016-07-01.html
[
all
...]
/external/mesa3d/doxygen/
gallium.doc
6
new architecture for building 3D graphics
drivers
. Initially
7
supporting Mesa and Linux graphics
drivers
, Gallium3D is designed to allow
10
Compared to existing Linux graphics
drivers
, Gallium3D will:
12
- Make
drivers
smaller and simpler.
13
Current DRI
drivers
are rather complicated. They're large, contain
34
- Pipe
drivers
:
38
- Winsys
drivers
:
77
put into effect by binding them. This allows Gallium3D
drivers
to create
84
Gallium3D
drivers
rely upon. For example, memory allocation is typically a
86
the window system. Pipe
drivers
use the winsys interface to handle thes
[
all
...]
/device/google/contexthub/firmware/os/platform/stm32/
stm32.mk
37
#platform
drivers
56
#platform
drivers
for bootloader
/device/linaro/bootloader/edk2/ArmPkg/Application/LinuxLoader/
LinuxLoader.h
130
@retval EFI_SUCCESS All
drivers
have been connected
152
@retval EFI_SUCCESS All
drivers
have been connected
/device/linaro/bootloader/edk2/ArmPkg/Library/BdsLib/
BdsHelper.c
74
Connect all DXE
drivers
76
@retval EFI_SUCCESS All
drivers
have been connected
/device/linaro/bootloader/edk2/EdkCompatibilityPkg/Foundation/Core/Dxe/ArchProtocol/Runtime/
Runtime.h
31
by this driver to produce the runtime transition of runtime
drivers
from
87
Foundation to manage runtime
drivers
and events. This protocol also implies
/device/linaro/bootloader/edk2/EdkCompatibilityPkg/Foundation/Framework/Protocol/FormCallback/
FormCallback.h
21
specific
drivers
which want to export access to custom hardware storage or
70
EFI_IFR_DATA_ARRAY DataArray; // Primarily used by those who call back to their
drivers
and use HII as a repository
/device/linaro/bootloader/edk2/MdePkg/Include/Protocol/
Runtime.h
7
services to the DXE Foundation to manage runtime
drivers
and events.
107
/// Foundation to manage runtime
drivers
and events. This protocol also implies
/device/linaro/bootloader/edk2/NetworkPkg/HttpBootDxe/
HttpBootComponentName.h
59
will be NULL for device
drivers
. It will also be NULL
60
for a bus
drivers
that wish to retrieve the name of the
/device/linaro/bootloader/edk2/NetworkPkg/HttpDxe/
ComponentName.h
58
will be NULL for device
drivers
. It will also be NULL
59
for a bus
drivers
that wish to retrieve the name of the
/device/linaro/bootloader/edk2/OvmfPkg/XenBusDxe/
ComponentName.h
56
will be NULL for device
drivers
. It will also be NULL
57
for a bus
drivers
that wish to retrieve the name of the
XenBusDxe.c
161
the same for UEFI Applications, UEFI OS Loaders, and UEFI
Drivers
including
162
both device
drivers
and bus
drivers
.
211
parameter is ignored by device
drivers
, and is optional for bus
212
drivers
. For bus
drivers
, if this parameter is not NULL, then
291
parameter is ignored by device
drivers
, and is optional for bus
292
drivers
. For a bus driver, if this parameter is NULL, then handles
/device/linaro/bootloader/edk2/OvmfPkg/XenPvBlkDxe/
ComponentName.h
56
will be NULL for device
drivers
. It will also be NULL
57
for a bus
drivers
that wish to retrieve the name of the
/docs/source.android.com/en/devices/architecture/
index.html
39
implementing
drivers
.</p>
66
<p>Developing your device
drivers
is similar to developing a typical Linux
/external/ltp/testcases/kernel/device-drivers/v4l/user_space/
test_VIDIOC_QUERYCAP.c
87
/* This ioctl must be implemented by ALL
drivers
*/
139
/* VIDIOC_QUERYCAP is a mandatory command, all
drivers
shall
/external/mesa3d/docs/
download.html
78
src/mesa - sources for the main Mesa library and device
drivers
79
src/gallium - sources for Gallium and Gallium
drivers
Completed in 770 milliseconds
<<
21
22
23
24
25
26
27
28
29
30
>>