nyuuzyou/wikis huggingface dataset:
Amazon Fire HD 10 (amazon-suez)

== Contributors ==
* Hadi Charara <hadicharara@ymail.com>
== Users owning this device ==
== How to enter flash mode ==
You have to have your bootloader unlocked through this method: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
Entering fastboot through normal methods will not work as we need to access the hacked bootloader. Normal fastboot doesn't let us flash in the required partitions.
Simply hold volume up while powering it up to access TWRP. From TWRP you can reboot into the hacked bootloader as needed.
== Installation ==
From TWRP, you have access to ADB sideload, which you can use to install the recovery zip exported from pmbootstrap, or you can reboot into the hacked bootloader to access fastboot. You have to take the following things into consideration:
- fastboot has a limit on the filesize of files to be flashed. rootfs cannot be flashed from fastboot. Only boot can be flashed. To flash rootfs, use ADB sideload.
- Since the unlocking of the bootloader modified the paritition scheme of the device, to flash into it, you have to execute: fastboot flash boot_x FILE_TO_BE_FLASHED
- The default recovery zip generated by pmbootstrap flashes boot.img into the paritition named 'boot'. This won't work as the hacked bootloader resides there. Instead, we have to unpack the zip file, modify line 5 of chroot/install_options and lines 69 and 70 of chroot/bin/pmos_install_functions to replace boot by boot_x. Repack the zip file afterwards and it should be good to go.
== Mainline ==
Parts 	Components 	In Torvalds tree? 	In chromiumOS-5.4 kernel?
Chipset 	MT8173 	Yes (mt8173.dtsi) 	Yes (mt8173.dtsi)
GPU 	PowerVR GX6250	No 	Yes (img-rouge)
Touch Screen 	ft5726NEi 	Yes (edt-ft5x06.c) 	Yes (edt-ft5x06.c)
Accelerometer	BMA253 	No 	No
ALSPS 	STK3X1X/ltr559	Yes (stk3310.c) / Yes (ltr501.c)	Yes (stk3310.c) / Yes (ltr501.c)
Sound 	rt5514 	Yes (rt5514.c) 	Yes (rt5514.c)
== See also ==
* Initial merge request
* 
*
Amazon Fire HD 8 2017 (amazon-douglas)

== Contributors ==
* shuhao
== Users owning this device ==
== Known Issues ==
* When accessing the audio device (such as via hwtest), the device freezes. After reboot you may be prompted with a "Collecting Logs" screen with an Amazon logo, indicating some sort of firmware level log collector.
* CPU1,2,3 continuously enable and disable themselves, with logs such as:
[ 378.053320] -(3)[0:swapper/3]CPU3: Booted secondary processor
[ 378.053334] -(3)[0:swapper/3][name:cpuinfo&]Detected VIPT I-cache on CPU3
[ 378.053385] -(3)[0:swapper/3][name:topology&]CPU3: update cpu_capacity 1024
[ 378.122632] (0)[1829:kworker/0:2][name:mtk_wcn_stub_alps&][cmb_stub] thermal_ctrl_cb null
[ 378.342631] -(0)[1600:kwin_wayland][name:sched_monitor&][BURST IRQ DURATION WARN] IRQ[ 51:musb-hdrc.0.auto] +1237 ( dur 30000 us , avg 24 us)
[ 379.122661] (0)[1829:kworker/0:2][name:mtk_wcn_stub_alps&][cmb_stub] thermal_ctrl_cb null
[ 380.053771] (1)[71:hps_main][name:smp&]CPU3: shutdown
* Although the kernel can detect plugged in USB keyboard, nor X neither wayland can use the keyboard. evtest works tho. USB drives also mounts correctly..
== How to enter flash mode ==
* You need to be bootloader unlocked via this method: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846.
* After unlock, the normal fastboot doesn't let us flash in the required partitions? See notes on Amazon Fire HD 10 (amazon-suez).
* Holding + gets you into TWRP.
* Flash with the ADB sideload method.
* However, the default recovery.zip generated by pmbootstrap flashes into the boot partition, not the boot_x partition which is what is needed for this device. The recovery.zip file has to be manually editted to replace boot with boot_x in chroot/install_options and chroot_bin/pmos_install_functions. Again, see notes on Amazon Fire HD 10 (amazon-suez).
Alternatively, you can flash just the boot_x partition and then flash the rest of the system on an external sdcard:
* pmbootstrap install --sdcard=/dev/...: This will install the rootfs on a SD card mounted on your computer.
* fastboot flash boot_x boot.img-amazon-douglas: This will flash the initramfs onto the device.
* Then remove the sd card from your computer and insert it into the device. Then reboot it.
* Future updates to the rootfs does not require additional fastboot operations.
== See also ==
* Initial merge request
Amazon Fire HD 8 2018 (amazon-karnak)

