Kernel 5.0 development thread

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Kernel 5.0 development thread

Unread post by memeka » Fri Jan 18, 2019 11:16 pm

Code: Select all

$ uname -a
Linux odroid 5.0.0-rc2 #3 SMP PREEMPT Sat Jan 19 00:08:56 ACDT 2019 armv7l armv7l armv7l GNU/Linux
source: https://github.com/mihailescu2m/linux
boot log: http://paste.ubuntu.com/p/NrJ3Dh9tw9/

working: mali, HMP
to test: USB, MFC, sound, CPUfreq/fan, ...
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:20 pm)

User avatar
rooted
Posts: 7340
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 497 times
Been thanked: 138 times
Contact:

Re: Kernel 5.0 development thread

Unread post by rooted » Sat Jan 19, 2019 1:06 am

subscribed

User avatar
mad_ady
Posts: 7568
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 394 times
Been thanked: 300 times
Contact:

Re: Kernel 5.0 development thread

Unread post by mad_ady » Sat Jan 19, 2019 2:33 am

great job!

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Sat Jan 19, 2019 10:38 am

Great news!
According to the boot log, your USB WiFi dongle seems to be working at least. :D

BTW, can you guys estimate when we can see the next LTS kernel even very roughly?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Sat Jan 19, 2019 10:45 am

USB both 2.0 and 3.0 ports, even USB 3.0 hub plugged in a USB 3.0 port is recognised. Network is seen on gb speed. Just need to test stability of hdd under heavy io load.

@mdrjr thinks 5.0 will be lts, I think maybe 5.4.
But keeping up to date with kernel api changes will help a lot on the next lts. 4.19 lts is only few months supported than 4.14 so no point doing that.

My next focus will be fixing mfc, even if recognised I am not sure it works well...

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Sat Jan 19, 2019 11:26 am

Glad to hear that USB 3.0 Superspeed mode works fine.
I agree with the opinion that the next LTS will be seen in the second half of this year and we can live with 4.14 until new 5.x LTS is available.

We will keep looking into your new repo: https://github.com/mihailescu2m/linux/t ... dxu4-5.0.y ;)

elatllat
Posts: 1690
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 31 times
Been thanked: 96 times
Contact:

Re: Kernel 5.0 development thread

Unread post by elatllat » Sun Jan 20, 2019 11:25 am

Thanks memeka.
Though ext4 is pressuring me to abandon 32bit systems.

History for the dts seems old
https://github.com/mihailescu2m/linux/b ... oidxu4.dts
There is divergence

Code: Select all

git diff --stat remotes/hardkernel/odroidxu4-4.14.y remotes/mihailescu2m/odroidxu4-5.0.y -- arch/arm/boot/dts/exynos5422-odroidxu4.dts
 arch/arm/boot/dts/exynos5422-odroidxu4.dts | 151 ++++++++++++++++++++------------------------------------------------------------------
 1 file changed, 35 insertions(+), 116 deletions(-)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Sun Jan 20, 2019 12:54 pm

elatllat wrote:
Sun Jan 20, 2019 11:25 am
History for the dts seems old
https://github.com/mihailescu2m/linux/b ... oidxu4.dts
There is divergence

Code: Select all

git diff --stat remotes/hardkernel/odroidxu4-4.14.y remotes/mihailescu2m/odroidxu4-5.0.y -- arch/arm/boot/dts/exynos5422-odroidxu4.dts
 arch/arm/boot/dts/exynos5422-odroidxu4.dts | 151 ++++++++++++++++++++------------------------------------------------------------------
 1 file changed, 35 insertions(+), 116 deletions(-)
exynos5422-odroidxu4.dts is exactly the same as the one on mainline.

Code: Select all

odroid@odroid:~/src/odroidxu4-5.0.y$ git diff --stat remotes/origin/master remotes/memeka/odroidxu4-5.0.y -- arch/arm/boot/dts/exynos5422-odroidxu4.dts
odroid@odroid:~/src/odroidxu4-5.0.y$ 

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Mon Jan 21, 2019 10:25 am

1. MFC debugged and fix found!

2. USB3.0
lsbusb -t command with a USB3.0 hub connected to one USB3.0 port, and in the hub a USB3.0 HDD, keyboard and mouse:

Code: Select all

$ lsusb -t
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
        |__ Port 2: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 4: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
        |__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 2: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 2: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
            |__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl8192cu, 480M
Haven't done stress-testing yet, but detection seems to work fine!

Code: Select all

[  932.167206] usb 4-1.2: new SuperSpeed Gen 1 USB device number 5 using xhci-hcd
[  932.190488] usb 4-1.2: New USB device found, idVendor=05e3, idProduct=0612, bcdDevice=92.12
[  932.190503] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  932.190510] usb 4-1.2: Product: USB3.0 Hub
[  932.190517] usb 4-1.2: Manufacturer: GenesysLogic
[  932.218252] hub 4-1.2:1.0: USB hub found
[  932.218620] hub 4-1.2:1.0: 4 ports detected
[  932.371050] usb 3-1.2: new high-speed USB device number 7 using xhci-hcd
[  932.475978] usb 3-1.2: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.12
[  932.475992] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  932.476000] usb 3-1.2: Product: USB2.0 Hub
[  932.476007] usb 3-1.2: Manufacturer: GenesysLogic
[  932.538245] hub 3-1.2:1.0: USB hub found
[  932.538559] hub 3-1.2:1.0: 4 ports detected
[  932.787111] usb 4-1.2.4: new SuperSpeed Gen 1 USB device number 6 using xhci-hcd
[  932.808627] usb 4-1.2.4: New USB device found, idVendor=1058, idProduct=0748, bcdDevice=10.19
[  932.808658] usb 4-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  932.808682] usb 4-1.2.4: Product: My Passport 0748
[  932.808689] usb 4-1.2.4: Manufacturer: Western Digital
[  932.808713] usb 4-1.2.4: SerialNumber: 575838314139324331313138
[  932.811024] usb-storage 4-1.2.4:1.0: USB Mass Storage device detected
[  932.821786] scsi host0: usb-storage 4-1.2.4:1.0
[  932.891066] usb 3-1.2.2: new low-speed USB device number 8 using xhci-hcd
[  932.999730] usb 3-1.2.2: New USB device found, idVendor=0b38, idProduct=0010, bcdDevice= 1.02
[  932.999744] usb 3-1.2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  933.087053] input: HID 0b38:0010 as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.0/0003:0B38:0010.0004/input/input5
[  933.147918] hid-generic 0003:0B38:0010.0004: input,hidraw0: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-xhci-hcd.1.auto-1.2.2/input0
[  933.153041] input: HID 0b38:0010 System Control as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.1/0003:0B38:0010.0005/input/input6
[  933.211394] input: HID 0b38:0010 Consumer Control as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.1/0003:0B38:0010.0005/input/input7
[  933.211753] hid-generic 0003:0B38:0010.0005: input,hidraw1: USB HID v1.10 Device [HID 0b38:0010] on usb-xhci-hcd.1.auto-1.2.2/input1
[  933.290981] usb 3-1.2.3: new low-speed USB device number 9 using xhci-hcd
[  933.398737] usb 3-1.2.3: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[  933.398747] usb 3-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  933.398754] usb 3-1.2.3: Product: USB Optical Mouse
[  933.398761] usb 3-1.2.3: Manufacturer: PixArt
[  933.410377] input: PixArt USB Optical Mouse as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.3/3-1.2.3:1.0/0003:093A:2510.0006/input/input8
[  933.411009] hid-generic 0003:093A:2510.0006: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-xhci-hcd.1.auto-1.2.3/input0
[  933.827764] scsi 0:0:0:0: Direct-Access     WD       My Passport 0748 1019 PQ: 0 ANSI: 6
[  933.828369] scsi 0:0:0:1: Enclosure         WD       SES Device       1019 PQ: 0 ANSI: 6
[  933.830421] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  933.831644] sd 0:0:0:0: [sda] Spinning up disk...
[  933.831985] scsi 0:0:0:1: Attached scsi generic sg1 type 13
[  934.850947] ......ready
[  939.971526] sd 0:0:0:0: [sda] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[  939.971878] sd 0:0:0:0: [sda] Write Protect is off
[  939.971885] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[  939.972242] sd 0:0:0:0: [sda] No Caching mode page found
[  939.976195] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  940.040331]  sda: sda1 sda2 sda3
[  940.045131] sd 0:0:0:0: [sda] Attached SCSI disk
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:20 pm)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Jan 22, 2019 3:11 pm

