/third_party/mesa3d/src/panfrost/lib/tests/ |
D | test-blend.c | 34 uint32_t hardware; member 52 .hardware = 0xF0122122 69 .hardware = 0xF0503503 87 .hardware = 0xF0932932 /* equivalently 0xF0923923 */ 104 .hardware = 0xF0523523 122 .hardware = 0xF09B29B2 /* equivalently 0xF09A39A3 */ 139 .hardware = 0xF052B52b /* equivalently 0xF05A35A3 */ 155 .hardware = 0xF0231231 /* equivalently 0xF0321321 */ 167 .hardware = 0x30122122 183 .hardware = 0xA0231231 /* equivalently 0xA0321321 */ [all …]
|
/third_party/mesa3d/bin/ |
D | update-android-headers.sh | 10 if [ ! -d platform-hardware-libhardware ]; then 12 …lone --depth 1 https://android.googlesource.com/platform/hardware/libhardware platform-hardware-li… 43 mkdir ${dest}/hardware 44 cp -av platform-hardware-libhardware/include/hardware/{hardware,gralloc,gralloc1,fb}.h ${dest}/hard… 45 cp -av platform-frameworks-native/vulkan/include/hardware/hwvulkan.h ${dest}/hardware
|
/third_party/skia/tools/skpbench/ |
D | skpbench.py | 226 def execute(self, hardware): argument 227 hardware.sanity_check() 248 hardware.sanity_check() 250 elif hardware.filter_line(message.value): 254 hardware.sanity_check() 298 def run_benchmarks(configs, srcs, hardware, resultsfile=None): argument 305 with hardware: 306 SKPBench.run_warmup(hardware.warmup_time, configs[0]) 314 skpbench.execute(hardware) 337 hardware.print_debug_diagnostics() [all …]
|
/third_party/flutter/skia/tools/skpbench/ |
D | skpbench.py | 204 def execute(self, hardware): argument 205 hardware.sanity_check() 226 hardware.sanity_check() 228 elif hardware.filter_line(message.value): 232 hardware.sanity_check() 276 def run_benchmarks(configs, srcs, hardware, resultsfile=None): argument 283 with hardware: 284 SKPBench.run_warmup(hardware.warmup_time, configs[0]) 292 skpbench.execute(hardware) 315 hardware.print_debug_diagnostics() [all …]
|
/third_party/mesa3d/src/egl/drivers/dri2/ |
D | platform_android_mapper.cpp | 36 using aidl::android::hardware::graphics::common::ChromaSiting; 37 using aidl::android::hardware::graphics::common::Dataspace; 38 using aidl::android::hardware::graphics::common::ExtendableType; 39 using aidl::android::hardware::graphics::common::PlaneLayout; 40 using aidl::android::hardware::graphics::common::PlaneLayoutComponent; 41 using aidl::android::hardware::graphics::common::PlaneLayoutComponentType; 42 using android::hardware::graphics::common::V1_2::BufferUsage; 43 using android::hardware::graphics::mapper::V4_0::Error; 44 using android::hardware::graphics::mapper::V4_0::IMapper; 45 using android::hardware::hidl_handle; [all …]
|
/third_party/mesa3d/ohos/pkgconfig_template/ |
D | gbm.pc | 2 libdir=${ohos_project_dir}/device/rockchip/hardware/gpu 3 includedir=${ohos_project_dir}/device/rockchip/hardware/gpu/include 9 Cflags: -I${ohos_project_dir}/device/rockchip/hardware/gpu/include
|
/third_party/skia/third_party/externals/swiftshader/src/System/ |
D | GrallocAndroid.cpp | 22 using V3Error = android::hardware::graphics::mapper::V3_0::Error; 23 using V3Mapper = android::hardware::graphics::mapper::V3_0::IMapper; 24 using android::hardware::hidl_handle; 27 using V4Error = android::hardware::graphics::mapper::V4_0::Error; 28 using V4Mapper = android::hardware::graphics::mapper::V4_0::IMapper; 29 using android::hardware::hidl_handle;
|
D | GrallocAndroid.hpp | 53 android::sp<android::hardware::graphics::mapper::V3_0::IMapper> m_gralloc3_mapper; 56 android::sp<android::hardware::graphics::mapper::V4_0::IMapper> m_gralloc4_mapper;
|
/third_party/skia/third_party/externals/swiftshader/src/Common/ |
D | GrallocAndroid.cpp | 22 using V3Error = android::hardware::graphics::mapper::V3_0::Error; 23 using V3Mapper = android::hardware::graphics::mapper::V3_0::IMapper; 24 using android::hardware::hidl_handle; 27 using V4Error = android::hardware::graphics::mapper::V4_0::Error; 28 using V4Mapper = android::hardware::graphics::mapper::V4_0::IMapper; 29 using android::hardware::hidl_handle;
|
D | GrallocAndroid.hpp | 53 android::sp<android::hardware::graphics::mapper::V3_0::IMapper> m_gralloc3_mapper; 56 android::sp<android::hardware::graphics::mapper::V4_0::IMapper> m_gralloc4_mapper;
|
/third_party/gstreamer/gstplugins_bad/sys/androidmedia/org/freedesktop/gstreamer/androidmedia/ |
D | GstAhsCallback.java | 23 import android.hardware.Sensor; 24 import android.hardware.SensorEvent; 25 import android.hardware.SensorEventListener;
|
/third_party/skia/third_party/externals/opengl-registry/extensions/INTEL/ |
D | INTEL_performance_query.txt | 48 The purpose of this extension is to expose Intel proprietary hardware 52 - number of hardware events such as number of spawned vertex shaders. In 66 different Intel hardware platforms. Performance counters are grouped 67 together into proprietary, hardware-specific, fixed sets of counters that 75 (sets of performance counters) are supported by the Intel hardware. However 76 each Intel hardware generation supports different sets of performance 77 counters. Therefore the query types between hardware generations can be 80 Intel OGL Performance Counters Specification issued per each new hardware 167 types. Different query types can be supported on different hardware 178 queryId parameter. If the given hardware platform doesn't support any [all …]
|
/third_party/openGLES/extensions/INTEL/ |
D | INTEL_performance_query.txt | 48 The purpose of this extension is to expose Intel proprietary hardware 52 - number of hardware events such as number of spawned vertex shaders. In 66 different Intel hardware platforms. Performance counters are grouped 67 together into proprietary, hardware-specific, fixed sets of counters that 75 (sets of performance counters) are supported by the Intel hardware. However 76 each Intel hardware generation supports different sets of performance 77 counters. Therefore the query types between hardware generations can be 80 Intel OGL Performance Counters Specification issued per each new hardware 167 types. Different query types can be supported on different hardware 178 queryId parameter. If the given hardware platform doesn't support any [all …]
|
/third_party/mesa3d/docs/ |
D | faq.rst | 19 1.2 Does Mesa support/use graphics hardware? 42 - Mesa is used as the core of the open-source X.org DRI hardware 47 hardware drivers. 52 is only now appearing in hardware. 54 can be changed for special needs (hardware limits are hard to 68 - There is no hardware acceleration. 72 Alternately, Mesa acts as the core for a number of OpenGL hardware 199 3.1 Rendering is slow / why isn't my graphics hardware being used? 202 If Mesa can't use its hardware accelerated drivers it falls back on one 208 sort of hardware it has detected. [all …]
|
D | macos.rst | 17 hardware-accelerated system OpenGL framework, to provide hardware acceleration 24 For native hardware, stay tuned for updates here!
|
/third_party/flutter/flutter/packages/flutter_tools/test/general.shard/android/ |
D | android_device_test.dart | 134 String hardware; 138 hardware = 'goldfish'; 145 ..writeln('[ro.hardware]: [$hardware]')..writeln( 212 String hardware; 216 hardware = 'unknown'; 222 ..writeln('[ro.hardware]: [$hardware]') 230 hardware = 'samsungexynos7420'; 238 hardware = 'goldfish'; 309 String hardware; 313 hardware = 'goldfish'; // Known emulator [all …]
|
/third_party/libinput/doc/user/ |
D | button-debouncing.rst | 18 - In the "bounce" method, libinput monitors hardware bouncing on button 20 if a user presses a button but the hardware generates a 35 libinput's debouncing is supposed to correct hardware damage or 36 substandard hardware. Debouncing also exists as an accessibility feature 40 the stack, libinput is limited to hardware debouncing.
|
/third_party/gstreamer/gstplugins_bad/sys/msdk/ |
D | gstmsdkcontext.c | 49 gboolean hardware; member 203 gst_msdk_context_open (GstMsdkContext * context, gboolean hardware, in gst_msdk_context_open() argument 211 priv->hardware = hardware; in gst_msdk_context_open() 214 msdk_open_session (hardware ? MFX_IMPL_HARDWARE_ANY : MFX_IMPL_SOFTWARE); in gst_msdk_context_open() 222 if (hardware) { in gst_msdk_context_open() 299 gst_msdk_context_new (gboolean hardware, GstMsdkContextJobType job_type) in gst_msdk_context_new() argument 303 if (obj && !gst_msdk_context_open (obj, hardware, job_type)) { in gst_msdk_context_new() 393 priv->hardware = parent_priv->hardware; in gst_msdk_context_new_with_parent()
|
/third_party/mesa3d/docs/isl/ |
D | units.rst | 16 about a surface in a canonical way that isn't dependent on hardware generation. 20 field aren't quite what is wanted by the hardware, we do the conversion when we 25 keep everything in the same units as the hardware expects but this lead to 26 unnecessary complications as the hardware evolved. One example of this 33 hardware units, everyone who ever reads :cpp:expr:`brw_mipmap_tree::qpitch` has 34 to change their interpretation based on hardware generation and whether or not 38 of the texture when we finally fill out the hardware packet. However, the 40 field much simpler because they never have to look at hardware generation or
|
/third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/MSP430/ |
D | MSP430.td | 26 "Enable 16-bit hardware multiplier">; 30 "Enable 32-bit hardware multiplier">; 34 "Enable F5 series hardware multiplier">;
|
/third_party/gstreamer/gstreamer/docs/random/ensonic/ |
D | draft-bufferpools.txt | 21 - hardware based elements like to reuse buffers as they e.g. 105 - padding: when using buffers on hardware one might need to pad the buffer on 107 - mlock: hardware that uses DMA needs buffers memory locked, if a buffer is 108 already memory locked, it can be used by other hardware based elements as is 109 - cache flushes: hardware based elements usually need to flush cpu caches when 113 other hardware elements and elements with any caps (tee, queue, capsfilter)
|
/third_party/mesa3d/src/intel/isl/ |
D | README | 16 hardware: the actual memory layout of Intel GPU surfaces and how one programs 20 match those of the hardware enum `SURFACE_FORMAT` rather than the OpenGL 25 hardware enum `SURFACE_FORMAT` does not, and therefore neither does `enum 26 isl_format`. Rather than define new pixel formats that have no hardware 54 Logical units are independent of hardware generation and are closely related 56 hardware generation and reflect the surface's layout in memory.
|
/third_party/boost/libs/predef/doc/ |
D | hardware_simd.qbk | 14 #include <boost/predef/hardware/simd.h> 36 #include <boost/predef/hardware/simd.h> 55 #include <boost/predef/hardware/simd.h> 72 #include <boost/predef/hardware/simd.h>
|
/third_party/gstreamer/gstplugins_bad/sys/d3d11/ |
D | plugin.cpp | 210 gboolean hardware; in plugin_init() local 212 g_object_get (device, "hardware", &hardware, NULL); in plugin_init() 213 if (hardware) in plugin_init()
|
/third_party/openGLES/extensions/EXT/ |
D | WGL_EXT_display_color_table.txt | 45 hardware, and to take place during vertical blanking. 117 intensities in the video output hardware. Each RGB color component is 120 Because display color tables are implemented in the output hardware, 126 only the pixels belonging to that drawable. However, hardware may be 217 wglLoadDisplayColorTableEXT. The size of hardware tables depends on the 221 The internal format of hardware tables is inaccessible. For purposes of 232 blue hardware table. The hardware table entry at that index replaces C. 235 application table and the hardware table. Each element of the hardware 245 than hardware table elements. Hardware elements are generated by
|