radv-xclipse-26.3.0-devel-05b3092 vs mesa_radv_xclipse

On Samsung Xclipse 920 (Samsung Galaxy S22, Samsung Galaxy S23 FE, Samsung Galaxy S24 FE, Samsung Galaxy S24+). The first driver named is compared against the second, which is the baseline.

mesa_radv_xclipse details radv-xclipse-26.3.0-devel-05b3092 details

Feature checks that differ (4)

Speed test scenes (benchmark)

The two drivers were not measured on the same set of device models. Frame times from different devices do not compare drivers, so read these numbers with that in mind.

Time to draw one frame, per scene: the average (mean) frame time of the scene's best round, which is how many frames the driver delivered; lower is faster. "Typical" beside it is the median frame, which can sit well under the average when a driver's frames come in two speeds. A pair of reports made before per-round averages were recorded is compared on the median. A scene whose rounds disagree by more than 15% is left out. A scene marked "paced" was held at that mean frame time by the driver or the display queue, together with at least one other scene of the same run; its time says how the frames were spaced, not how fast the driver rendered, so it is not compared. A scene marked "too light" took under 8 ms at the standard size (1920 by 1080) on both drivers, where the screen's frame queue spaces the frames more than the chip does; its heavier run is the one compared: the row ending in _2160p is the scene drawn at 3840 by 2160, and compute_nbody_2x is that scene with twice the particles. "Faster" and "slower" describe radv-xclipse-26.3.0-devel-05b3092 against mesa_radv_xclipse. "Picture vs stock" compares one fixed frame per scene as a coarse colour grid (0 is identical, above 40 is a different picture); it finds a scene that was not drawn. Where both reports carry the finer 64x36 grid, the second figure is how many of its 2,304 cells differ by more than 4 of 255, and "worst" is the largest single cell; this is what finds a small rendering error in a picture that otherwise matches. A row marked 16x9 comes from a report made before the finer grid existed. "Starts" is how many of a scene's process starts reached a measured round. A GPU clock marked "not comparable" differed by more than 5% of the device's maximum between the two timings.

Technical differences (Vulkan)

Extensions only in radv-xclipse-26.3.0-devel-05b3092 (15)

• VK_AMD_texture_gather_bias_lod
• VK_EXT_device_generated_commands
• VK_EXT_external_memory_host
• VK_EXT_fragment_shader_interlock
• VK_EXT_image_drm_format_modifier
• VK_EXT_mesh_shader
• VK_EXT_pipeline_library_group_handles
• VK_KHR_acceleration_structure
• VK_KHR_ray_query
• VK_KHR_ray_tracing_maintenance1
• VK_KHR_ray_tracing_pipeline
• VK_KHR_ray_tracing_position_fetch
• VK_NV_geometry_shader_passthrough
• VK_NV_viewport_array2
• VK_NV_viewport_swizzle

Extensions only in mesa_radv_xclipse (11)

• VK_EXT_cooperative_matrix_maintenance1
• VK_EXT_image_compression_control_swapchain
• VK_EXT_pipeline_protected_access
• VK_EXT_present_timing
• VK_KHR_cooperative_matrix
• VK_KHR_present_id
• VK_KHR_present_id2
• VK_KHR_present_wait
• VK_KHR_present_wait2
• VK_KHR_swapchain_maintenance1
• VK_KHR_unified_image_layouts

Core features that differ (2)

protectedMemory Vulkan 1.1	pass to unsupported
pipelineProtectedAccess Vulkan 1.4	pass to unsupported

Limits that differ (9)

Limit	mesa_radv_xclipse	radv-xclipse-26.3.0-devel-05b3092
framebufferColorSampleCounts	7	15
framebufferDepthSampleCounts	7	15
framebufferStencilSampleCounts	7	15
framebufferNoAttachmentsSampleCounts	7	15
sampledImageColorSampleCounts	7	15
sampledImageIntegerSampleCounts	7	15
sampledImageDepthSampleCounts	7	15
sampledImageStencilSampleCounts	7	15
storageImageSampleCounts	7	15

Formats supported by only one driver (0 gained, 1 lost)

Only in radv-xclipse-26.3.0-devel-05b3092:

• None

Only in mesa_radv_xclipse:

• G10X6_B10X6R10X6_2PLANE_422_UNORM_3PACK16