Updated to 5.0-rc3

* MFC issues were fixed by mainline patches in RC3
* added patches for frequency, cooling
* no ASV tabled patch, it will be implemented on mainline soon -> already added chipid patches

Code: Select all

$ sudo hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   2352 MB in  2.00 seconds = 1177.20 MB/sec
 Timing buffered disk reads: 340 MB in  3.02 seconds = 112.74 MB/sec
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:20 pm)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Jan 22, 2019 10:04 pm

Just added:

* implemented ASV tables (until samsung patches become available)
* fixes for thermal system
* HDMI resolutions and support for Vu5/7
* gsc, mfc fixes (incl. cacheable mmap)
* fixes for rtc/watchdog (not tested)
* chipid driver and other patches from samsung-soc (to be included later in mainline)
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:20 pm)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 23, 2019 9:13 am

* removed chipid driver to enable ASV tables patch to work properly

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 5.0.0-rc3 (odroid@odroid) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #20 SMP PREEMPT Wed Jan 23 10:27:24 ACDT 2019
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Hardkernel Odroid XU4
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 128 MiB at 0xb6800000
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] On node 0 totalpages: 518656
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 322048 pages, LIFO batch:63
[    0.000000] Running under secure firmware.
[    0.000000] random: get_random_bytes called from start_kernel+0xa0/0x498 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu @(ptrval) s38348 r8192 d23092 u69632
[    0.000000] pcpu-alloc: s38348 r8192 d23092 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516928
[    0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=12345678-1234-5678-9abc-123456789abc rootwait ro fsck.repair=yes net.ifnames=0  HPD=true vout=hdmi  smsc95xx.macaddr=00:1e:06:61:7a:39 false s5p_mfc.mem=16M
[    0.000000] hdmi: using HDMI mode
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1901124K/2074624K available (9216K kernel code, 731K rwdata, 2428K rodata, 1024K init, 318K bss, 42428K reserved, 131072K cma-reserved, 1157120K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 732 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 319 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] hperf_hmp: fast CPUs mask: 000000F0
[    0.000000] hperf_hmp: slow CPUs mask: 0000000F
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000030] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 49
[    0.001023] Console: colour dummy device 80x30
[    0.001687] printk: console [tty1] enabled
[    0.001739] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001779] pid_max: default: 32768 minimum: 301
[    0.001994] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002033] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002982] CPU: Testing write buffer coherency: ok
[    0.003488] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.024060] Setting up static identity map for 0x40100000 - 0x40100060
[    0.024392] ARM CCI driver probed
[    0.024632] Exynos MCPM support installed
[    0.031996] rcu: Hierarchical SRCU implementation.
[    0.047995] smp: Bringing up secondary CPUs ...
[    0.080354] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.104315] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.136311] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.168308] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.168317] CPU4: Spectre v2: using ICIALLU workaround
[    0.192280] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.192287] CPU5: Spectre v2: using ICIALLU workaround
[    0.204491] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.204499] CPU6: Spectre v2: using ICIALLU workaround
[    0.216497] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.216505] CPU7: Spectre v2: using ICIALLU workaround
[    0.216687] smp: Brought up 1 node, 8 CPUs
[    0.216731] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.216754] CPU: All CPU(s) started in HYP mode.
[    0.216773] CPU: Virtualization extensions available.
[    0.218626] devtmpfs: initialized
[    0.234415] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.234568] hperf_hmp: registered cpufreq transition notifier
[    0.234850] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.234886] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.237493] pinctrl core: initialized pinctrl subsystem
[    0.239473] NET: Registered protocol family 16
[    0.243106] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.244413] audit: initializing netlink subsys (disabled)
[    0.244610] audit: type=2000 audit(0.244:1): state=initialized audit_enabled=0 res=1
[    0.245230] cpuidle: using governor menu
[    0.245735] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.245761] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.287306] EXYNOS5420 PMU initialized
[    0.383229] usbcore: registered new interface driver usbfs
[    0.383300] usbcore: registered new interface driver hub
[    0.383466] usbcore: registered new device driver usb
[    0.384060] s3c-i2c 12c80000.i2c: slave address 0x00
[    0.384086] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.384381] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.384812] media: Linux media interface: v0.10
[    0.384861] videodev: Linux video capture interface: v2.00
[    0.384975] pps_core: LinuxPPS API ver. 1 registered
[    0.384995] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.385250] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    0.386049] Advanced Linux Sound Architecture Driver Initialized.
[    0.387263] clocksource: Switched to clocksource mct-frc
[    0.423277] random: fast init done
[    1.034381] VFS: Disk quotas dquot_6.6.0
[    1.034467] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.047886] NET: Registered protocol family 2
[    1.048515] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    1.048562] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    1.048652] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    1.048819] TCP: Hash tables configured (established 8192 bind 8192)
[    1.048934] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.048986] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.049306] NET: Registered protocol family 1
[    1.049877] RPC: Registered named UNIX socket transport module.
[    1.049900] RPC: Registered udp transport module.
[    1.049918] RPC: Registered tcp transport module.
[    1.049937] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.050146] Trying to unpack rootfs image as initramfs...
[    1.518914] Freeing initrd memory: 8212K
[    1.520156] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[    1.520995] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[    1.525406] Initialise system trusted keyrings
[    1.525633] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    1.534414] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.535157] NFS: Registering the id_resolver key type
[    1.535197] Key type id_resolver registered
[    1.535217] Key type id_legacy registered
[    1.535293] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.535349] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    1.639905] Key type asymmetric registered
[    1.639932] Asymmetric key parser 'x509' registered
[    1.640002] bounce: pool size: 64 pages
[    1.640062] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.640294] io scheduler mq-deadline registered
[    1.640317] io scheduler kyber registered
[    1.640578] io scheduler bfq registered
[    1.642947] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[    1.643065] samsung-usb2-phy 12130000.phy: Linked as a consumer to regulator.0
[    1.643891] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[    1.643985] exynos5_usb3drd_phy 12100000.phy: Linked as a consumer to regulator.0
[    1.644019] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[    1.644394] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[    1.644486] exynos5_usb3drd_phy 12500000.phy: Linked as a consumer to regulator.0
[    1.644518] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator
[    1.652823] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    1.652852] dma-pl330 121a0000.pdma: 	DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    1.655486] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    1.655513] dma-pl330 121b0000.pdma: 	DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    1.656352] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    1.656378] dma-pl330 10800000.mdma: 	DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    1.716649] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.718769] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 58, base_baud = 0) is a S3C6400/10
[    1.719164] 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 59, base_baud = 0) is a S3C6400/10
[    1.719597] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 60, base_baud = 0) is a S3C6400/10
[    2.628663] printk: console [ttySAC2] enabled
[    2.633317] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 61, base_baud = 0) is a S3C6400/10
[    2.643367] exynos-trng 10830600.rng: Exynos True Random Number Generator.
[    2.649630] iommu: Adding device 14450000.mixer to group 0
[    2.654718] exynos-mixer 14450000.mixer: Linked as a consumer to 14650000.sysmmu
[    2.663174] exynos-hdmi 14530000.hdmi: Failed to get supply 'vdd': -517
[    2.669025] iommu: Adding device 10850000.g2d to group 1
[    2.673648] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a60000.sysmmu
[    2.681013] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a70000.sysmmu
[    2.694060] mali 11800000.mali: Continuing without Mali regulator control
[    2.700656] mali 11800000.mali: GPU identified as 0x0620 r0p1 status 0
[    2.706412] mali 11800000.mali: Protected mode not available
[    2.711946] devfreq devfreq0: Couldn't update frequency transition information.
[    2.719586] mali 11800000.mali: Probed as mali0
[    2.733471] brd: module loaded
[    2.735641] libphy: Fixed MDIO Bus: probed
[    2.739464] usbcore: registered new interface driver r8152
[    2.744667] usbcore: registered new interface driver cdc_ether
[    2.750459] usbcore: registered new interface driver cdc_subset
[    2.758309] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.763417] ehci-exynos: EHCI EXYNOS driver
[    2.767878] exynos-ehci 12110000.usb: EHCI Host Controller
[    2.773039] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    2.780943] exynos-ehci 12110000.usb: irq 85, io mem 0x12110000
[    2.799314] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    2.804178] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    2.812127] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.819312] usb usb1: Product: EHCI Host Controller
[    2.824158] usb usb1: Manufacturer: Linux 5.0.0-rc3 ehci_hcd
[    2.829790] usb usb1: SerialNumber: 12110000.usb
[    2.834958] hub 1-0:1.0: USB hub found
[    2.838157] hub 1-0:1.0: 3 ports detected
[    2.842981] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.848261] ohci-exynos: OHCI EXYNOS driver
[    2.852580] exynos-ohci 12120000.usb: USB Host Controller
[    2.857801] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    2.865539] exynos-ohci 12120000.usb: irq 85, io mem 0x12120000
[    2.935548] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[    2.942375] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.949564] usb usb2: Product: USB Host Controller
[    2.954320] usb usb2: Manufacturer: Linux 5.0.0-rc3 ohci_hcd
[    2.959954] usb usb2: SerialNumber: 12120000.usb
[    2.965074] hub 2-0:1.0: USB hub found
[    2.968315] hub 2-0:1.0: 3 ports detected
[    2.974309] mousedev: PS/2 mouse device common for all mice
[    2.979695] i2c /dev entries driver
[    2.997967] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV
[    3.011518] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV
[    3.027905] vdd_sd: Bringing 3300000uV into 2800000-2800000uV
[    3.175326] usb 1-1: new high-speed USB device number 2 using exynos-ehci
[    3.337368] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176, bcdDevice= 2.00
[    3.344125] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.351217] usb 1-1: Product: 802.11n WLAN Adapter
[    3.355982] usb 1-1: Manufacturer: Realtek
[    3.360052] usb 1-1: SerialNumber: 00e04c000001
[    4.097447] s5m-rtc s2mps14-rtc: registered as rtc0
[    4.101428] s2mps11-clk s2mps11-clk: DMA mask not set
[    4.108715] iommu: Adding device 11f50000.jpeg to group 2
[    4.112690] s5p-jpeg 11f50000.jpeg: Linked as a consumer to 11f10000.sysmmu
[    4.119987] s5p-jpeg 11f50000.jpeg: encoder device registered as /dev/video30
[    4.126895] s5p-jpeg 11f50000.jpeg: decoder device registered as /dev/video31
[    4.133822] s5p-jpeg 11f50000.jpeg: Samsung S5P JPEG codec
[    4.139502] iommu: Adding device 11f60000.jpeg to group 3
[    4.144661] s5p-jpeg 11f60000.jpeg: Linked as a consumer to 11f20000.sysmmu
[    4.151922] s5p-jpeg 11f60000.jpeg: encoder device registered as /dev/video32
[    4.158850] s5p-jpeg 11f60000.jpeg: decoder device registered as /dev/video33
[    4.165797] s5p-jpeg 11f60000.jpeg: Samsung S5P JPEG codec
[    4.171999] iommu: Adding device 11000000.codec to group 4
[    4.177167] s5p-mfc 11000000.codec: Linked as a consumer to 11200000.sysmmu
[    4.183662] s5p-mfc 11000000.codec: Linked as a consumer to 11210000.sysmmu
[    4.207898] s5p-mfc 11000000.codec: preallocated 16 MiB buffer for the firmware and context buffers
[    4.215603] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[    4.224220] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[    4.234744] s5p-mfc 11000000.codec: decoder registered as /dev/video10
[    4.241217] s5p-mfc 11000000.codec: encoder registered as /dev/video11
[    4.249560] iommu: Adding device 13e00000.video-scaler to group 5
[    4.254688] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu
[    4.262756] iommu: Adding device 13e10000.video-scaler to group 6
[    4.268571] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu
[    4.280489] exynos-tmu 10060000.tmu: Linked as a consumer to regulator.7
[    4.286735] exynos-tmu 10064000.tmu: Linked as a consumer to regulator.7
[    4.293368] exynos-tmu 10068000.tmu: Linked as a consumer to regulator.7
[    4.300078] exynos-tmu 1006c000.tmu: Linked as a consumer to regulator.7
[    4.306713] exynos-tmu 100a0000.tmu: Linked as a consumer to regulator.7
[    4.313295] device-mapper: uevent: version 1.0.3
[    4.317348] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[    4.326423] cpu cpu0: Linked as a consumer to regulator.44
[    4.330976] cpu cpu0: Dropping the link to regulator.44
[    4.336803] cpu cpu0: Linked as a consumer to regulator.44
[    4.348252] cpu cpu4: Linked as a consumer to regulator.40
[    4.360239] sdhci: Secure Digital Host Controller Interface driver
[    4.364962] sdhci: Copyright(c) Pierre Ossman
[    4.369468] Synopsys Designware Multimedia Card Interface Driver
[    4.375813] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    4.382212] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    4.388537] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    4.393923] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 87,64 bit host data width,64 deep fifo
[    4.403232] dwmmc_exynos 12200000.mmc: Linked as a consumer to regulator.18
[    4.410143] dwmmc_exynos 12200000.mmc: Linked as a consumer to regulator.3
[    4.417023] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq
[    4.439815] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    4.460919] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    4.466381] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    4.472771] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    4.478152] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 88,64 bit host data width,64 deep fifo
[    4.487465] dwmmc_exynos 12220000.mmc: Linked as a consumer to regulator.19
[    4.494380] dwmmc_exynos 12220000.mmc: Linked as a consumer to regulator.13
[    4.516710] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    4.542174] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    4.552482] mmc0: new HS200 MMC card at address 0001
[    4.556576] mmcblk0: mmc0:0001 016G92 14.7 GiB 
[    4.561032] mmcblk0boot0: mmc0:0001 016G92 partition 1 4.00 MiB
[    4.567037] mmcblk0boot1: mmc0:0001 016G92 partition 2 4.00 MiB
[    4.571607] s5p-secss 10830000.sss: s5p-sss driver registered
[    4.572577] mmcblk0rpmb: mmc0:0001 016G92 partition 3 512 KiB, chardev (244:0)
[    4.578798] hidraw: raw HID events driver (C) Jiri Kosina
[    4.590812]  mmcblk0: p1 p2
[    4.593603] exynos-bus soc:bus_wcore: Linked as a consumer to regulator.41
[    4.600767] exynos-bus soc:bus_wcore: Dropping the link to regulator.41
[    4.613258] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp
[    4.618534] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp
[    4.625204] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp
[    4.632004] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp
[    4.638940] exynos-adc 12d10000.adc: Linked as a consumer to regulator.4
[    4.650246] NET: Registered protocol family 17
[    4.653276] NET: Registered protocol family 15
[    4.657659] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    4.659471] Key type dns_resolver registered
[    4.668822] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[    4.672036] Registering SWP/SWPB emulation handler
[    4.679003] mmcblk1: mmc1:aaaa SL16G 14.8 GiB 
[    4.683922] registered taskstats version 1
[    4.688771]  mmcblk1: p1 p2
[    4.691356] Loading compiled-in X.509 certificates
[    4.702940] Key type encrypted registered
[    4.731102] exynos-hdmi 14530000.hdmi: Linked as a consumer to regulator.6
[    4.737009] exynos-hdmi 14530000.hdmi: Linked as a consumer to regulator.7
[    4.743871] OF: graph: no port node found in /soc/hdmi@14530000
[    4.750036] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations
[    4.757016] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0a64884)
[    4.763645] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0a64f28)
[    4.770297] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered.
[    4.778453] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0a65e3c)
[    4.784947] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.791531] [drm] No driver support for vblank timestamp query.
[    4.961427] Console: switching to colour frame buffer device 240x67
[    4.982561] exynos-drm exynos-drm: fb0:  frame buffer device
[    4.988647] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0
[    4.995976] exynos-dwc3 soc:usb3-0: Linked as a consumer to regulator.9
[    5.002398] exynos-dwc3 soc:usb3-0: Linked as a consumer to regulator.11
[    5.008831] dwc3 12000000.dwc3: Failed to get clk 'ref': -2
[    5.014405] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    5.019571] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[    5.027438] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    5.036588] xhci-hcd xhci-hcd.1.auto: irq 156, io mem 0x12000000
[    5.042805] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    5.050771] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.057956] usb usb3: Product: xHCI Host Controller
[    5.062791] usb usb3: Manufacturer: Linux 5.0.0-rc3 xhci-hcd
[    5.068429] usb usb3: SerialNumber: xhci-hcd.1.auto
[    5.073573] hub 3-0:1.0: USB hub found
[    5.077021] hub 3-0:1.0: 1 port detected
[    5.081096] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    5.086370] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[    5.094008] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0  SuperSpeed
[    5.100634] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.108754] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[    5.116889] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.124076] usb usb4: Product: xHCI Host Controller
[    5.128909] usb usb4: Manufacturer: Linux 5.0.0-rc3 xhci-hcd
[    5.134546] usb usb4: SerialNumber: xhci-hcd.1.auto
[    5.139678] hub 4-0:1.0: USB hub found
[    5.143109] hub 4-0:1.0: 1 port detected
[    5.147958] exynos-dwc3 soc:usb3-1: Linked as a consumer to regulator.9
[    5.154127] exynos-dwc3 soc:usb3-1: Linked as a consumer to regulator.11
[    5.160544] dwc3 12400000.dwc3: Failed to get clk 'ref': -2
[    5.166111] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    5.171299] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 5
[    5.180874] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    5.190665] xhci-hcd xhci-hcd.2.auto: irq 157, io mem 0x12400000
[    5.197312] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    5.205995] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.213640] usb usb5: Product: xHCI Host Controller
[    5.218928] usb usb5: Manufacturer: Linux 5.0.0-rc3 xhci-hcd
[    5.225064] usb usb5: SerialNumber: xhci-hcd.2.auto
[    5.230683] hub 5-0:1.0: USB hub found
[    5.234928] hub 5-0:1.0: 1 port detected
[    5.239523] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    5.245471] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 6
[    5.253582] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0  SuperSpeed
[    5.260682] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.269332] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[    5.278104] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.285811] usb usb6: Product: xHCI Host Controller
[    5.291150] usb usb6: Manufacturer: Linux 5.0.0-rc3 xhci-hcd
[    5.297262] usb usb6: SerialNumber: xhci-hcd.2.auto
[    5.302900] hub 6-0:1.0: USB hub found
[    5.307152] hub 6-0:1.0: 1 port detected
[    5.312485] rtc rtc1: invalid alarm value: 1900-01-11T00:00:00
[    5.318856] s3c-rtc 101e0000.rtc: registered as rtc1
[    5.325428] exynos-bus soc:bus_wcore: Linked as a consumer to regulator.41
[    5.332918] exynos-bus: new bus device registered: soc:bus_wcore ( 84000 KHz ~ 400000 KHz)
[    5.342100] exynos-bus: new bus device registered: soc:bus_noc ( 67000 KHz ~ 100000 KHz)
[    5.350971] exynos-bus: new bus device registered: soc:bus_fsys_apb (100000 KHz ~ 200000 KHz)
[    5.360163] exynos-bus: new bus device registered: soc:bus_fsys (100000 KHz ~ 200000 KHz)
[    5.369161] exynos-bus: new bus device registered: soc:bus_fsys2 ( 75000 KHz ~ 150000 KHz)
[    5.378263] exynos-bus: new bus device registered: soc:bus_mfc ( 96000 KHz ~ 333000 KHz)
[    5.387135] exynos-bus: new bus device registered: soc:bus_gen ( 89000 KHz ~ 267000 KHz)
[    5.395873] exynos-bus: new bus device registered: soc:bus_peri ( 67000 KHz ~  67000 KHz)
[    5.404849] exynos-bus: new bus device registered: soc:bus_g2d ( 84000 KHz ~ 333000 KHz)
[    5.413676] exynos-bus: new bus device registered: soc:bus_g2d_acp ( 67000 KHz ~ 267000 KHz)
[    5.422879] exynos-bus: new bus device registered: soc:bus_jpeg ( 75000 KHz ~ 300000 KHz)
[    5.431809] exynos-bus: new bus device registered: soc:bus_jpeg_apb ( 84000 KHz ~ 167000 KHz)
[    5.441000] exynos-bus: new bus device registered: soc:bus_disp1_fimd (120000 KHz ~ 200000 KHz)
[    5.450405] exynos-bus: new bus device registered: soc:bus_disp1 (120000 KHz ~ 300000 KHz)
[    5.459379] exynos-bus: new bus device registered: soc:bus_gscl_scaler (150000 KHz ~ 300000 KHz)
[    5.468938] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 400000 KHz)
[    5.478076] odroid-audio sound: ASoC: CPU DAI (null) not registered
[    5.484613] odroid-audio sound: snd_soc_register_card() failed: -517
[    5.491945] odroid-audio sound: ASoC: CPU DAI (null) not registered
[    5.492608] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    5.498479] odroid-audio sound: snd_soc_register_card() failed: -517
[    5.505364] dma-pl330 3880000.adma: 	DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    5.520390] s5m-rtc s2mps14-rtc: setting system clock to 2019-01-23T00:05:48 UTC (1548201948)
[    5.541415] vdd_ldo12: disabling
[    5.543866] odroid-audio sound: i2s-hifi <-> samsung-i2s mapping ok
[    5.547044] vdd_ldo16: disabling
[    5.552329] dma-pl330 3880000.adma: PM domain MAU will not be powered off
[    5.558220] vdd_ldo24: disabling
[    5.567584] vdd_ldo28: disabling
[    5.572767] vdd_ldo30: disabling
[    5.580707] ALSA device list:
[    5.583975]   #0: Odroid-XU4
[    5.587996] Freeing unused kernel memory: 1024K
[    5.603476] Run /init as init process
[    5.655427] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    5.689447] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice=92.22
[    5.698183] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.706132] usb 4-1: Product: USB3.0 Hub
[    5.710706] usb 4-1: Manufacturer: GenesysLogic
[    5.741233] hub 4-1:1.0: USB hub found
[    5.745674] hub 4-1:1.0: 2 ports detected
[    5.819308] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    5.981756] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.22
[    5.990211] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.997628] usb 3-1: Product: USB2.0 Hub
[    6.001833] usb 3-1: Manufacturer: GenesysLogic
[    6.061058] hub 3-1:1.0: USB hub found
[    6.065887] hub 3-1:1.0: 2 ports detected
[    6.070330] usb 4-1.2: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[    6.102414] usb 4-1.2: New USB device found, idVendor=05e3, idProduct=0612, bcdDevice=92.12
[    6.111052] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.118626] usb 4-1.2: Product: USB3.0 Hub
[    6.122961] usb 4-1.2: Manufacturer: GenesysLogic
[    6.157227] hub 4-1.2:1.0: USB hub found
[    6.161724] hub 4-1.2:1.0: 4 ports detected
[    6.427310] usb 3-1.2: new high-speed USB device number 3 using xhci-hcd
[    6.491363] usb 6-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    6.520251] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[    6.531491] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    6.541684] usb 6-1: Product: USB 10/100/1000 LAN
[    6.549414] usb 6-1: Manufacturer: Realtek
[    6.556494] usb 6-1: SerialNumber: 000001000000
[    6.566344] usb 3-1.2: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.12
[    6.574948] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.582491] usb 3-1.2: Product: USB2.0 Hub
[    6.586811] usb 3-1.2: Manufacturer: GenesysLogic
[    6.637201] hub 3-1.2:1.0: USB hub found
[    6.641707] hub 3-1.2:1.0: 4 ports detected
[    6.764864] usb 6-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    6.848332] r8152 6-1:1.0 eth0: v1.09.9
[    6.972345] EXT4-fs (mmcblk1p2): mounted filesystem without journal. Opts: (null)
[    6.999311] usb 3-1.2.2: new low-speed USB device number 4 using xhci-hcd
[    7.119874] usb 3-1.2.2: New USB device found, idVendor=0b38, idProduct=0010, bcdDevice= 1.02
[    7.128843] usb 3-1.2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    7.295280] usb 3-1.2.3: new low-speed USB device number 5 using xhci-hcd
[    7.407062] usb 3-1.2.3: New USB device found, idVendor=093a, idProduct=2510, bcdDevice= 1.00
[    7.416009] usb 3-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    7.423944] usb 3-1.2.3: Product: USB Optical Mouse
[    7.429271] usb 3-1.2.3: Manufacturer: PixArt
[    7.443685] NET: Registered protocol family 10
[    7.449321] Segment Routing with IPv6
[    7.473511] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    7.497669] systemd[1]: Detected architecture arm.
[    7.528630] systemd[1]: Set hostname to <odroid>.
[    7.563345] usb 3-1.2.4: new high-speed USB device number 6 using xhci-hcd
[    7.672006] usb 3-1.2.4: New USB device found, idVendor=1058, idProduct=0748, bcdDevice=10.19
[    7.681179] usb 3-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[    7.689210] usb 3-1.2.4: Product: My Passport 0748
[    7.694494] usb 3-1.2.4: Manufacturer: Western Digital
[    7.700153] usb 3-1.2.4: SerialNumber: 575838314139324331313138
[    7.837813] random: systemd: uninitialized urandom read (16 bytes read)
[    7.846312] systemd[1]: Created slice System Slice.
[    7.867442] random: systemd: uninitialized urandom read (16 bytes read)
[    7.875648] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    7.899352] random: systemd: uninitialized urandom read (16 bytes read)
[    7.907492] systemd[1]: Created slice system-getty.slice.
[    7.927458] systemd[1]: Listening on udev Kernel Socket.
[    7.947638] systemd[1]: Listening on Journal Audit Socket.
[    7.967520] systemd[1]: Listening on udev Control Socket.
[    7.987496] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    8.259956] EXT4-fs (mmcblk1p2): re-mounted. Opts: errors=remount-ro
[    8.648227] systemd-journald[277]: Received request to flush runtime journal from PID 1
[    9.106051] random: crng init done
[    9.106062] random: 7 urandom warning(s) missed due to ratelimiting
[    9.140363] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    9.420758] input: HID 0b38:0010 as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.0/0003:0B38:0010.0001/input/input1
[    9.479626] hid-generic 0003:0B38:0010.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 0b38:0010] on usb-xhci-hcd.1.auto-1.2.2/input0
[    9.484545] input: HID 0b38:0010 System Control as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.1/0003:0B38:0010.0002/input/input2
[    9.506547] SCSI subsystem initialized
[    9.543535] input: HID 0b38:0010 Consumer Control as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.1/0003:0B38:0010.0002/input/input3
[    9.543805] hid-generic 0003:0B38:0010.0002: input,hidraw1: USB HID v1.10 Device [HID 0b38:0010] on usb-xhci-hcd.1.auto-1.2.2/input1
[    9.546061] input: PixArt USB Optical Mouse as /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.1.auto/usb3/3-1/3-1.2/3-1.2.3/3-1.2.3:1.0/0003:093A:2510.0003/input/input4
[    9.546335] hid-generic 0003:093A:2510.0003: input,hidraw2: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-xhci-hcd.1.auto-1.2.3/input0
[    9.546456] usbcore: registered new interface driver usbhid
[    9.546461] usbhid: USB HID core driver
[    9.585006] usb-storage 3-1.2.4:1.0: USB Mass Storage device detected
[    9.585455] scsi host0: usb-storage 3-1.2.4:1.0
[    9.585950] usbcore: registered new interface driver usb-storage
[    9.605364] usbcore: registered new interface driver uas
[    9.739821] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.751162] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.829237] rtl8192cu: Chip version 0x10
[    9.917233] rtl8192cu: Board Type 0
[    9.917459] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[    9.917605] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[    9.918206] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[    9.919133] usbcore: registered new interface driver rtl8192cu
[    9.929633] usbcore: registered new interface driver rtl8xxxu
[   10.142882] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   10.595841] scsi 0:0:0:0: Direct-Access     WD       My Passport 0748 1019 PQ: 0 ANSI: 6
[   10.596166] scsi 0:0:0:1: Enclosure         WD       SES Device       1019 PQ: 0 ANSI: 6
[   10.610326] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[   10.610448] scsi 0:0:0:1: Attached scsi generic sg1 type 13
[   10.616020] sd 0:0:0:0: [sda] Spinning up disk...
[   11.615410] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   11.617586] rtl8192cu: MAC auto ON okay!
[   11.651321] .
[   11.652741] rtl8192cu: Tx queue select: 0x05
[   12.431607] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   12.675292] .
[   13.458023] wlan0: authenticate with 2c:0b:e9:be:9c:81
[   13.469748] wlan0: send auth to 2c:0b:e9:be:9c:81 (try 1/3)
[   13.474616] wlan0: authenticated
[   13.699708] sd 0:0:0:0: [sda] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[   13.700004] sd 0:0:0:0: [sda] Write Protect is off
[   13.700010] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
[   13.700304] sd 0:0:0:0: [sda] No Caching mode page found
[   13.706251] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   13.770953]  sda: sda1 sda2 sda3
[   13.773403] sd 0:0:0:0: [sda] Attached SCSI disk
[   33.291813] cryptd: max_cpu_qlen set to 1000
[   33.322645] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   33.656063] wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by 2c:0b:e9:be:9c:81

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 23, 2019 10:21 am

