Posts by myxal

    Am I doing this right? I decompiled the DTB, set status="disabled" on the first enabled usb node (and the phy which the subsequent attempt to boot complained about), compiled and replaced sun4i-a10-a1000.dtb. Diff:


    That did get rid of detecting the USB wifi (didn't have anything else attached), but the error message is the same:

    Quote

    [ 4.084220] Run /init as init process

    [ 4.095837] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

    [ 4.109445] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

    jernej, which /init is this referring to? This one?

    I've tried the ready-made image linked here, which should be a mainline kernel, albeit an old one: Mainline Debian HowTo - linux-sunxi.org (image link). I didn't go into installing UBoot and full-featured boot - I think that nukes the onboard android, which I don't want to do yet (want to back up the partitions first, and don't have an ADB cable yet). But the pre-install environment did boot successfully, with even the USB ports working (there was no driver for the onboard wifi, but it did show up in lsusb.


    What would be a simple way to prevent jernej's build from loading the Realtek wifi drivers, to check if that's the culprit here?

    OK usbc0 is disabled in the fex. So dtb should be OK. I don't see any differences.

    Hmm, maybe this is the problem - what would be the DTS equivalent of usb_host_init_state in FEX?

    Quote


    various: Set usbc2 usb_host_init_state to 1

    Code
    usb_host_init_state for usbc2 needs to be 1 for the wifi driver to properly
    auto-load. I don't have these boards to verify, but these are 512Mb RAM
    variants of 1Gb boards I do have, so it is safe to assume this is necessary
    with their 512Mb counter-parts too.
    
    Signed-off-by: Hans de Goede <[email protected]>
    Code
    &usbphy {
        usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */
        usb1_vbus-supply = <&reg_usb1_vbus>;
        usb2_vbus-supply = <&reg_usb2_vbus>;
        status = "okay";
    };

    Not quite sure what that does, but here's what looks relevant from A1000 fex file:

    Hmm, seems to happen after finding the built-in USB WLAN:

    Files

    Re: A2000, not quite there yet...

    Code
    ## Flattened Device Tree blob at 43000000
       Booting using the fdt blob at 0x43000000
       Loading Device Tree to 49ff7000, end 49fffb32 ... OK
    
    Starting kernel ...
    
    [    0.165777] sun4i-usb-phy 1c13400.phy: Couldn't get regulator usb1_vbus... Deferring probe
    [    1.376003] debugfs: Directory '1c22c00.codec' with parent 'sun4i-codec' already present!
    [    1.746350] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
    [    1.754214] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

    Output on HDMI shows a short white line in the top left corner. My monitor is 1440p, and is showing that the input signal has the full resolution, but I don't think the A10 is capable of [email protected]? Seems like it's being driven beyond capabilities. Tried again on another monitor with 1920x1200, works OK.


    VGA output works ([email protected]), shows Linux console (same as observed on UART). Doesn't appear to actually boot, see attached log.

    log.txt

    I'm also at a loss as to how to go about the display output DT patch - never did anything with DT, only know that it "describes HW" in lieu of autodiscovery like ACPI.

    Do you mean something like this, but for the sun4i-a10-a1000.dts ? Or is some other info needed?

    Hello. I have an A2000 box with the A10 chip. Didn't see any Allwinner nightly builds, as the blog post implied, and the most recent posts here suggest that the board's specs are just too low to even bother.


    So.. what's the current status/intention/plan of A10 support? (Waiting for driver fixes? Looking for testers/hardware? Unsupported permanently? Lack of maintainer time/interest?)

    Hi all,

    I'm considering getting a Rockchip TV-box or SBC, considering the early positive results for Hi10P H264 (a.k.a. 10-bit H264 "anime release") playback test by CNX on RK3229: Rockchip RK3229 Video Playback Take 2 – 10-bit H.264 & H.265, Audio HD Pass-through with Zidoo X1 II


    The trouble is, I haven't found much verified information regarding the following:

    1. Is the MPP in the RK3399 equal, or superset of the one in RK3229?
    2. Will KODI in LibreELEC handle Hi10P files?? (The CNX article doesn't mention any specific players, so I assume it was tested on bundled players, running on Android.)