AMD Radeon HD 8280 Mobile IGP

The AMD Radeon HD 8280 Mobile IGP is an integrated graphics processor built on GCN 2.0, using the Kalindi chip in the Kabini Mobile generation. It is manufactured on TSMC’s 28 nm process with 1,178 million transistors in a 110 mm² die, giving a transistor density of 10.7M/mm². Its compute block contains 128 shading units, 8 texture mapping units, and 4 ROPs, with peak FP32 throughput of 115.2 GFLOPS. In the database, it is assigned a 50th percentile rank versus all GPUs and an average benchmark score of 0; the nearestRivals list is empty. Those facts frame the analysis below.

Benchmark Performance

Benchmark data for this entry is sparse. The database records an average benchmark score of 0, and the nearestRivals array contains no entries, so there are no percentage deltas to report against specific named competitors. The only positional metric is the 50th percentile rank versus all GPUs. That rank places the IGP at the midpoint of the database by position, but the zero average benchmark score means no measured benchmark points are attached to the record.

Without rival scores or deltaPct values, specification throughput is the main functional evidence. The IGP delivers 115.2 GFLOPS of FP32 compute, a texture rate of 3.600 GTexel/s, and a pixel rate of 1.800 GPixel/s. These figures describe the fixed limits of the part. The 128 shading units provide the compute foundation, while the 8 TMUs handle texture work and the 4 ROPs bound pixel output. Because the pixel rate is 1.800 GPixel/s, fill-heavy workloads will hit a relatively low ceiling. Texture-heavy scenes are similarly constrained by the 3.600 GTexel/s rate. The overall performance posture is consistent with a power-conscious IGP rather than a discrete-class graphics solution.

Power and Cooling

The IGP is rated for a 15 W TDP. It is not an add-in board: slot width is listed as IGP and the bus interface is IGP, so it draws power through the host platform rather than through a dedicated expansion slot. No power connectors are listed, and no suggested PSU figure is provided. Because this is a mobile IGP, the surrounding system is responsible for power delivery and heat removal. Display outputs are portable-device dependent, so the number and type of display connections are determined by the host device, not by the GPU itself.

Who Should Consider It

The data points toward users who need a low-power integrated graphics solution for a portable device. With 115.2 GFLOPS of FP32 throughput and a 1.800 GPixel/s pixel rate, the IGP is not positioned for high-resolution, high-detail 3D gaming. It can handle basic desktop composition, lightweight media tasks, and undemanding 3D workloads. Gaming use cases should be limited to low detail settings and lower resolutions. The 4 ROP count and 8 TMUs mean that both pixel fill and texture throughput are modest, so scenes with heavy effects or rich textures will strain the part. High-resolution output is further complicated by a memory subsystem that is system shared, meaning the IGP has no dedicated high-bandwidth frame buffer.

FAQ

Q: Does this IGP have dedicated video memory?

A: No. Memory size, memory type, and bus width are all listed as “System Shared,” and bandwidth is listed as “System Dependent.”

Q: What API support does it provide?

A: It supports DirectX 12 (12_0), OpenGL 4.6, and Vulkan 1.2.170.

Q: Does it support hardware ray tracing or tensor acceleration?

A: No. RT cores are null and tensor cores are null, so there are no dedicated ray tracing or tensor acceleration blocks.

Q: What is its power requirement?

A: It has a 15 W TDP, slot width of IGP, no power connectors, and no suggested PSU listed.

Q: Is this product still in production?

A: No. Its production status is end-of-life, with a release date of 2013-09-17.

Q: What is the FP32 performance figure?

A: The FP32 throughput is 115.2 GFLOPS.

How It Compares

The nearestRivals field is empty, so there are no named competitors with scores or deltaPct values to compare. The only rank reference in the database is the 50th percentile versus all GPUs. In terms of product lineage, the predecessor is TeraScale 3 IGP and the successor is GCN 3.0 IGP, placing the HD 8280 Mobile IGP between those IGP generations within AMD’s integrated lineup. Without rival scores, exact percentage comparisons cannot be derived from this data set.

Memory Subsystem

All memory-related fields are system shared. There is no dedicated VRAM size, no dedicated VRAM type, and no dedicated bus width. The IGP uses the host system’s memory, and bandwidth is listed as “System Dependent,” meaning the actual data rate depends on the host platform’s memory configuration. For high-resolution workloads, this is a significant constraint because frame buffers and texture data must be written to and read from shared system memory. The lack of a fixed bandwidth figure means the IGP has no guaranteed memory throughput independent of the host device. In memory-constrained situations, performance can degrade further as the CPU and GPU contend for the same resources.

Ray Tracing and Feature Set

The feature set is defined by the GCN 2.0 architecture and the integrated configuration. RT cores and tensor cores are both null, so hardware-accelerated ray tracing and tensor operations are not available. API support includes DirectX 12 (12_0), OpenGL 4.6, and Vulkan 1.2.170. This provides compatibility with modern graphics interfaces, but the IGP does not include dedicated hardware blocks for newer acceleration features. Applications that rely on conventional shader-based rendering can use the 128 shading units and 115.2 GFLOPS of FP32 compute, while hardware-dependent ray tracing effects are outside this part’s feature set.