Great progress.
Can I try your Kernel 5.0 on XU4 Ubuntu 18.04 Mate image now?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 23, 2019 10:27 am

odroid wrote:
Wed Jan 23, 2019 10:21 am
Great progress.
Can I try your Kernel 5.0 on XU4 Ubuntu 18.04 Mate image now?
Give it a try, it should run very nice. I like 5.0 better than 4.14 already :)
Here's my config: http://paste.ubuntu.com/p/KKjmXNGC5q/
These users thanked the author memeka for the post:
NC-Tony-Casanova (Tue Dec 31, 2019 3:04 pm)

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 23, 2019 10:55 am

I'm trying a native build now. :D

Code: Select all

sudo apt-get install git gcc g++ build-essential libssl-dev bc flex bison
git clone --depth 1 https://github.com/mihailescu2m/linux -b odroidxu4-5.0.y
cd linux/
Copied your config into arch/arm/configs/ as odroidxu4_defconfig file.

Code: Select all

make odroidxu4_defconfig
make -j8
After compiling, I will post the result to ask you a next step to install modules, zImage, dtb and root ramdisk. ;)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 23, 2019 11:07 am


User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 23, 2019 11:14 am

Ok. I will look into the link.
Which gcc version did you use?
I'm using 7.3.0

Code: Select all

