React Compatibility Checker

The pre-sales question that otherwise costs an email round-trip per customer — and the one where a vague answer causes a returned board six weeks later. Pick two things, get a straight answer with the caveats attached.

Supported

KLV-7000 works with Linux 6.x.

Requires driver ≥ 3.4

Product \ PlatformLinux 6.xZephyrFreeRTOSWindowsBare metal
KLV-7000
KLV-5000
KLV-3000
SupportedPartial supportNot supportedUntested

Installation

npx shadcn@latest add "https://kelvinui.com/registry/compatibility-checker.json"

Props

PropTypeDescription
products{ id, label }[]Rows of the matrix
platforms{ id, label }[]Columns of the matrix
entriesCompatEntry[]{ productId, platformId, status, note?, requires? }
productLabelstringAxis label (default "Product")
platformLabelstringAxis label (default "Platform")
cta{ label, href }Shown for unsupported / untested combinations

Four states, and why untested must exist

status is yes, partial, no, or untested. That fourth state carries most of the value: a missing entry resolves to untested, never to yes. Silently defaulting to supported is how a customer ends up designing in a part that was never validated on their platform.

partial requires a note. Partial support with no explanation is worse than no answer — it tells someone there is a limitation without telling them whether it affects them. The demo's FreeRTOS entry says exactly what is missing and what it costs: no DMA offload, roughly 40% of the Linux throughput.

requires is the other field that prevents support tickets. Supported and supported-on-driver-3.4-or-later are different claims, and the customer running 3.1 needs the second one.

Selecting a cell in the full matrix updates the answer panel, so the component works both as a targeted lookup and as the complete support table people will screenshot for a design review.

New components every week

Get the week's new Kelvin UI components and templates in one short email. No spam, unsubscribe anytime.