Board Support Matrix

Board Support Matrix

Status date: 2026-07-18

How to read this page

Status	Meaning
implemented	Detection, pin map and a selectable backend exist; at least local build evidence is recorded.
alias	A documented compatible board/carrier reuses an existing map/backend.
limited	Code exists, but hardware validation or capabilities such as pull/alt/PWM/expander access are incomplete.
carrier-only	The module has no fixed user header; support belongs to one exact carrier/development kit.
base-covered	The product uses an already supported base board and needs no independent pin map.
blocked	Authoritative mapping, exact carrier/DTS or backend evidence is missing.
deferred	The product is known but has no stable library target policy yet.
needs-review	The product exists but the two GPIO repositories still need an explicit support decision.
out-of-scope	This Pi-style Linux header library is not the correct interface for the product.

The normalized Banana Pi catalog has 110 products: 14 implemented, 9 alias, 19 limited, 6 carrier-only, 3 base-covered, 14 blocked, 9 deferred, 5 needs-review and 31 out-of-scope. Customer-private boards are excluded.

Code-backed families

The repository contains Banana Pi model paths for these major families:

• Legacy Allwinner: M1/M1 Plus/R1, M2, M2 Plus variants, M2 Ultra/Berry, M2 Magic, M2 Zero/P2 Zero, M3, M64.
• Newer Allwinner: M4 Berry and M4 Zero (H618; hardware PWM remains limited).
• Amlogic: M2S, CM4IO carrier, M5 and M2 Pro.
• SpacemiT K1: F3 and CM6 IO carrier.
• Renesas RZ/V2N: AI2N carrier path.
• Rockchip: R2 Pro, M5 Pro/CM5 Pro IO, M7, W3, AIM7, M4 Super, M1 Super, Forge1 and P2 Pro.
• Realtek/Synaptics/Sunplus: W2, M4, M6, F2S, F2P and F4.
• MediaTek: R2, R3, R4, R4 Lite, R4 Pro, R64.

This list says a code path exists. Read the per-board row in the porting plan for capability and validation limits.

Current software-startable work

1. BPI-SM10 — official 40-pin table/schematic and exact local K3 DTS exist; finish signal-to-controller mapping and backend work.
2. BPI-CanMV-K230D Zero — official 40-pin table, schematic and SDK exist; derive Linux gpiochip/offset and implement without guessing runtime numbering.

Hardware-validation work

BPI-F4 now has a source-backed SP7350 backend, four detection aliases and a 20-line terminal-table map. It remains limited: physical numbering means official terminal-table row 1-29, pull is a no-op, I2C/SPI nodes are provisional, and exact production DTS/gpioinfo/digital-I/O logs are still required.

Still blocked by exact internal evidence

BPI-M2C, BPI-F2, BPI-F5, BPI-2K0300, BPI-CM2+CM4IO, BPI-CM5+CM4IO, RK3588 Stamp-hole/Gold-finger carriers, BPI-S64 Core kit and BPI-AI2H carrier require an exact board package or runtime evidence.

Scope decisions

• BPI-LM7 is covered through the W3 development kit; only exact LM7+W3 detection evidence is needed.
• BPI-R2 Mini and BPI-R3 Mini have no Pi-style library target under the current evidence.
• K3 Pico-ITX, OpenWrt One, BPI-R4 Mini, BPI-5202 and BPI-2K3000 require an explicit connector/library policy before support is promised.

Never infer support from the SoC name, physical dimensions or a sibling-board DTS.