odroid@odroid:~/linux$ gcc --version
gcc (Ubuntu/Linaro 7.3.0-27ubutu1~18.04) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 23, 2019 11:39 am

I've just followed our WiKi page. https://wiki.odroid.com/odroid-xu4/os_i ... _tree_blob

Code: Select all

make -j8
sudo make modules_install
sudo cp -f arch/arm/boot/zImage /media/boot
sudo cp -f arch/arm/boot/dts/exynos5422-odroid*dtb /media/boot
sudo cp .config /boot/config-`make kernelrelease`
sudo update-initramfs -c -k `make kernelrelease`
sudo mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n uInitrd -d /boot/initrd.img-`make kernelrelease` /boot/uInitrd-`make kernelrelease`
sudo cp /boot/uInitrd-`make kernelrelease` /media/boot/uInitrd
sync
sudo reboot
It booted well and Mali GPU works fine. Kodi 17.6 also plays well 1080p/60fps H.264 video :o :D

Code: Select all

odroid@odroid:~$ uname -a
Linux odroid 5.0.0-rc3+ #1 SMP PREEMPT Wed Jan 23 01:50:00 UTC 2019 armv7l armv7l armv7l GNU/Linux

Code: Select all

odroid@odroid:~$ neofetch 
            .-/+oossssoo+/-.                                                    
        `:+ssssssssssssssssss+:`           ------------- 
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 18.04.1 LTS armv7l 
    .ossssssssssssssssssdMMMNysssso.       Host: Hardkernel Odroid XU4 
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.0.0-rc3+ 
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 14 mins 
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 1827 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 4.4.19 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Terminal: /dev/ttySAC2 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: SAMSUNG EXYNOS (Flattened Device Tree) (8)
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   Memory: 506MiB / 1993MiB 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.                                        
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/                                         
  +sssssssssdmydMMMMMMMMddddyssssssss+                                          
   /ssssssssssshdmNNNNmyNMMMMhssssss/                                           
    .ossssssssssssssssssdMMMNysssso.                                            
      -+sssssssssssssssssyyyssss+-                                              
        `:+ssssssssssssssssss+:`                                                
            .-/+oossssoo+/-. 

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 23, 2019 11:42 am

