Posts by AA666

Quote from jernej

What codecs? Anyway, GPU has nothing to do with video decoding, if codec is one of the supported ones (MPEG2, H264, HEVC).

After more deeply testing found that freezing occurs also in various Kodi menus - video files scrolling or weather plugin, not only during video playback.

So, looks like its not related to codecs, but related to some general video mem management.

From time to time 'taxi' artefact appears, like first weather row as on screen below:

Upd: Just tested build LibreELEC-A64.arm-9.80-devel-20200426023927-38764c8 and it also affected:

[   68.186742] lima 1c40000.gpu: mmu page fault at 0x2275800 from bus id 0 of type read on ppmmu0
[   68.187530] lima 1c40000.gpu: pp task error 0 int_state=0 status=1
[   68.187537] lima 1c40000.gpu: pp task error 1 int_state=0 status=0
[   68.187542] lima 1c40000.gpu: mmu resume

Hi Jernej,

Found picture freezing during rewind or ff on Pine A64+ on various video formats, found in dmesg only following:

[ 83.647007] lima 1c40000.gpu: mmu page fault at 0x933c00 from bus id 0 of type read on ppmmu0
[ 83.648756] lima 1c40000.gpu: pp task error 0 int_state=0 status=5
[ 83.648762] lima 1c40000.gpu: pp task error 1 int_state=0 status=0
[ 83.648767] lima 1c40000.gpu: mmu resume

Found this after upgrade to one of latest builds:

LibreELEC-A64.arm-9.80-nightly-20200605-44747ec-pine64-plus

Tested this issue on one of previous builds and this one not affected:

LibreELEC-A64.arm-9.80-nightly-20200308-9f00cd2-pine64-plus

Just let me know if you need more information.

Thanks, Jernej, of course its always better to be aligned with policy and I'll go by hard way, I'll PM you in case if I stuck somewhere.

Quote from jernej

AA666 I can include first patch (do you plan to send it to Linux?) but I don't like to merge second one. Reason is that Pine64 doesn't have IR soldered. This is job for DT overlay, which can be done with dtoverlay and configfs functionality included in kernel, but I can't give you any tutorial at this time.

I would like to apply it to mainline, but it will be long process with some probability of success. Meanwhile we can test it with others A64 boards.

Actually Pine board has soldered IR header, where you can just insert IR diode. I did it some time ago and IR start to work with original BSP without any further manipulations. At the moment I can't see any drawbacks if we leave IR enabled, but IR diode will not be inserted.

Here is IR receiver installation guide for Pine: pine64_ir_receiver_installation_guide.pdf

Quote from igloo

Hi,

i have orangepi lite (H3 device)

my problem with fixed ip address is still not solved, but my remote (vu+ remote) is working all buttons except the most important one KEY_SELECT, ie the OK button.

i followed the procedure on wiki (hard way) and added this udev rule to make it work on kodi

Code

 : > /storage/.config/udev.rules.d/98-eventlircd.rules

is anyone facing this OK key not working? it works with test procedure but not in kodi.

Code

libreelec:~ # ir-keytable -c -w /storage/.config/rc_keymaps/my_remote
Read my_remote table
Old keytable cleared
Wrote 7 keycode(s) to driver
Protocols changed to rc-6 

libreelec:~ # ir-keytable -r
scancode 0x80521058 = KEY_UP (0x67)
scancode 0x80521059 = KEY_DOWN (0x6c)
scancode 0x8052105b = KEY_RIGHT (0x6a)
scancode 0x8052105c = KEY_SELECT (0x161)
scancode 0x8052900c = KEY_POWER (0x74)
scancode 0x8052900d = KEY_MUTE (0x71)
scancode 0x8052905a = KEY_LEFT (0x69)
Enabled protocols: rc-6 

Display More

igloo just change in your my_remote KEY_SELECT to KEY_OK and it will be OK

jernej could you please add IR receiver to A64 family as well?

I created 2 small patches for this, 1st to add IR pins to A64 device tree:

99-add-ir-receiver-for-a64.patch.txt

