Linux mainline 5.7 just released

my recommendation wait some days - we still try fix missed places and fix bugs :wink: but its already usable !

Ok no worries.
Will wait for it :wink:

good news nvme works for VIM3 VIM3L same as for Edge

root@Krescue:/# uname -a
Linux Krescue 5.7.0 #1 SMP PREEMPT Mon Jun 1 20:48:36 +09 2020 aarch64 GNU/Linux
root@Krescue:/# lspci
01:00.0 Class 0108: 2646:2263
00:00.0 Class 0604: 16c3:abcd
root@Krescue:/# ls /dev/nvme
nvme-fabrics  nvme0n1       nvme0n1p2
nvme0         nvme0n1p1     nvme0n1p3

root@Krescue:/# iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"OW11"  
          Mode:Managed  Frequency:5.18 GHz  Access Point: 10:D0:7A:9A:AB:A4   
          Bit Rate=390 Mb/s   Tx-Power=31 dBm   
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=56/70  Signal level=-54 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@Krescue:/# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 7E:FB:81:2D:33:C8  
          inet addr:172.23.10.244  Bcast:172.23.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5413 (5.2 KiB)  TX bytes:4532 (4.4 KiB)
          Interrupt:7 
5 Likes

Great work @hyphop, looking forward to this, what are the new features by the way :smile:

I tried nvme on VIM3/PRO and just noted that when writing to nvme frequently noise affects the readability of the screen. When reading from nvme such noise is not there. What could it be? Thanks

@hyphop what about other PCIE devices?
Is it finally possible to connect dvb-t pcie or something else (gfx card) ?

btw http://lists.infradead.org/pipermail/linux-amlogic/2020-May/016641.html

1 Like

Is there support for NPU?

no npu is supported only on 4.9

1 Like

why not ? i have test wifi pcie card and nvme ssd disk only and it same pci

1 Like

I mean if amlogic npu galcor modules was porter over the 5.7 kernel ?

Hi @hyphop
Can I build 5.7 now? I hope the patches will work fine now ?

yes u can try
fenix used already linux mainline 5.7

or there (one defconfig for both soc amlogic + rockchip )

1 Like

Building it using the combined defconfig
Here is the build process.

Building on Khadas Vim3. Lets see how long it takes.

UPDATE: Your defconfig is incomplete even for only aml and rk config, Panfrost and lima is missing. Normally I use defconfig and do menuconfig to add the missing but in your I have to define everything all over again so instead I will just use my own.
Thanks. It built fine though.

yes ! its minimal for khdas boards ! but u can improve as u like ! and do make savedefconfig and generate and use new defconfig

PS: just my recommendation not include everything to kernel its bad practice - if possible make as module we make as module (only special parts which necessary for boot-up we enable in kernel )

I do not know if it is kernel related, but we have some issue with wifi on VIM1 running this kernel,
see Debian buster cannot see non US wifi channel SSID (and connect))

in dmesg, we have these errro messages:

[    4.136703] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    4.200186] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.khadas,vim.txt failed with error -2

It is working kind of “fine”
I made issue in github so plz add pcie patch
thx

both message its not real problem errors! i will check your problem Mainline linux built by fenix and kresq not listing wifi channel 13+ (and not connect) soon

1 Like

yes please, andnin fact, your latest openwrt also has this issue, so i think it s related to mainline kernel, but got unnoticed by most. It used to work ok in older kernels like 4.9.x :crazy_face:

Has anyone tried the CEC framework on a VIM3L? My first pass last night with cec-ctl and cec-follower seemed to talk to an empty bus. Same devices works fine with Android TV CEC implementation. Haven’t had a chance to dig in, but curious?