Posts by rozpruwacz

    HI taki ,

    Regarding topic 1. I also think that the demod/tuner drivers should be distributed as addons. In my linux branch (https://github.com/mczerski/linux/tree/amlogic-dvb) I try to make the frontend attachment modular. Current version allows to plug in individual demod / tuner drivers with or monolitic driver implemntations with DTS. But current approach requires each plugin to "behave" in certain not documented way. I also want to try with slightly different approach and to use component framework. But there will be always some code required on the demod/driver side to be added - this is why addon approach will be the best.

    Regarding topic 2. Could you explain in more details what issues you have ? From my expirience there is no issues with i2c axccept one case, where two demods are on the same i2c bus - I had to modify m88rs6060 driver because it did not work well with i2c transactions interleaved with i2c transactions for the second demod.

    Also I would like to test Your current driver version. Can You share it through some git repository ?

    taki it might be a bug that I found when porting vendor driver to mainline.
    In aml_dmx.c You will find sunch code:

    Change 1<<(NEW_PDTS_READY) to 0<<(NEW_PDTS_READY) and check if it helps.
    For some reason this NEW_PDTS_READY interrupt source triggers at a very high rate and the kernel disables it. Disabling this interrupt is only a workaround but I don't know how to fix that better. And by looking at the code this interrupt source is not relevant.

    The other thing is that when using tvheadend I also have no dmx_irqs (only dvr_irqs).
    But when using dvbv5-zap (dvbv5-zap -c dvb_channel.conf -r "Some channel") I get dmx_irqs:

    Code
    48: 308 0 0 0 GICv2 55 Edge dmx irq
    49: 0 0 0 0 GICv2 37 Edge dmx irq
    50: 0 0 0 0 GICv2 53 Edge dmx irq
    51: 638 0 0 0 GICv2 51 Edge dvr irq
    52: 0 0 0 0 GICv2 57 Edge dvr irq

    I think we must decide how we approach this topic. The work I did was more like a proof of concept that it is even possible to have DVB working under mainline kernel. To make it real it must be merged into upstream.

    taki You said:

    I have developed this according to modern kernel architecture.

    Is that mean that You wrote it from scratch or did You take the vendor driver and adapted it like I did ?
    One thing is to write driver code according to mainline kernel infrastructure, other thing is to have this driver merged into upstream. I do not have expirience in pushing code to mainline kernel but I think that the code from my branch is far from this goal :D

    First: I'm sure I've seen already somewhere the solution for that (but can't find it now). Try to find this answer.

    Second: If You will not find the answer I could guide You how to do that. But You need access to serial console of the board, and You will need to change some u-boot environment variable. Basically I need You to paste here the output of the "printenv" command from the u-boot console. Do You know how to do that ?

    So it is my understanding that when libreelec is installed, it installs the core components to the NAND flash of the device, and then upon first boot it sets the device storage to external flash (USB formatted with the proper filesystem) to use in the future.

    Where You read this ? I can tell You that I put LibreELEC-Amlogic_G02REF.arm-9.0-devel-20190307225115-0e98e15.img.gz onto sd card and booted the box with it. Libreelec installed on the sd card and did not touch the nand. I can dual boot, when sd card is inserted the libreelec is booted and whithout sd card the stock android rom is booted from nand.

    I have different request if I may :) I'm using device with dvb-t tuner si2168, and it is not detected in this build. It is however working on the stock android rom. Is it possible to add driver for this tuner ?