BSP Tracker / BSP Status / Allwinner
Allwinner T507 / T527
Boots and runs on mainline, but you lose the entire video engine — no decode, no encode — plus camera and ISP. T507 exists precisely to route out the camera and LCD pins that mainline does not drive. If your product needs video or a camera, you are on the Tina 5.15 BSP.
Mainline instead of the vendor BSP
Can you ship mainline instead, and what exactly do you lose if you do?
Mainline, with named losses
| Block | IP | Upstream | Detail |
|---|---|---|---|
| GPU | Mali-G31 / G57 | upstream | allwinner,sun50i-h616-mali and allwinner,sun55i-a523-mali; panfrost. |
| VPU decode | Allwinner Video Engine (cedrus) | missing | The cedrus compatible list stops at sun50i-h6. No H616, no sun55i. |
| VPU encode | Video Engine | missing | No upstream encoder support. |
| NPU | T527 NPU (T507 has none) | missing | No upstream NPU driver for sun55i. |
| ISP | CSI / ISP | missing | No upstream H616 or A523 camera pipeline. |
Vendor BSP
Repository. https://gitlab.com/tina5.0_aiot (Tina SDK; no browsable vendor git)
Newest branch that actually exists. Tina 5.0_AIOT, tracking Linux 5.15.
Cadence. Allwinner runs no public git server with release branches. The SDK ships as a repo-manifest tree and archive downloads; board vendors overlay their own forks. Kernel choices are 5.10 or 5.15.
Silicon longevity
The vendor publishes no commitment. Allwinner publishes no longevity programme. The T507 page markets it as industrial and automotive but commits to nothing. The 10-year figures you will find come from module makers (Forlinx, MYIR), not from Allwinner. A T527 news post mentions a ten-year figure in Chinese, but it refers to service life, not guaranteed supply.
Yocto
Layer. meta-sunxi. No branch for the current Yocto LTS.
No wrynose branch. Community layer with no Allwinner involvement; Allwinner ships its own meta-tina instead.
Hardware you can buy
Evaluate on. Forlinx OKT507-C, MYIR MYD-LT527, Avaota A1 (SBC)
Production modules.
- FETT507-C SoM — Forlinx
- FET527N-C SoM — Forlinx
- MYC-LT527 CPU module — MYIR
Notes
T507 is the H616 die with extra pins routed out. Which kernel the T507 BSP actually ships was not verified — the Tina evidence comes from the T527 SDK.
What to do about it
Allwinner T507 / T527: upstream fixes stop December 2026. That leaves 5 months. After that date the kernel this BSP is based on receives no further security fixes from upstream, and maintaining it becomes your team’s responsibility.
There are three options:
- Backport the fixes yourself. Your team maintains a kernel that nobody else maintains: tracking each CVE, applying the patch to a tree that has diverged from upstream, and testing the result, for as long as the product ships.
- Move to the vendor’s newer BSP. This gives you a few more years of upstream fixes, and it costs a second bring-up: a new kernel, your patches forward-ported, drivers re-validated, and the product re-tested.
- Move to mainline. Mainline supports part of this SoC. The blocks marked above are the ones a migration has to solve or replace. It is the only option that does not have to be repeated when the next vendor kernel reaches end of life.
All three are engineering work, and all three are work we do: reading vendor kernel trees, checking what mainline actually supports, and moving products from one to the other. This page is built from the same work.
Get the updates
An email when a kernel series reaches end of life, a board row changes, or a layer picks up a release branch. Nothing else.
RSS