== Contributors ==
* BenTheTechGuy
== Users owning this device ==
== How to enter flash mode ==
* Your bootloader must be unlocked via this method: https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2018-karnak-amonet-3.3963496/
* PMOS needs to be flashed using TWRP instead of fastboot so the boot.img can be patched with the amonet exploit.
* TWRP can be reached by holding and at boot.
== Installation ==
 pmbootstrap init
pmbootstrap install --android-recovery-zip --recovery-install-partition=data
# Make sure you're booted into TWRP at this point
pmbootstrap flasher --method=adb sideload
== See also ==
* 
*
Amazon Fire TV 3 (amazon-needle)

== Contributors ==
* BenTheTechGuy
== Users owning this device ==
== Unlocking the bootloader ==
Root the device using the FireFU exploit, which takes advantage of vulnerabilities in Amlogic DFU mode and U-Boot to unlock the bootloader and disable dm-verity. You will need an I2C-capable Arduino such as the Due as well as an HDMI breakout board (or a cut HDMI cable).
NOTE: The FireFU exploit does not work on devices running FireOS 6.2.5.8 or newer. Even after unlocking the bootloader, upgrading to those versions of FireOS disables flashing of unsigned images in Fastboot. Due to FireFU's repositioning of the boot image's offsets, your device will be bricked if it upgrades past 6.2.5.5 with FireFU installed. It's highly recommended to block all OTA updates after rooting the device.
== How to enter flash mode ==
In FireOS, connect with adb over the network or USB and run adb reboot bootloader.
In DFU mode, run ./aml_reboot fastboot in the FireFU directory.
== Installation ==
== See also ==
* Original Amazon Kernel
Amazon Fire TV Stick 4K (amazon-mantis)

__TOC__
== Contributors ==
User:Ungeskriptet
== Maintainer(s) ==
== Users owning this device ==
== Unlocking the bootloader ==
# Download and extract kamakiri-mantis-v2.0.1.zip
# Run the bootrom-step.sh script from a Linux computer
# Connect the Fire TV Stick to the computer with a USB cable. The script will now start exploiting the bootrom of the Fire TV Stick
# After the first script finished, run the fastboot-step.sh script to flash TWRP
# Your Fire TV Stick 4K is now successfully exploited and unlocked!
== How to enter recovery mode ==
To boot into recovery/fastboot mode, run the boot-recovery.sh or boot-fastboot.sh script from this archive first and connect the Fire TV Stick with a USB cable to the computer.
== Installation ==
Follow the installation guide and create a recovery zip, then export the zip using $ pmbootstrap export and copy it onto a USB drive. Boot the Stick into recovery mode and install the zip from USB drive by going to "Install", "Select storage" and select the last storage device. When plugging in a USB drive/selecting storage the device may freeze up, so only insert the USB drive when already booted in TWRP. 
== UART ==
To get UART working, solder wires the points shown below and run the enable-uart command in a TWRP shell. The baud rate is 921600. 
== See also ==
* WIP kernel for MT8695
* FCC certification page
* Kernel + MT7668 driver sources
* Initial merge request
* 
* 
* DIAL
Category:Devices with known UART pinout
Amazon Fire TV Stick Basic Edition (amazon-tank)

== Contributors ==
*Nimayer(Symmetrist)
== Maintainer(s) ==
*Nimayer(Symmetrist)
== Users owning this device ==
== Information ==
The Amazon Fire TV Stick Basic Edition contains the same hardware of Fire TV Stick (Gen 2), but is meant for global market.
== Unlocking the bootloader ==
Before installing PostmarketOS you need to unlock the bootloader using the amonet exploit as explained here.
== Installation ==
* Install the amonet exploit following this guide on XDA
* Configure PostmarketOS using pmbootstrap init
* Create the recovery zip using pmbootstrap install --android-recovery-zip
* Export the recovery zip using pmbootstrap export
* Clone the amonet repository
* Launch amonet/boot-recovery.sh
* Connect the Fire TV Stick to your computer
* The Fire TV Stick should boot to TWRP recovery
* Copy the recovery zip with adb push /tmp/postmarketOS-export/pmos-amazon-tank.zip /tmp/
* Install the recovery zip with adb shell twrp install /tmp/pmos-amazon-tank.zip
* Reboot with adb shell reboot
== Serial port ==
This picture shows the location of the UART pads on the PCB.
== Full PCB photo ==
== See also ==
* Initial merge request
* 
* 
* FCC certification page
* DIAL
Amazon Kindle 4 (amazon-yoshi)

