ATI Mobility Radeon X1350

The ATI Mobility Radeon X1350 is an end-of-life AMD mobile GPU built on the M62 chip using the Ultra-Threaded SE architecture. It belongs to the M6x (Mobility X1) generation, with UMC as the foundry on a 90 nm process. The die size is 100 mm², containing 105 million transistors for a listed transistor density of 1.1M / mm². The database entry has no benchmark entries and an average benchmark score of zero; its percentileVsAllGpus is 50, meaning it sits at the median of the database’s GPU population, though no score is attached to that percentile. Its predecessor is the M5x and its successor is the M7x.

Who Should Consider It

There are no recorded benchmark scores, so a resolution/settings recommendation cannot be grounded in measured results. Instead, the fixed specifications define the practical range. The X1350 has 128 MB of DDR2 memory, a 64-bit memory path, 4 TMUs, and 4 ROPs, with a pixel fill rate of 1.676 GPixel/s and a texture fill rate of 1.676 GTexel/s. That is a low-capacity, low-bandwidth configuration. Users should consider this part only for legacy DirectX 9-era software, because the API support is DirectX 9.0c (9_3) and OpenGL 2.1, with no Vulkan listed.

Low resolutions and low detail settings are the appropriate operating range. The 128 MB frame buffer limits how much pixel, depth, and texture data can be stored, and the 6.272 GB/s memory bandwidth restricts how quickly that data can be moved through the 4 TMUs and 4 ROPs. The 50th percentile database position suggests the X1350 was not at the very bottom of the historical GPU population, but with no actual benchmark score, that percentile should not be translated into a specific framerate. This is not a high-resolution or high-fidelity part; it is a constrained legacy mobile GPU.

Memory Subsystem

The memory subsystem is fully specified. The X1350 uses 128 MB of DDR2 memory on a 64-bit bus, with a bandwidth of 6.272 GB/s. The memory clock is 392 MHz, and the effective data rate is listed as 784 Mbps. The listed bandwidth is consistent with that bus width and effective data rate.

For high resolutions, the constraints are immediate. A 128 MB frame buffer can only hold a limited amount of color, depth, and texture data per frame. As resolution increases, the memory required per frame increases, and all of that data competes for the same 128 MB. The 64-bit bus further limits transfer throughput. At 6.272 GB/s, the memory path must serve texture fetches, pixel writes, and display reads through only 4 TMUs and 4 ROPs. The effective data rate of 784 Mbps is the per-pin data rate, and the bus width determines how many pins are transferring data at once. The result is a memory subsystem that will hit its ceiling before the shading resources are likely to become the main bottleneck.

How It Compares

The nearestRivals field is empty. This dataset provides no named rival, no rival scores, and no deltaPct values, so there is no direct head-to-head comparison available. The only placement metric is percentileVsAllGpus, listed as 50, which places the X1350 at the midpoint of the database’s GPU list. However, the benchmark array is empty and the average benchmark score is zero, so that percentile is a database position rather than a measured performance margin.

In terms of product lineage, the predecessor is the M5x and the successor is the M7x. This shows that the X1350 belongs to the M6x generation, but no performance deltas between those generations are provided. Without nearest rivals, any statement such as “ahead of” or “behind” a specific GPU would be unsupported by the data.

FAQ

Q: What APIs are supported?

A: DirectX 9.0c (9_3) and OpenGL 2.1. Vulkan is not listed in the data.

Q: What is the memory configuration?

A: 128 MB DDR2 memory on a 64-bit bus, with 6.272 GB/s bandwidth. The memory clock is 392 MHz with an effective data rate of 784 Mbps.

Q: What are the fill rates?

A: The pixel fill rate is 1.676 GPixel/s and the texture fill rate is 1.676 GTexel/s, based on 4 ROPs and 4 TMUs.

Q: When was it released and is it still in production?

A: The release date is 2006-09-17. The production status is listed as end-of-life.

Q: Does it have ray tracing or tensor cores?

A: No RT core count and no tensor core count are listed, so no ray tracing or tensor-accelerated feature set is specified in the data.

Q: What host interface does it use?

A: It uses PCIe 1.0 x16.

Ray Tracing and Feature Set

The data lists no rtCores and no tensorCores. Because both fields are null, the X1350 cannot be described as having ray tracing hardware or tensor-core acceleration. The shading unit count is also not listed. The feature set is instead defined by the Ultra-Threaded SE architecture, the 4 TMUs, the 4 ROPs, and the resulting fill rates of 1.676 GPixel/s and 1.676 GTexel/s.

On the API side, DirectX 9.0c (9_3) and OpenGL 2.1 are the only supported APIs. Vulkan is null. This places the feature set inside the DirectX 9 generation, with no listed path to modern API features. Ray tracing and tensor work require hardware categories that are simply not present in the dataset.

Power and Cooling

No TDP is listed. There is no suggested PSU rating, no power connector specification, no slot width, and no dimensions listed. The X1350 is a Mobility part from the M6x (Mobility X1) generation, so it belongs in a notebook environment rather than a desktop with a separate PSU.

The only process-related details available are the 90 nm UMC process, the 105 million transistor count, and the 100 mm² die size. No thermal or electrical limits are tied to those details in the data. As a result, power draw and cooling demand cannot be quantified from the dataset. Connector requirements are absent, and the only interface listed is PCIe 1.0 x16, which is a host bus rather than a power input.