Can you please test the sound?

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 23, 2019 11:45 am

Yes, HDMI sound is okay with pre-installed Kodi 17.6 :)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 23, 2019 8:25 pm

Great to hear sound is working.

New update: I've rebased the code on mali drivers r20p0 (same used on r14p0), previously i was using r19p0.
Also added rootless gpiomem driver and spi1 too.

As a general rule, I usually rebase when new patches are added or mainline is updated to keep a nice structure in the patches on top of mainline.
Unfortunately this means everyone needs to redownload the source... :oops:

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 24, 2019 7:14 am

new: jpeg hw decoder

i am working to get the jpeg hw decoder in a usable state.
with a small patch i was able to get it to decode, but there are still small issues because of some missing v4l2 ioctls. i'll try implementing and see how that goes :)

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Jan 24, 2019 9:25 am

Nice update!

But, I found one strange issue with ffplay(SDL). The video rendering colors are washed out. Kodi has no such issue.
I switched to 4.14.94 and there was no issue either.

Is this issue related to the missing v4l2 ioctls?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 24, 2019 2:58 pm

odroid wrote:
Thu Jan 24, 2019 9:25 am
Nice update!

But, I found one strange issue with ffplay(SDL). The video rendering colors are washed out. Kodi has no such issue.
I switched to 4.14.94 and there was no issue either.

