Driver & firmware fundamentals

What this catalog knows — and what it cannot prove

Understand exact IDs, qualified matches, class context, source dates and the limits of hardware compatibility claims.

Evidence has different strengths

An exact curated ID identifies a source-backed device or family in the stated bus context. A missing subsystem qualifier is a conditional match. A bound driver name or device class gives contextual profiles, not an exact model. If several profiles remain plausible, the tool keeps them separate and does not silently choose a winner.

Review dates are editorial

An immutable kernel-source link records the table or implementation inspected. The review date is the day the source was checked, not a successful test on physical hardware and not the oldest supported kernel. Distribution backports, kernel configuration and firmware revisions can differ. Runtime evidence from your local machine remains necessary.

Unknown hardware stays unknown

The parser accepts more devices than the curated catalog can explain. An unknown result still gives the numeric identity and reported binding when present, but does not invent a firmware package or compatibility score. Cross-links lead to documented diagnostic guides. A no-match result is a coverage limit, not a health certificate or proof of unsupported Linux hardware.

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.

Use the local identification tool