TimSmall

Tried the 4.4 images (
 
apt install linux-dtb-legacy-rockchip linux-image-legacy-rockchip  
... which bricks it nicely, but during early boot it does at least I get some trace of the device:
 
U-Boot 2020.07-armbian (Oct 19 2020 - 00:10:11 +0200) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPC-T4 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: FriendlyElec NanoPC-T4 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 18 ms (171.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 181 bytes read in 15 ms (11.7 KiB/s) 6557203 bytes read in 645 ms (9.7 MiB/s) 8565640 bytes read in 832 ms (9.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: Vendor: 0x144d Rev: 1L2QEXD7 Prod: S41GNX0M266030 Type: Hard Disk Capacity: 244198.3 MB = 238.4 GB (500118192 x 512) ... is now current device Scanning nvme 0:1... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus usb@fe3c0000: USB EHCI 1.00 Bus dwc3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus dwc3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found  
This looks like uboot finding it. It subsequently tries to network boot.  Any tips for attempting to debug this further?  What are the moving parts?  Is it just going be kernel PCIe init/probe code, or is there rockchip firmware at play too?
 
Cheers!
 
Tim.

I'll try to add support for it soon. But it will be in the same boat as others at first. Don't expect to have 10 bit HEVC support at the beginning. BTW, VP9 is separate peripheral so it needs separate driver. Since nobody did reverse engineering yet, it will take a long time to be supported. However, it seems to be Webm project reference VP9 HW decoder, so there is a great chance that other SoCs from other manufacturers have same unit and someone else might write a driver for it.