Is this issue related to the missing v4l2 ioctls?
No, no issues with v4l2 ioctls. I've added a patch that I hope to fix this issue. Please clone repository again and compile to test.

I've fixed the JPEG decoder as well, it can now hardware decode MJPEG. I've tested with this video file:

Code: Select all

$ mediainfo grill-mjpeg.mov
General
Complete name                            : grill-mjpeg.mov
Format                                   : QuickTime
Format/Info                              : Original Apple specifications
File size                                : 34.9 MiB
Duration                                 : 17 s 400 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 16.8 Mb/s
Movie_More                               : Quicktime for Linux
Encoded date                             : UTC 2003-11-17 17:17:37
Tagged date                              : UTC 2003-11-17 17:17:37
Copyright                                : Made with Cinelerra for Linux

Video
ID                                       : 1
Format                                   : JPEG
Codec ID                                 : mjpa
Duration                                 : 17 s 400 ms
Bit rate mode                            : Variable
Bit rate                                 : 15.3 Mb/s
Width                                    : 720 pixels
Height                                   : 576 pixels
Display aspect ratio                     : 5:4
Frame rate mode                          : Constant
Frame rate                               : 25.000 FPS
Standard                                 : PAL
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan type, store method                  : Separated fields (2 fields per block)
Scan order                               : Top Field First
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 1.476
Stream size                              : 31.7 MiB (91%)
Language                                 : English
Encoded date                             : UTC 2003-11-17 17:17:37
Tagged date                              : UTC 2003-11-17 17:17:37

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 17 s 400 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 3.19 MiB (9%)
Language                                 : English
Encoded date                             : UTC 2003-11-17 17:17:37
Tagged date                              : UTC 2003-11-17 17:17:37
and I was able to play it with:

