| /frameworks/rs/ |
| D | Android.mk | 18 driver/rsdAllocation.cpp \
19 driver/rsdBcc.cpp \
20 driver/rsdCore.cpp \
21 driver/rsdFrameBuffer.cpp \
22 driver/rsdFrameBufferObj.cpp \
23 driver/rsdGL.cpp \
24 driver/rsdMesh.cpp \
25 driver/rsdMeshObj.cpp \
26 driver/rsdPath.cpp \
27 driver/rsdProgram.cpp \
[all …]
|
| /frameworks/base/docs/html/tools/extras/ |
| D | oem-usb.jd | 27 to test your applications, then you need to install the appropriate USB driver. This document
29 where you can download the appropriate USB driver for your device. However, this list is
32 <p>If you're developing on Mac OS X or Linux, then you probably don't need to install a USB driver.
38 the <a href="{@docRoot}sdk/win-usb.html">Google USB Driver</a>, instead of an OEM driver. The Galaxy
39 Nexus driver, however, is distributed by <a
46 <p>First, find the appropriate driver for your device from the <a href="#Drivers">OEM drivers</a>
49 <p>Once you've downloaded your USB driver, follow the instructions below to install or upgrade the
50 driver, based on your version of Windows and whether you're installing for the first time
51 or upgrading an existing driver.</p>
53 <p class="note"><strong>Tip:</strong> When you finish the USB driver installation,
[all …]
|
| /frameworks/av/media/libmediaplayerservice/nuplayer/ |
| D | NuPlayer.cpp | 174 void NuPlayer::setDriver(const wp<NuPlayerDriver> &driver) { in setDriver() argument
175 mDriver = driver; in setDriver()
330 sp<NuPlayerDriver> driver = mDriver.promote(); in onMessageReceived() local
331 if (driver != NULL) { in onMessageReceived()
332 driver->notifySetDataSourceCompleted(OK); in onMessageReceived()
395 sp<NuPlayerDriver> driver = mDriver.promote(); in onMessageReceived() local
396 if (driver != NULL) { in onMessageReceived()
397 driver->notifyDuration(durationUs); in onMessageReceived()
759 sp<NuPlayerDriver> driver = mDriver.promote(); in onMessageReceived() local
760 if (driver != NULL) { in onMessageReceived()
[all …]
|
| D | NuPlayer.h | 36 void setDriver(const wp<NuPlayerDriver> &driver);
|
| /frameworks/support/v8/renderscript/rs_support/ |
| D | Android.mk | 104 driver/rsdAllocation.cpp \
105 driver/rsdBcc.cpp \
106 driver/rsdCore.cpp \
107 driver/rsdRuntimeStubs.cpp \
108 driver/rsdSampler.cpp \
109 driver/rsdScriptGroup.cpp \
|
| /frameworks/base/core/java/android/database/sqlite/ |
| D | SQLiteCursor.java | 78 public SQLiteCursor(SQLiteDatabase db, SQLiteCursorDriver driver, in SQLiteCursor() argument
80 this(driver, editTable, query); in SQLiteCursor()
93 public SQLiteCursor(SQLiteCursorDriver driver, String editTable, SQLiteQuery query) { in SQLiteCursor() argument
102 mDriver = driver; in SQLiteCursor()
|
| D | SQLiteDatabase.java | 1312 SQLiteCursorDriver driver = new SQLiteDirectCursorDriver(this, sql, editTable, in rawQueryWithFactory() local
1314 return driver.query(cursorFactory != null ? cursorFactory : mCursorFactory, in rawQueryWithFactory()
|
| /frameworks/native/opengl/specs/ |
| D | 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
|
| /frameworks/native/opengl/libs/EGL/ |
| D | Loader.h | 61 status_t close(void* driver);
|
| D | Loader.cpp | 198 status_t Loader::close(void* driver) in close() argument
200 driver_t* hnd = (driver_t*)driver; in close()
|
| /frameworks/compile/libbcc/tests/debuginfo/ |
| D | README | 11 by the libbcc driver utility (bcc) on the host through GDB. The debugger
39 By default, llvm-lit will use the clang and bcc driver built in the android
|
| D | build_test_apk.sh | 104 --driver)
|
| /frameworks/base/docs/html/sdk/ |
| D | RELEASENOTES.jd | 192 driver.
195 driver that you can install. The driver is compatible with both 32- and 64-bit
196 versions of Windows XP and Vista. The driver represents an upgrade from the USB
197 driver included in previous Android SDKs, although installing the new driver is
200 <p>If you installed the USB driver from a previous SDK release and it is working
201 properly, you do not need to upgrade to the new driver. However, we recommend
202 upgrading if you have had any problems with the older driver or simply want
205 <p>For driver installation or
299 Windows versions of the SDK, a custom USB driver is included that supports the
302 to obtain a USB driver, especially if you have an SDK add-on that defines
[all …]
|
| D | win-usb.jd | 211 <p>The Galaxy Nexus driver is distributed by <a
217 driver. To start developing with your device, read
224 component. You need the driver only if you are developing on Windows and
229 <img src="{@docRoot}images/developing/sdk-usb-driver.png" alt="" />
241 helps you keep the driver up to date by notifying you when your current driver is out of date.
247 <li>Proceed to install the package. When done, the driver files are
|
| /frameworks/native/opengl/tests/testViewport/ |
| D | README | 25 being ignored by the OpenGL driver.
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/driver-common/SRC/ |
| D | DriverRS.java.template | 22 // This is the renderer for the driver
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/driver-int-param/ |
| D | DriverRS.java.template | 22 // This is the renderer for the driver
|
| /frameworks/compile/libbcc/tests/debuginfo/host-tests/ |
| D | lit.cfg | 57 lit.note('using bcc driver: %r' % config.bcc_driver)
|
| /frameworks/compile/slang/ |
| D | llvm-rs-cc.cpp | 53 using clang::driver::options::DriverOption;
|
| D | README.rst | 29 llvm-rs-cc is a driver on top of libslang. The architecture of
|
| /frameworks/base/docs/html/tools/devices/ |
| D | emulator.jd | 342 your system such as VirtualBox or VMWare, you may need to unload the driver for that virtual machine
387 <p>To install the virtualization driver:</p>
395 <li>After installation completes, confirm that the virtualization driver is operating correctly by
432 <p>You can stop using the virtualization driver by uninstalling it. Re-run the installer or use
485 <p>You can stop using the virtualization kernel driver by uninstalling it. Before removing it, shut
486 down any running x86 emulators. To unload the virtualization kernel driver, run the following
501 <li>If you use another virtualization technology in your Linux platform, unload its kernel driver
502 before running the x86 emulator. For example, the VirtualBox driver program is {@code vboxdrv}.</li>
|
| /frameworks/base/docs/html/training/basics/firstapp/ |
| D | running-app.jd | 108 If you're developing on Windows, you might need to install the appropriate USB driver for your
|
| /frameworks/base/docs/html/tools/ |
| D | device.jd | 75 <li>If you're developing on Windows, you need to install a USB driver for adb. For an
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-3.1-highlights.jd | 133 driver is needed, in most cases. When multiple devices are connected, users can
|
| /frameworks/base/docs/html/training/articles/ |
| D | smp.jd | 142 memory-mapped device driver I/O for the moment.)</p>
356 <p>(In a kernel device driver that accesses memory-mapped I/O locations, it may
|