== Contributors ==
* samcday
== Users owning this device ==
== How to enter flash mode ==
* Jailbreak your device by following the Kindle4NTHacking Jailbreak guide from MobileRead wiki.
* Follow the instructions on the Kindle4NTHacking page to set up USBnet and obtain a root shell.
* Write the image to main partition:
 cat /tmp/postmarketOS-export/amazon-yoshi.img | ssh -oHostKeyAlgorithms=+ssh-rsa -oKexAlgorithms=+diffie-hellman-group1-sha1 root@192.168.15.244 "dd of=/dev/mmcblk0p1 bs=512"
* Reboot into fastboot mode:
 idme -d --bootmode fastboot
 reboot
* Download and compile fread-installer-fastboot
* Flash kernel:
 ./fastboot flash kernel /tmp/postmarketOS-export/uImage && ./fastboot setvar bootmode main && ./fastboot reboot
* Congratulations, you now have a much less useful e-reader device. But it's running mainline Linux, so there's that at least!
== Installation ==
== See also ==
* Initial merge request
*i.MX508 product page
Amazon Kindle Fire HD 3rd Generation (amazon-soho)

== Contributors ==
* Jack_Kekzoz
* Shrimpboyho3
== Maintainer(s) ==
* Jack_Kekzoz
* Shrimpboyho3
== Users owning this device ==
== Downstream kernel ==
Please note the downstream kernel is currently NOT SELinux enforcing. It is built using gcc4. This kernel can be installed easily using the installation guide now that the initial merge request has been merged, though please do note the quirks in the Installation section below.
== Mainline kernel ==
Though no effort has been made to mainline this device yet, there is good support for OMAP4 in mainline. Efforts have been made to mainline the 8.9 inch Kindle Fire HD (jem), which uses the same SoC and many of the same components, so much of the code will work for soho.
== How to flash firmware ==
You can flash firmware two different ways: fastboot or recovery.
To flash pmOS, you need a recovery such as TWRP or use fastboot. To get into fastboot mode, a fastboot/factory cable is required. Connect the cable to the (powered off) device first, and then connect it to your computer. The device will then boot into fastboot mode. An alternative method is also available. If your device has root, you can boot into TWRP by following instructions on XDA (just search "kindle fire soho twrp" on Google).
To boot into TWRP once installed, press the volume down button and the power button at the same time, releasing the power button when the 'Kindle Fire' logo appears, and only releasing the volume down button when the white Amazon logo appears.
== Installation ==
For flashing, pmbootstrap flasher flash_rootfs works, but for some reason pmbootstrap flasher flash_kernel does not. However, pmbootstrap export allows you to fastboot flash boot /path/to/boot.img-amazon-soho, which works fine (though some versions of fastboot require flash:raw instead of flash)
Sideloading a recovery zip in TWRP also should work.
== Partitions ==
Output of sudo parted /dev/mmcblk0 print:
Model: MMC SEM08G (sd/mmc)
Disk /dev/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 
Number	Start 	End 	Size 	File system	Name 	Flags
1 	131kB 	262kB 	131kB 	 	xloader 	msftdata
2 	262kB 	524kB 	262kB 	 	bootloader	msftdata
3 	524kB 	590kB 	65.5kB	 	idme 	msftdata
4 	590kB 	606kB 	16.4kB	 	crypto 	msftdata
5 	606kB 	608kB 	2048B 	 	misc 	msftdata
6 	1049kB	17.8MB	16.8MB	ext4 	efs 	msftdata
7 	17.8MB	26.2MB	8389kB	 	recovery 	msftdata
8 	26.2MB	32.7MB	6519kB	 	boot 	msftdata
9 	32.7MB	41.1MB	8397kB	 	exploit 	msftdata
10 	41.2MB	1343MB	1302MB	 	system 	msftdata
11 	1343MB	2287MB	944MB 	ext4 	cache 	msftdata
12 	2287MB	7818MB	5531MB	ext4 	userdata 	msftdata
== See also ==
* TWRP installation files and instructions
* Initial merge request
* 
*
Amediatech X96 air (amediatech-x96-air)

