[TEST/A20/Lamobo R1/20160307] kernel 4.4.4 Linaro gcc 5.1.1 (full crypto, power managt)

[wildcat_paris]

FYI

 

quick update kernel 4.4.24

gr@bpi:~$ cat /proc/version
Linux version 4.4.4-sunxi (root@server1404) (gcc version 5.1.1 20150608 (Linaro GCC 5.1-2015.08) ) #1 SMP Mon Mar 7 13:55:59 CET 2016

download deb here

 

 

 

I have moved to 4.4.4 Xcompiled with linaro 4.9.2 5.1.1

 

=> Armbian tool on Ubuntu 14.04.34  guest with gcc 5.3

 

full-crypto + A20 hardware (P)RNG + CPU @1GHz

 

NOTE: [standard sunxi-next] nice, the linux-trusty*.deb package is built with kernel only compile (thanks)

config

http://pastebin.com/V4p7B9bK

 

 

 

NOTE : [standard sunxi-next] nice to have NEON as module

 

I prefer CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y

testing CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE=y

CONFIG_PM_DEVFREQ=y

 

added LED triggers

but forgot to add Ministrel for Wifi AC

Edited March 9, 2016 by wildcat_paris
kernel 4.4.4

[Igor]

nice job. 

 

OK, a lot of diffs are M to Y ... any reason why shouldn't we leave those as modules?

[wildcat_paris]

Hello Igor,

 

The M => Y is not a request for standart (for crypto especially)... my own choice only... I am supposed to work one day on a module with kernel crypto with fast PRNG upgrading frandom module from ARC4 to SALSA or AES... one day

[Jacob Gadikian]

I'm going to be using a lamobo today to make my internet not-shit via MPTCP.  If people would like< I'm glad to try and add MPTCP kernel support to armbian while I am at it.  

 

.....Wildcat-- I'd love to know what the kernel you mentioned is all about, too.  Sounds, well like the sort of thing I'd do...... or try to anyway .  

[wildcat_paris]

@Jacob

 

you mean

https://en.wikipedia.org/wiki/Multipath_TCP

 

looking at mptcp, it is not included in the linux kernel tree (as far as I can see), currently they maintain kernel 3.18 version on github and there is a patch for kernel 4.1 (does it work on 4.4? to be tested?)

 

Isn't that a (apache,etc.) server side feature, Apple is using it to optimize "Hello Siri" connections?

 

http://multipath-tcp.org/pmwiki.php?n=Main.Release90

http://multipath-tcp.org/pmwiki.php/Users/DoItYourself

http://multipath-tcp.org/patches/

 

and also, you need to compile routing tool packages adapted to mptcp, etc.

https://github.com/multipath-tcp

 

so? can it help the Lamobo-R1 hardware limitations?

 

---

 

in case you want to play with my kernel built with the Armbian tool, here is my deb files for kernel 4.4.4 for trusty / with CPU @1GHz + performance governor, standard Armbian already integrates the patch from OpenWRT for lamobo to improve TCP

download : http://guillaume.romagny.free.fr/lamobo/(use @ your own risk!)

gr@bpi:~$ cat /proc/version
Linux version 4.4.4-sunxi (root@server1404) (gcc version 5.1.1 20150608 (Linaro GCC 5.1-2015.08) ) #1 SMP Mon Mar 7 13:55:59 CET 2016

 

 

gr@bpi:~$ sensors
sun4i_ts-isa-0000
Adapter: ISA adapter
SoC temperature:  +36.4°C

gr@bpi:~$ sudo cpufreq-info
[sudo] password for gr:
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 244 us.
  hardware limits: 144 MHz - 1.01 GHz
  available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz, 1.01 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand, performance
  current policy: frequency should be within 144 MHz and 1.01 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1.01 GHz (asserted by call to hardware).
  cpufreq stats: 144 MHz:0.00%, 312 MHz:0.00%, 528 MHz:0.00%, 720 MHz:0.00%, 864 MHz:0.00%, 912 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:100.00%  (1)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 244 us.
  hardware limits: 144 MHz - 1.01 GHz
  available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz, 1.01 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand, performance
  current policy: frequency should be within 144 MHz and 1.01 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1.01 GHz (asserted by call to hardware).
  cpufreq stats: 144 MHz:0.00%, 312 MHz:0.00%, 528 MHz:0.00%, 720 MHz:0.00%, 864 MHz:0.00%, 912 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:100.00%  (1)