and 2nd to enable IR on all Pine64 boards:

99-enable-ir-receiver-pine64.patch.txt

It works for my PineA64+ board and should work for all A64 family, because pins and IRQ are the same.

lumpi you can put ir-keytable -a /storage/.config/rc_maps.cfg into /storage/.config/autostart.sh to load your rc map after reboot. Don't forget to chmod +x on autostart.sh file.

Quote from lumpi

I guess I'm just too simple for this remote control stuff...

I dug out an Asus PC-39, which is RC5 and compatible with the sunxi receiver and part of the standard remotes...

no luck, well not completely, see what happens:

Code

LibreELEC:~ # ir-keytable -c -w /usr/lib/udev/rc_keymaps/asus_pc39 
Read asus_pc39 table
Old keytable cleared
Wrote 39 keycode(s) to driver
Protocols changed to rc-5 

when I'm pressing a button nothing seems to happen on the big screen, but at least the button presses seem to arrive properly:

Code

LibreELEC:~ # ir-keytable -p rc-5 -t
Protocols changed to rc-5 
Testing events. Please, press CTRL-C to abort.
1835.957557: event type EV_MSC(0x04): scancode = 0x822
1835.957557: event type EV_KEY(0x01) key_down: KEY_EXIT(0x00ae)
1835.957557: event type EV_SYN(0x00).
1836.069036: event type EV_MSC(0x04): scancode = 0x822
1836.069036: event type EV_SYN(0x00).
1836.180619: event type EV_MSC(0x04): scancode = 0x822
1836.180619: event type EV_SYN(0x00).
1836.430065: event type EV_KEY(0x01) key_up: KEY_EXIT(0x00ae)
1836.430065: event type EV_SYN(0x00).
1840.541220: event type EV_MSC(0x04): scancode = 0x808
1840.541220: event type EV_KEY(0x01) key_down: KEY_UP(0x0067)
1840.541220: event type EV_SYN(0x00).
1840.652828: event type EV_MSC(0x04): scancode = 0x808
1840.652828: event type EV_SYN(0x00).
1840.764406: event type EV_MSC(0x04): scancode = 0x808
1840.764406: event type EV_SYN(0x00).
1841.010067: event type EV_KEY(0x01) key_up: KEY_UP(0x0067)
1841.010067: event type EV_SYN(0x00).
1842.109146: event type EV_MSC(0x04): scancode = 0x804
1842.109146: event type EV_KEY(0x01) key_down: KEY_DOWN(0x006c)
1842.109146: event type EV_SYN(0x00).
1842.220762: event type EV_MSC(0x04): scancode = 0x804
1842.220762: event type EV_SYN(0x00).
1842.332367: event type EV_MSC(0x04): scancode = 0x804
1842.332367: event type EV_SYN(0x00).
1842.580058: event type EV_KEY(0x01) key_up: KEY_DOWN(0x006c)
1842.580058: event type EV_SYN(0x00).

Display More

I guess I should call it a day and try again tomorrow, or maybe im firing up the raspi with some suitable RX, lets see...

OK giving up for today, found a second rc_maps.cfg in /etc , didn't manage making this editable, but keeping it another task for tomorrow, trying to add this line to the end:

Code

sunxi-ir    *        asus_pc39

neither irw nor LibreELEC:~ # irw /run/lirc/lircd produce any output, strange...

Display More

lumpi you can store custom maps and configs in /storage/.config folder, here is a guide for Amlogic devices, but it is similar for Allwinner:

LE9.0 remote configs ir-keytable Amlogic devices

I make my remote works with Kodi by disabling eventlircd as well:

: > /storage/.config/udev.rules.d/98-eventlircd.rules

Taken from here:

LE9.0 remote configs ir-keytable Amlogic devices

Thanks for suggestion, will do it in this way.

Hope Jernej is still here...

I compiled latest hw_dec_ffmpeg branch for Pine A64+ and it works as described on my 2Gb board.

Also I created two small patches to enable sunxi-ir on pine, perhaps you can include them into your branch, as I never submitted anything to mainline.