== Contributors ==
* Petr Hodina
== Users owning this device ==
== Summary ==
This device is nearly identical to the
X96 Max Plus.
The main difference is additional USB 2.0 port on the device.
There are 2 variants:
* 100M LAN
* 1Gbit LAN
== Installation ==
Use pmbootstrap to build your own installation image.
$ pmbootstrap init
$ pmbootstrap install --fde
== See also ==
* Initial merge request
Amediatech X96 mini (amediatech-x96-mini)

== Contributors ==
== Users owning this device ==
== How to enter flash mode ==
== Installation (to sdcard) ==
1. Follow the steps on Installation_guide#Initialization
2. Choose the beelink-gt1 device
3. Start the build process and install the completed image to a sdcard
$ pmbootstrap install --sdcard /dev/sdX # replace /dev/sdX with the device for your sdcard
4. Place the sdcard into the Beelink gt1 (Ultimate) and boot it.
== Installation (to emmc) ==
1. Install pmOS to sdcard
2. Copy pmOS from sdcard to emmc
== LEDs ==
X96 Mini uses LEDs with 3 pins (blue+ pin, GND, red+ pin). The red+ pin is connected to the 3v VCC so the LED will light up at red colour when the box is connected to the power. The blue+ pin is connect to the GPIO and it is configured to be powered on when pmOS boots up. Therefore the LED will turn into blue when pmOS boots up.
How to manually power off the blue+ pin:
 # echo 0 > /sys/class/leds/x96-mini:blue:power/brightness
How to manually power on the blue+ pin :
 # echo 1 > /sys/class/leds/x96-mini:blue:power/brightness
== How to root the device ==
It comes with root by default.
== UART ==
baud rate : 115200 , volt: 3v
The stock Android will give you a shell that is run as root.
== How to wipe the stock U-Boot ==
# Connect to it via UART
# Wait until it boots
# Run as root
# dd of=/dev/block/mmcblk0boot0 if=/dev/zero
== Gallery ==
File:Mainline-uboot-on-x96-mini.png|thumb|left|Mainline U-Boot
== See also ==
* Initial merge request
Amlogic Generic TV Box (amlogic-tvbox)

