Posts by koenkooi


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

    The verb 'building' is a bit misleading here, 'selling' would be a better fit. If you manufacture cheap electronics assembly and parts are the big cost factor, but don't forget about:

    • designing the thing, NRE
    • QA testing during production
    • Warranty/RMA


    And as you mentioned above, software support.

    And yes, Penang is a nice place, my wife has to travel there from time to time to troubleshoot things at their factory there. I wouldn't mind some roti canai right now :)

    Hmm.. What level of support is missing?

    Are you saying that ARM haven't published MALI-T820 interfaces, or that Amlogic haven't released any devkit for the S912?

    Last time I checked the userspace libraries are missing from the amlogic site. It could be that the binaries ARM ltd publishes will "Just Work(TM)", but afaik no one has tried that yet.


    Please kszaq build something for S912. I believe you can easily do that.

    No, he can't. The needed mali userspace hasn't been published yet. The s905 and s905x are similar enough to support in a single build, the s912 is too different to do that.
    Which also means that anyone can copy the S905 subdir in LE to S912 and start hacking without having to coordinate with anyone. Provided the mali blob shows up soon.


    With the image from 2016-10-03-devel and this dtb gxbb_p200_2G_beelink_minimxIII.dtb on a Beelink mx III CEC doesn't work anymore:

    Code
    mxIII:~ # dmesg | grep -i cec[    3.394487@0] input: cec_input as /devices/virtual/input/input2[    3.394693@0] cectx aocec: aml_cec_probe(): no hdmirx reg resource[    3.394696@0] cectx aocec: aml_cec_probe(): no hhi reg resource[    3.394805@0] cectx aocec: aml_cec_probe(): can't find hdmirx[    3.395949@0] cec: wake up flag:0

    And

    Code
    mxIII:~ # grep -i cec .kodi/temp/kodi.log 11:31:28 T:548185489408  NOTICE: Register - new cec device registered on cec->AOCEC: CEC Adapter (0000:0000)11:31:28 T:547828908256   ERROR: CecLogMessage - AllocateLogicalAddresses - failed to allocate device '0', type 'playback device'11:31:28 T:547828908256   ERROR: CecLogMessage - failed to find a free logical address for the client11:31:28 T:547828908256   ERROR: CecLogMessage - failed to register the new CEC client - cannot allocate the requested device types11:31:28 T:547828908256   ERROR: CecLogMessage - failed to register a CEC client11:31:28 T:547820519648   ERROR: OpenConnection - could not opening a connection to the CEC adapter

    The topology is mxIII -> Onkyo receiver -> Samsung TV. It was previously working quite well, but after upgrading it by putting the img.gz in ~/.update CEC stopped working.

    This seems to be a side effect of running from eMMC, running from uSD doesn't show this problem. And better, running from uSD will use eMMC as storage, so all my settings and libraries are being picked up.

    With the image from 2016-10-03-devel and this dtb gxbb_p200_2G_beelink_minimxIII.dtb on a Beelink mx III CEC doesn't work anymore:

    Code
    mxIII:~ # dmesg | grep -i cec[    3.394487@0] input: cec_input as /devices/virtual/input/input2[    3.394693@0] cectx aocec: aml_cec_probe(): no hdmirx reg resource[    3.394696@0] cectx aocec: aml_cec_probe(): no hhi reg resource[    3.394805@0] cectx aocec: aml_cec_probe(): can't find hdmirx[    3.395949@0] cec: wake up flag:0

    And

    Code
    mxIII:~ # grep -i cec .kodi/temp/kodi.log 11:31:28 T:548185489408  NOTICE: Register - new cec device registered on cec->AOCEC: CEC Adapter (0000:0000)11:31:28 T:547828908256   ERROR: CecLogMessage - AllocateLogicalAddresses - failed to allocate device '0', type 'playback device'11:31:28 T:547828908256   ERROR: CecLogMessage - failed to find a free logical address for the client11:31:28 T:547828908256   ERROR: CecLogMessage - failed to register the new CEC client - cannot allocate the requested device types11:31:28 T:547828908256   ERROR: CecLogMessage - failed to register a CEC client11:31:28 T:547820519648   ERROR: OpenConnection - could not opening a connection to the CEC adapter

    The topology is mxIII -> Onkyo receiver -> Samsung TV. It was previously working quite well, but after upgrading it by putting the img.gz in ~/.update CEC stopped working.


    ermethic We use the same CEC implementation in our builds: Amlogic driver with support for libCEC from Raybuntu.

    Speaking of CEC, the displayed name is hardcoded in the .dts file to 'Mbox', would you accept a patch to hardcode it to something like 'Kodi'? A better way would be to have the LE buildsystem change it, but I haven't figured out how to do that yet :)

    Do you have the nouveau changes in a git repo anywhere?

    Yes, but it's not running LE, so pointing you to GitHub - koenkooi/meta-kodi: The official OpenEmbedded/Yocto Project layer for Kodi would not help much. It's linux 4.7.1 + mesa 12.0.1 + xorg 1.18.4 + xf86-video-nouveau from git and the matching firmwares. I disabled the "prefer vdpau mixer" in kodi as well. From a quick look at the LE git tree it's only missing a package.mk for the xorg driver and the firmware.


    After Power Off then Power On some times is hungs and display
    *** Error in mount flash: mount common: Could not mount /dev/mmcblk0p1 ***
    and after disconecti power, wait 10 sec, conect power some time Boot normaly
    !!!

    I get that as well when using the uSD card, that problem went away after installing it to eMMC, which I realize isn't an option for everyone.

    Just read this article: Tanix TX5 Pro TV Box Review – Part 2: Modding and Testing, under section 4K it said: 'The Amlogic S905X does not supports h.264 60 fps above 1080p'.

    I also don't get the logic of 4K h.264, which is supported by S905 but not by S905X while this format is now more and more popular in Asia. Not sure about what would happen with S912!

    Judging from the kernel sources s912 ('gxm') is an s905x ('gxl') with a different MALI and an extra a53 cluster.

    This will change for the next build.

    koenkooi Can you try if rootwait in CMDLINE with my standard options helps booting?

    This diff on top of HEAD..2016-08-03-devel.diff:

    Boots from uSD!
    [hr]
    I neglected to mention earlier: 4k playback issues on an 1080p TV are still the same: big buck bunny 2160p30 switches to 1080p60, black screen, sintel 2160p24 switches to 1080p24, black screen.
    FWIW I don't get the logic behind using a 100Mbit PHY for a 4k box, it is *just* enough for jellyfish 90mbit. I realize on s905x you get it for free, but still...

    It boots and works after merging in your changes, the diff between your build and mine: git diff

    Going to add console=tty0 to the next build and see what happens. For the adventurous people among us, the .3 build in the same dir as the diff is the one I'm testing.
    [hr]
    New data point:

    Code
    [koen@thinkpad LibreELEC.tv]$ git diffdiff --git a/projects/S905/linux/linux.aarch64.conf b/projects/S905/linux/linux.aarch64.confindex 9dd040b..ee6a6b0 100644--- a/projects/S905/linux/linux.aarch64.conf+++ b/projects/S905/linux/linux.aarch64.conf@@ -342,7 +342,7 @@ CONFIG_FORCE_MAX_ZONEORDER=11 # # Boot options #-CONFIG_CMDLINE="console=ttyAMA0 systemd.show_status=auto"+CONFIG_CMDLINE="console=ttyAMA0 console=tty0 systemd.show_status=auto" # CONFIG_CMDLINE_FROM_BOOTLOADER is not set CONFIG_CMDLINE_EXTEND=y # CONFIG_CMDLINE_FORCE is not set

    Triggers the "can't mount" bug.