Code: Select all

gst-launch-1.0 filesrc location=grill-mjpeg.mov ! parsebin ! v4l2jpegdec ! v4l2convert capture-io-mode=dmabuf ! kmssink
CPU usage was 17% for the fully accelerated pipeline, while using jpegdec ! videoconvert results in 30% CPU usage and v4l2jpegdec ! videoconvert results in 20% CPU usage.

I hope it will be useful with cameras that can stream high-res in MJPEG format ;)
I did not test the JPEG encoder, it might work as well...

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Jan 24, 2019 5:29 pm

Can I use the same Kernel config?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 24, 2019 5:59 pm

odroid wrote:
Thu Jan 24, 2019 5:29 pm
Can I use the same Kernel config?
Yes of course

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Jan 24, 2019 6:03 pm

Ok. The ffplay color issue has gone away. :)
I will try some MPEG4/MPEG2/H.264 videos by early next week.

BTW, we will send you two different cameras for your development next week.
https://www.hardkernel.com/shop/ocam-5m ... -0-camera/
https://www.hardkernel.com/shop/odroid-usb-cam-720p/

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 24, 2019 8:34 pm

odroid wrote:
Thu Jan 24, 2019 6:03 pm
Ok. The ffplay color issue has gone away. :)
I will try some MPEG4/MPEG2/H.264 videos by early next week.
Good to hear :)
odroid wrote:
Thu Jan 24, 2019 6:03 pm
BTW, we will send you two different cameras for your development next week.
https://www.hardkernel.com/shop/ocam-5m ... -0-camera/
https://www.hardkernel.com/shop/odroid-usb-cam-720p/
I don't think it's needed, I have one Logitech C270 webcam (similar to the odroid-usb-cam-720p), and an ELP webcam that can do 720p H.264 (http://www.elpcctv.com/h264-hd-720p-usb ... p-227.html). They are USB2.0 tho`... :roll:

User avatar
rooted
Posts: 7340
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 497 times
Been thanked: 138 times
Contact:

Re: Kernel 5.0 development thread

Unread post by rooted » Thu Jan 24, 2019 11:57 pm

Might still be cool to have the Ocam since it's USB 3.0

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Sat Jan 26, 2019 7:47 pm


Lowest CPU playing 1080p videos, less than half of the 4.14 kernel :)
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:21 pm)

User avatar
rooted
Posts: 7340
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 497 times
Been thanked: 138 times
Contact:

Re: Kernel 5.0 development thread

Unread post by rooted » Sat Jan 26, 2019 11:21 pm

memeka wrote:

Lowest CPU playing 1080p videos, less than half of the 4.14 kernel :)
Nice Image

How is htop showing the big.LITTLE of the cores?

User avatar
mad_ady
Posts: 7568
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 394 times
Been thanked: 300 times
Contact:

Re: Kernel 5.0 development thread

Unread post by mad_ady » Sun Jan 27, 2019 12:59 am

Yup, that looks nice :)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Sun Jan 27, 2019 1:28 am

@rooted it’s the armbian fork of htop

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Jan 29, 2019 2:32 pm

Updates:

* rebased on mainline 5.0-rc4
* tested gstreamer with dmabuf_import
* tested kodi with dmabuf_import (DRMPRIME)
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:21 pm)

dante6913
Posts: 96
Joined: Sat Oct 01, 2016 7:16 am
languages_spoken: english, Portuguese
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by dante6913 » Wed Jan 30, 2019 1:01 am

I'm getting an error with
"sudo make modules_install
sudo cp -f arch/arm/boot/zImage /media/boot"

modules_install tells me that can't find .ko files
and sudo cp -f arch/arm/boot/zImage /media/boot tells me that this file doesn't exist. So I was not able to build the kernel and boot with it.
Is there any date for releasing a image of ubuntu 18.04 with kernel 5.0, so the less skilled could test it?
Thanks

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Jan 30, 2019 2:17 am

Image after 5.0 is officially released and binary driver redistribution rights are sorted :)

User avatar
odroid
Site Admin
Posts: 33676
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 508 times
Been thanked: 506 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Jan 30, 2019 8:31 am

dante6913 wrote:
Wed Jan 30, 2019 1:01 am
I'm getting an error with
"sudo make modules_install
sudo cp -f arch/arm/boot/zImage /media/boot"

modules_install tells me that can't find .ko files
and sudo cp -f arch/arm/boot/zImage /media/boot tells me that this file doesn't exist. So I was not able to build the kernel and boot with it.
Is there any date for releasing a image of ubuntu 18.04 with kernel 5.0, so the less skilled could test it?
Thanks
Was there any error while building kernel with "make -j8" ?
Do you have enough space on eMMC/SD?

dante6913
Posts: 96
Joined: Sat Oct 01, 2016 7:16 am
languages_spoken: english, Portuguese
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by dante6913 » Wed Jan 30, 2019 9:52 pm

odroid wrote:
Wed Jan 30, 2019 8:31 am
dante6913 wrote:
Wed Jan 30, 2019 1:01 am
I'm getting an error with
"sudo make modules_install
sudo cp -f arch/arm/boot/zImage /media/boot"

modules_install tells me that can't find .ko files
and sudo cp -f arch/arm/boot/zImage /media/boot tells me that this file doesn't exist. So I was not able to build the kernel and boot with it.
Is there any date for releasing a image of ubuntu 18.04 with kernel 5.0, so the less skilled could test it?
Thanks
Was there any error while building kernel with "make -j8" ?
Do you have enough space on eMMC/SD?

Thanks odroid, indeed I got a warning about low space (but I tthought that was enought) .
I'm going to use a bigger sd card and try again in the weekend.

MastaG
Posts: 311
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Thu Jan 31, 2019 12:40 am

So memeka is on fire again!

two quick questoins:

1. There seems to be a open driver for the arm gpu: https://www.phoronix.com/scan.php?page= ... eview-Mesa
The article says that the kernel bits are still missing.. but has anyone looked at this? perhaps it contains fixes for our binary driver as well..
EDIT: Here's the driver: https://gitlab.freedesktop.org/panfrost/mali_kbase
EDIT2: They seem to be having fun: https://freenode.irclog.whitequark.org/ ... 2019-01-06