This is a generic port for various Amlogic-based set-top boxes.
== Contributors ==
* User:FerassElHafidi (f_ on IRC)
* User:Exkc (@exxxxkc:matrix.org)
== Devices ==
== How to enter flash mode ==
(See Amlogic#Boot process)
== Installation ==
# Run pmbootstrap init and select amlogic as vendor and tvbox as device.
# Select the kernel variant based on your device
# Follow the onscreen instructions and configure as your needs.
Sample output:
[13:12:47] Location of the 'work' path. Multiple chroots (native, device arch, device rootfs) will be created in there.
[13:12:47] Work path [/home/UwU/.local/var/pmbootstrap]:
[13:12:48] Choose the postmarketOS release channel.
[13:12:48] Available (10):
[13:12:48] * edge: Rolling release / Most devices / Occasional breakage: https://postmarketos.org/edge
[13:12:48] * v24.06: Latest release / Recommended for best stability
[13:12:48] * v23.12: Old release (unsupported)
[13:12:48] Channel [edge]:
[13:12:49] NOTE: pmaports is on master branch, copying git hooks.
[13:12:49] Choose your target device vendor (either an existing one, or a new one for porting).
[13:12:49] Available vendors (91): acer, alcatel, amazon, amediatech, amlogic, apple, ark, arrow, asus, ayn, beelink, bq, clockworkpi, cubietech, cutiepi, dongshanpi, epson, essential, fairphone, finepower, fly, fxtec, generic, goclever, google, gp, hisense, htc, huawei, inet, infocus, jolla, klipad, kobo, lark, leeco, lenovo, lg, librecomputer, linksys, mangopi, medion, meizu, microsoft, mobvoi, motorola, nextbit, nobby, nokia, nvidia, odroid, oneplus, oppo, ouya, pine64, planet, pocketbook, postmarketos, powkiddy, purism, qcom, qemu, qualcomm, radxa, raspberry, realme, samsung, semc, sharp, shift, sipeed, sony, sourceparts, surftab, t2m, thundercomm, tokio, tolino, trekstor, valve, vernee, vivo, volla, wexler, wiko, wileyfox, xiaomi, xunlong, yu, zte, zuk
[13:12:49] Vendor [qemu]: amlogic
[13:12:54] Available codenames (1): tvbox
[13:12:54] Device codename: tvbox
[13:13:00] Which kernel do you want to use with your device?
[13:13:00] Available kernels (4):
[13:13:00] * p201: Kernel for Amlogic P201-based TV box (S905)
[13:13:00] * p212: Kernel for Amlogic P212-based TV box (S905X)
[13:13:00] * videostrong-kii-pro: Kernel for Videostrong KII Pro (S905)
[13:13:00] * xiaomi-once: Kernel for Xiaomi Mi Box 3 (S905X)
[13:13:00] Kernel [xiaomi-once]:
Then flash to an USB stick/SD card:
$ pmbootstrap install --sdcard=/dev/device # Replace device with your storage device
Next, boot pmOS on your device. This might depend on which device you're trying to boot. On most devices, you need to hold a button hidden in the AV port or at the bottom while booting. For other devices where this does not work, look at your device's page. E.g. Xiaomi Mi Box 3 (xiaomi-once) requires some more setup before it'll boot.
== See also ==
* Initial merge request
* Amlogic#U-Boot quirk in some set-top boxes
* 
*
Amlogic S812/S812-B/S812-S/S805/S802

The S812/S812-B/S812-S/S805/S802 SoCs are media player SoCs mainly used in Android set-top boxes.
S802 is the only chip in the Meson8 Amlogic SoC family. S805 is the only chip in the Meson8b .The rest of them are part of Meson8m2.However,they are very similar to each other .Here are the differences between them:
Here is the difference between them :
* S802: 4x 2GHz Cortex-A9
* S805: Similar to S802 but with Cortex-A5
* S812: Similar to S802 but with H.265 UHD Decoder
* S812-S: Similar to S802 but with Dolby digital hardware decoding
* S812-B: Unknown
There are also -h variant of S812/S812-B/S812-S/S805/S802. it is a variant of the soc that has include Dolby/DTS licenses.
== Devices ==
==See Also==
s802-b Spec
Amlogic S905D2/S905X2/S905Y2/A311D/S922X

The S905D2/S905X2/S905Y2/A311D/S922X SoCs are media player SoCs mainly used in Android set-top boxes.
A311D/S922X are from G12B SoC family but the rest of them are part of G12A.However,they are very similar to each other .Here are the differences between them:
 
Here is the difference between them :
* S905D2: Enhanced audio (from AXG), 1x USB 3.0 or 1x PCIe 2.0, built-in 1G MAC and 100M PHY, two video decoders (4Kx2K@60fps + 1080P@60fps)
* S905X2: Similar to S905D2 but without DVB interface and DSI
* S905Y2: Similar to S905X2 but without built-in Ethernet
* S922X: Similar to S905X2 but with 4 X Cortex-A73@1.8GHZ,2 X Cortex-A53@1.9GHZ (Kind of like Amlogic S912 in term of performance range)
* A311D: Similar to S922X but with NPU
There are also -h variant of S905D2/S905X2/S905Y2. it is a variant of the soc that has include Dolby/DTS licenses.
== Devices ==
== See Also ==
* Amlogic
* Linux and U-Boot mainlining status
Amlogic S905D3/S905X3/S905Y3

The S905D3/S905X3/S905Y3 are very similar to each other and are from the SM1 Amlogic SoC family. 
Here are the differences between them:
* S905D3: Enhanced audio (from AXG), 1x USB 3.0 or 1x PCIe 2.0, built-in 1G MAC and 100M PHY, two video decoders (4Kx2K@60fps + 1080P@60fps), Neural Processor Unit, MIPI-DSI and CSI input
* S905D3-NON: similar to S905D3 but without NPU
* S905X3: Similar to S905D3 but without the DSI output and CSI input
* S905Y3: Similar to S905X3 but without DVB interface and built-in Ethernet
There are also -h variant of S905D3/S905X3/S905Y3. it is a variant of the soc that has include Dolby/DTS licenses.
== Devices ==
== Boot process ==
== Status ==
=== NPU ===
Requires a proprietary downstream driver. Tomeu Vizoso is working on reverse-engineering the NPU.
Join #ml-mainline on irc.oftc.net if you wish to help.
=== Audio ===
Works
== See also ==
* Amlogic
* Linux and U-Boot mainlining status
Amlogic S905W/S905D/S912/S905X/S905L/S805X/S805Y/S905Z

Amlogic S905W/S905D/S912/S905X/S905L/S805X/S805Y/S905Z SoCs are media player SoCs mainly used in Android set-top boxes.
S912 is the only chip in the GXM Amlogic SoC family but the rest of them are part of GXL.However,they are very similar to each other .Here are the differences between them:
 
High-end Chip :
* S905W : It capable of hardware decoding 4Kp60/30 H.265/H.264, VP9 and has 100M ethernet phy,1G ethernet mac,VP9 hardware , camera interface and TS inputs,1 X cpu cluster that contain 4 X Cortex-A53@2GHZ 
* S905D : Seem to identical to S905W , but support ISO7816 IN for DVB
* S912 : Identical to S905D but instead of having one cluster it has 2 thus it has 8 X Cortex-A53@2GHZ in total, uses exactly the same BL2 firmware as the others, but technically actually belongs in the GXM family
Mid-range Chip:
* S905X : A slightly lower clock variant (CPU cores up to 1.5 GHz) of S905W
* S905L : Identical to the S905X except for the lack of VP9 decoding, camera interface and TS inputs.
Low-end Chip:
* S805X : A slightly lower clocked (CPU cores up to 1.2 GHz) and can only decode 1080p60/30 H.265/H.264 , VP9.It is a stripped down variant of S905X.
* S805Y : Used in Xiaomi Mi TV Stick (xiaomi-aquaman), identical to the S805X.
Unknown :
* S905Z : Used in the Amazon Fire TV 3 (amazon-needle), identical to the S905X but lack of VP9 hardware decoding.
There are also -h variant of Amlogic S905W/S905D/S905X/S905L/S805X/S805Y/S905Z. it is a variant of the soc that has include Dolby/DTS licenses.
== Devices ==
==Different Between GXM and GXL==
<narmstrong> S912 is basically gxl with a second cpu cluster, so I think the gxl bl2 would work but bl31 should be fixed to bring up the second cluster
<f_> Pretty much..
<narmstrong> It’s even dumber that you think, the second cpu cluster hasn’t a dedicated pll, it uses the fixed 1ghz system pll fixed divider… <
See Irc log from linux-amlogic
== Boot process ==
See: Amlogic#Boot process
BL1 looks for a header (named @AML header) at different offsets depending on the storage media:
* On an SD card or eMMC: offset 512 (512 bytes completly ignored by BL1), header and checksum from offset 528 to 623, payload at offset 4608 onwards
BL2 is signed by using a proprietary utility from Amlogic called aml_encrypt_gxl, but there's a replacement called gxlimg. See https://github.com/repk/gxlimg. It has been confirmed to work on Libre_Computer_AML-S905X-CC-V1.0_(librecomputer-lepotato)
Then BL2 loads the following:
* BL30/SCP_BL2: System control processor firmware
* BL31: EL3 Runtime Software
* BL32: OPTEE (optional)
* BL33: U-Boot
All bootloader stages except U-Boot are proprietary. BL31 can be replaced with upstream Arm Trusted Firmware-A.
There's also an ongoing effort led by User:F to reverse-engineer BL2 and port U-Boot SPL.
== Status ==
=== GPU and hardware acceleration ===
Works.
=== IR RX ===
Works
=== Audio ===
S/PDIF audio works, but HDMI is untested
=== X11 ===
Works fine. A custom configuration file is needed else it crashes (included).
== See also ==
* Amlogic
* S905X datasheet
* Linux and U-Boot mainlining status
Amlogic S905X4/S905C2

The S905X4/S905C2L are very similar to each other and they are from SC1 SoC family. 
Here is the difference between them :
* S905C2: 
* S905X4: 
There are also -h variant of S905C2/S905X4. it is a variant of the soc that has include Dolby/DTS licenses.
== Devices ==
== See Also ==
* Amlogic
* Linux and U-Boot mainlining status
* [Potential downstream kernel]