Posts by GDPR-1


    lrusak  chewitt  codesnake before I start testing and maybe do a PR, any reason for the outdated driver ? just want to be sure i'm not missing anything :)


    Ask amlogic. The kernel is supplied by Amlogic and they screwed up big time many things. You can go ahead and try to backport a recent version. Just make sure to use git and keep the git history. cherry-pick might help.

    Good luck.

    Can you please try most recent alpha LibreELEC-Odroid_C2.aarch64-7.90.009.img.gz. For lirc to work with mceusb you need a file called /storage/.config/lircd.conf
    lircd.conf.mceusb

    However in 009 I had lots of problems with mceusb. I worked around it here:
    ODROID Forum • View topic - LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs

    About your HDMI connect problem. Let's see if 009 fixes it otherwise we can try this patch from kszaq:
    LibreELEC.tv/hdmi_always_connected.patch at 7.0.2.009 · kszaq/LibreELEC.tv · GitHub

    I really think that you are serious. To be honest I wasn't sure at first. Anyway, in my opinion if you want to build something and you want LibreELEC to support your hardware a forum thread is not the right way to go. Create your company, build some kind of product. Read this: Sponsor – LibreELEC
    And get in touch with the LibreELEC Team by email.

    no offense 2ami but if he hires a whole LE Team for software development you are not gonna buy it because its not the cheapest. Some other chinese box seller will bring out nearly the same product without software support but thanks to open source software he doesn't have to. And its not the fault of FOSS here, its the consumers fault. If it wasn't for Wetek there would probably be no Kodi support for Amlogic yet.

    What about Hardkernel. They are based in South Korea.

    Well and here is your problem and it doesn't really distinguish you from any of the other chinese box manufacturers, no offense. You just want to build a cheap device and hope others like kszaq will do the software support for free. There is a reason why Wetek devices are more expensive but without Wetek there probably wouldn't be proper Kodi support.

    Please make an effort to consider supporting development. Think about paying developers to develop and support software. You'll have to spend a lot of money for someone that will make his work public and free. Do the math.

    And after you've invested that money another chinese manufacturer comes a long and builds a similar device for half the price.

    Ok, I get it. I read his commit and understand the use of TARGET_KERNEL_ARCH for the S905 builds keeping TARGET_KERNEL_ARCH=arm64 and TARGET_ARCH=arm, with some linux drivers forcefully compiling using gcc-linaro-aarch64-elf. Sounds like a great plan! Please keep us posted as it progresses.

    Thanks JoKeRzBoX for the motivation ;). The idea is very good to use 32bit libs userspace. I've wanned this for a long time but I hate repacking. Using a precompiled toolchain is currently the fastest and cleanest way to implement this without changing the whole build system. To be honest I'm not entirely happy with this solution because we need gcc 4.9 toolchain for uboot but gcc 4.9 is pretty old and there were issues with one RTL driver to compile.

    I've made my own build for Odroid C2 ODROID Forum • View topic - LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs
    My main motivation was libwidevine and Amazon VOD.


    I tried it with cec-client, and it seems to be some sort of timing issue ?
    Ubuntu Pastebin (cec-client log)

    If the Pi CEC client is marked as active source, it is getting keys. Then at message 11850, the tv is turned off, then at 17327 it is turned back on. Then it is not getting key presses until i type "as" into cec-client, marking it as an active source again - and at that moment, i am getting the key presses again (message 39055 and later).

    This is with LE 7.0.1, Samsung 55JU6400, firmware 1470.


    You are probably correct. Thats what I assume. Unfortunately I don't have a TV with that issue. Amlogic CEC driver had a similar issue (read my previous post). But I can only speculate.

    While developing the CEC driver for Amlogic S905 with @gda I saw a similar issue on my Samsung TV's. Took me a while to figure it out. I'm not 100% sure but in my case Kodi was sending CEC messages too fast and some got dropped by the TV. We fixed in in the kernel driver by delaying the CEC write a little bit. Remember CEC is a very sloooooow protocol according to the CEC spec.

    Don't get emotional with Samsung. It might be a feature not a bug. Anyone with S905 and Recent samsung firmware having this issue please ping me.