2. Is the analog headphone jack working in this kernel? (for the Xu3)

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 31, 2019 3:22 am

1. Not working
https://gitlab.freedesktop.org/panfrost/mesa/issues/12

2. Did not test on xu3. Maybe you can and let us know :)

User avatar
AreaScout
Posts: 1251
Joined: Sun Jul 07, 2013 3:05 am
languages_spoken: german, english
ODROIDs: X2, U3, XU3, C2, HiFi Shield, XU4, XU4Q,
N1, Go, VU5A, Show2, CloudShell2,
H2, N2, VU7A, VuShell
Has thanked: 46 times
Been thanked: 151 times
Contact:

Re: Kernel 5.0 development thread

Unread post by AreaScout » Thu Jan 31, 2019 4:13 am

memeka wrote:
Thu Jan 31, 2019 3:22 am
1. Not working
https://gitlab.freedesktop.org/panfrost/mesa/issues/12

2. Did not test on xu3. Maybe you can and let us know :)
apropos XU3 did you run kernel 5.0 on it ? enabling the display port would be of interest because that driver DOES support NV12/21 planes aka direct to plane for Kodi ?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Jan 31, 2019 4:19 am

@Areascout
1. Sure direct to plane, but it would still have the same bugs as egl drmprime has now.
2. On Samsung mainline todo: Odroid XU3 (exynos5422) Display Port support. Needs a hardware fix (like DP->HDMI converter with external power supply provided from USB port) and some research. no idea what’s about that hw fix, but I don’t think it’s working

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Feb 01, 2019 12:10 pm

UPDATES

* mali driver updated to r21p0

Please note r21p0 driver DOES NOT WORK with previous mali binary blobs.
So before compiling the kernel, please revert the changes in this patch: https://github.com/mihailescu2m/midgard ... b955.patch

EDIT: mpv video tests

* output nv12 to GPU for conversion: mpv -v --no-audio ~/Videos/bunny_trailer-1080p.mov --vo=gpu --gpu-context=drm
output log: http://paste.ubuntu.com/p/3RX8DrTDtz/
cpu usage avg: 22%

* output nv12 direct-to-plane (no gpu) + sw conversion: mpv -v --no-audio ~/Videos/bunny_trailer-1080p.mov --vo=drm
output log: http://paste.ubuntu.com/p/Zs2wzbCBX5/
cpu usage avg: 35%

* output nv12 direct-to-plane (no gpu) + gscaler conversion: mpv -v --no-audio ~/Videos/bunny_trailer-1080p.mov --vo=drm using branched ffmpeg
output log:
cpu usage avg:
These users thanked the author memeka for the post:
pinkodroid (Mon Apr 15, 2019 5:22 pm)

MastaG
Posts: 311
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 01, 2019 6:52 pm

Hi memeka I still need to test it on my Xu3.
However I'm using these mali blobs from arm: malit62xr12p004rel0linux1wayland.tar.gz GNU/Linux armhf Wayland/GBM/DRM
Are these compatible with the r21p0 kernel drivers?
If not should I downgrade the kernel to r20p or are there other drivers which support wayland?

I'm running Fedora 29 with Gnome on wayland..

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Feb 01, 2019 8:53 pm

@MastaG, r12 wouldn't work.
r21 kernel drivers removed all previous compatibility :( so best is to go back to r20 by reverting the diff above.
no other wayland drivers either :(

MastaG
Posts: 311
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 01, 2019 9:11 pm

@memeka
Thanks, I'll revert back then.
Regarding these binary drivers, in the past I've asked arm to update the wayland/gbm/drm drivers to support a more recent libgbm (as the current one is based on mesa 17).
They said they're no longer putting efforts in the drivers for our gpu and pointed me to Samsung/Hardkernel.
Now I see HK has some updated blobs..compared to the ones on the arm website.
Does that mean they have the source of the binary blobs?
If yes.. couldn't they just update them to make it compatible with r21p0 and bump the libgbm part to mesa 19 :)
Also wayland support in the bigmali.tar drivers would be nice as well...

<complain mode off>

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Feb 01, 2019 9:57 pm

@MastaG

AFAIR HK has X11 & fbdev license from ARM so it cannot distribute wayland blobs. Not even sure they have access to the wayland sources.
Also, if ARM did not update gbm API in their sources, HK cannot do anything, even if they would have access...

So there are 2 options:
1. use my libgbm_compat :)
2. wait for panfrost support https://gitlab.freedesktop.org/panfrost/mesa/issues/12

MastaG
Posts: 311
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 01, 2019 10:43 pm

@memeka
yes, I'm using your libgbm_compat and extended it a bit.. adding more functions returning null, thanks for that btw :)
still an updated driver would be nice to have.

I read a lot of phoronix and it seems gnome 3.32 will carry even more performance fixes for wayland compared to 3.30 (which I'm using now with libgbm_compat).
So I'm looking forward on upgrading to Fedora 30.. will probably switch to alpha soon.

@odroid
Any plans for obtaining a license from arm for using the wayland drivers?
Canonical switched ubuntu to gnome as well and are also putting efforts in landing wayland improvements.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Mon Feb 04, 2019 3:23 pm

Updates

* rebased on mainline 5.0-rc5
* patched mali kernel driver r21p0 to work with older blobs

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 58 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Mon Feb 04, 2019 9:23 pm

Just for the fun, I tried panfrost:

Code: Select all

$ LD_LIBRARY_PATH=/usr/local/panfrost/lib/arm-linux-gnueabihf ./eglinfo 
panfrost: Using kbase UK version 11.0, fd 6
gbm = 0x42c558
screen is valid!
trying to initialize EGL
EGL initialized
EGL API version: 1.4
EGL vendor string: Mesa Project
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES 
EGL extensions string:
    EGL_EXT_image_dma_buf_import EGL_KHR_cl_event2 EGL_KHR_config_attribs
    EGL_KHR_create_context EGL_KHR_create_context_no_error
    EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses
    EGL_KHR_gl_colorspace EGL_KHR_gl_renderbuffer_image
    EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image
    EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base
    EGL_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
    EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float
    EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image
    EGL_MESA_image_dma_buf_export EGL_WL_bind_wayland_display
Configurations:
     bf lv colorbuffer dp st  ms    vis   cav bi  renderable  supported
  id sz  l  r  g  b  a th cl ns b    id   eat nd gl es es2 vg surfaces 
---------------------------------------------------------------------
0x01 32  0  8  8  8  8  0  0  0 0 0x34325241--         y  y  y     win
0x02 32  0  8  8  8  8 16  0  0 0 0x34325241--         y  y  y     win
0x03 32  0  8  8  8  8 24  8  0 0 0x34325241--         y  y  y     win
0x04 32  0  8  8  8  8 32  0  0 0 0x34325241--         y  y  y     win
0x05 24  0  8  8  8  0  0  0  0 0 0x34325258--         y  y  y     win
0x06 24  0  8  8  8  0 16  0  0 0 0x34325258--         y  y  y     win
0x07 24  0  8  8  8  0 24  8  0 0 0x34325258--         y  y  y     win
0x08 24  0  8  8  8  0 32  0  0 0 0x34325258--         y  y  y     win
Just eglinfo is working :)

Post Reply

Return to “Ubuntu”

Who is online

Users browsing this forum: No registered users and 6 guests