Group: Hardware/Components/SOCs
Contents
Introduction
This page has information about various system on a chip.
Note that some information automatically applies to devices using systems on a chip mentioned here and some don't.
For instance:
- If a system on a chip has a GPU, devices using that system on a chip will also get this GPU (unless there are versions without GPU, and that is not mentioned here).
- If a system on a chip supports WiFi, PCIe, or other busses, and that the device didn't connect that to connectors, users won't be able to use these busses.
- If a system on a chip can boot with free software, it doesn't mean that all the devices using it can. Some devices use restricted boot in ways that can't be disabled unless security flaws are found in the hardware.
Though:
- That information can be used to rule out devices. For instance if a device has a system on a chip that doesn't boot with free software, it most likely can't boot with free software.
- It can be used to see which chips can be used to produce devices that boot with free software or could somehow gain the RYF certification.
Information
Vendor | Product | CPU architecture | GPU | RYF issues | Linux upstream status | Bootloader upstream status | Busses for WiFi | Companion chips | Documentation | Minumum quantities | Available until |
---|---|---|---|---|---|---|---|---|---|---|---|
Rockchip | RK3399 | arm64 |
|
|
? | ? |
|
? | ? | ? | ? |
Amlogic | S805X | Aarch64 | Mali-450 (Lima) |
|
TODO: Look at status | TODO: Look at status | |||||
Amlogic | S905X | Aarch64 |
|
TODO: Look at status | TODO: Look at status | ||||||
Texas instruments | DM370(like omap3 but higher speed) | ARMv7 | Powervr |
|
Good |
|
|
? | ? | ? | ? |
Texas instruments | omap4 | ARMv7 | Powervr |
|
Probably good |
|
|
? | ? | ? | ? |
Allwinner Tech | A31 | ARMv7 | Powervr |
|
very few missing drivers | ? |
|
? | ? | ? | ? |
Allwinner Tech |
|
ARMv7 | Mali |
|
very few missing drivers | Good |
|
? | ? | ? | ? |
Samsung | Exynos 3 Single -> Exynos 5 dual | armv7 | Mali |
|
? | ? |
|
? | ? | ? | ? |
Samsung | Exynos 5 Octa | ? | Powervr |
|
? | ? |
|
? | ? | ? | ? |
Ingenic | JZ4760 | ? | Vivante GC200 | ? | ? |
|
|
? |
|
1 | ? |
NXP | I.MX 25 | ARM 32bit (which one?) | No GPU | No known issues | Mostly complete | Mostly complete? (bareobx?, u-boot?) |
|
? | ? | ? | |
NXP | I.MX 50 | ARMv7? | ? |
Issues:
TODO: |
Mostly complete | Mostly complete? (bareobx?, u-boot?) |
|
? | ? | ? | |
NXP | I.MX 51 | ARMv7 | Adreno |
Issues:
Optional: |
Mostly complete | Mostly complete? (bareobx?, u-boot?) |
|
? | ? | ? | |
NXP |
|
ARMv7 | Vivante |
Issues:
Optional: |
Mostly complete | Mostly complete? (bareobx?, u-boot?) |
|
? | ? | ? | |
NXP |
|
ARMv7 | ? |
Good:
Issues: Optional: |
Mostly complete | Mostly complete? (bareobx?, u-boot?) |
|
? | ? | ? | |
NXP |
|
ARMv7 | No GPU | Good:
Optional: |
Good | Good |
|
? | ? | ? | |
NXP | i.MX8 (models?) | ARM 64bit? | Vivante |
Issues:
Optional: |
|
? | ? | ? | |||
Samsung |
|
ARMv4 | No GPU? | No known issues | Needs to be ported to the devicetree | ? |
|
? | ? | ? | |
Creative | ZMS-08 | Armv7 (Cortex A8) | Vector Processor (?) | ? | ? | ? | ? | ? | ? | ? | ? |
Vendor | Product | CPU architecture | GPU | RYF issues | Linux upstream status | Bootloader upstream status | Busses for WiFi | Companion chips | Documentation | Minumum quantities | Available until |
TODO
- Document microcode:
- Look at which Freescale/NXP SOC or CPU use a microcode
- Migrate the Processors page here
References
- ↑ https://gitlab.denx.de/u-boot/u-boot/raw/master/doc/board/amlogic/libretech-ac.rst
-
↑ From #linux-amlogic on Freenode:
10:10 < repk> GNUtoo: bl31 is secure monitor or the ATF runtime, it runs in EL3 and dispatch SMC to secure/non-secure world. bl301 is a part of the SCP firmware. On meson the SCP is run by a microcontroller (cortex-M3) and handles power related stuff.
10:10 < repk> see https://trustedfirmware-a.readthedocs.io/en/latest/ for more on that
10:15 < repk> So BL1 is the CPU boot ROM code executes in SRAM and lunch BL2 which initializes DDR load all remaining firmwares (BL30 SCP, BL31 secure monitor, BL32 TEE, BL33 u-boot) in it. Then BL31 installs the secure monitor sends bl30 to SCP, and gives control to BL32 (if exists e.g. OPTEE) and BL33 (usually u-boot). Then u-boot loads boots linux.
- ↑ https://source.denx.de/u-boot/u-boot/-/raw/master/doc/board/amlogic/libretech-cc.rst
- ↑ https://trustedfirmware-a.readthedocs.io/en/latest/plat/meson-gxl.html