Jump to content

Neil Armstrong

Members
  • Posts

    47
  • Joined

  • Last visited

Posts posted by Neil Armstrong

  1. @ning exact, the OSD scaler is shared between the OSD1 & OSD1, but we use the scaler to update automatically the field when in interlace mode, if we wanted to enable OSD2 we should switch the field manually in the vsync irq. It's doable but I don't plan on doing it

     

    For A311D, Amlogic did a brand new blender module for OSD and VD planes, but I don't have the exact capabilities of the blender and the number of available scalers, when I'll have the info, I may expose more OSD planes and eventually a Cursor plane.

  2. S805X doesn’t support 4K, even if it works some time, it’s not stable enough to consider functional, I sent fixes to Da for that, but he’s still testing them.

     

    any (binary) edid dump would help !

     

    and for 4K development, the hdmi2 yuv420 4k60 mode is only used on Cheap 4K TVs, workout this patchset you’ll have 4k30 just fine

  3. @TonyMac32 I'm getting a failure in u-boot with the latest 4.19 bionic desktop LePotato image I get from armbian.com :

    Spoiler

     

    Quote

    GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;
    no sdio debug board detected 
    TE: 1888362

    BL2 Built : 11:58:42, May 27 2017. 
    gxl gc3c9a84 - xiaobo.gu@droid05

    set vcck to 1120 mv
    set vddee to 1000 mv
    Board ID = 6
    CPU clk: 1200MHz
    DQS-corr enabled
    DDR scramble enabled
    DDR3 chl: Rank0+1 @ 912MHz - PASS
    Rank0: 1024MB(auto)-2T-13
    Rank1: 1024MB(auto)-2T-13
    DataBus test pass!
    AddrBus test pass!
    Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
    New fip structure!
    Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
    Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x00018400
    Load bl33 from SD, src: 0x0003c200, des: 0x01000000, size: 0x00081200
    NOTICE:  BL3-1: v1.0(release):3348978
    NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
    [BL31]: GXL CPU setup!
    mpu_config_enable:ok
    [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
    OPS=0x84
    48 38 b be a2 f0 dc eb 16 d9 1e b2 [2.241797 Inits done]
    secure task start!
    high task start!
    low task start!
    ERROR:   Error initializing runtime service opteed_fast


    U-Boot 2018.11-armbian (Jan 11 2019 - 19:16:55 +0100) libretech-cc

    DRAM:  2 GiB
    MMC:   mmc@72000: 0, mmc@74000: 1
    Loading Environment from EXT4... ** File not found /boot/boot.env **

    ** Unable to read "/boot/boot.env" from mmc0:1 **
    In:    serial@4c0
    Out:   serial@4c0
    Err:   serial@4c0
    [BL31]: tee size: 0
    [BL31]: tee size: 0
    Net:   
    Warning: ethernet@c9410000 (eth0) using random MAC address - 2a:ef:31:d6:85:db
    eth0: ethernet@c9410000
    Hit any key to stop autoboot:  0 
    switch to partitions #0, OK
    mmc0 is current device
    Scanning mmc 0:1...
    Found U-Boot script /boot/boot.scr
    3048 bytes read in 1 ms (2.9 MiB/s)
    ## Executing script at 1f000000
    154 bytes read in 1 ms (150.4 KiB/s)
    ** File not found /boot/uInitrd **
    ** File not found /boot/Image **
    ** File not found /boot/dtb/amlogic/meson-gxl-s905x-libretech-cc.dtb **
    libfdt fdt_check_header(): FDT_ERR_BADMAGIC
    No FDT memory address configured. Please configure
    the FDT address via "fdt addr <address>" command.
    Aborting!
    ** File not found /boot/dtb/amlogic/overlay/meson-fixup.scr **
    Bad Linux ARM64 Image magic!
    SCRIPT FAILED: continuing...
    MMC Device 2 not found
    no mmc device at slot 2
    starting USB...
    USB0:   Register 2000140 NbrPorts 2
    Starting the controller
    USB XHCI 1.00
    scanning bus 0 for devices... 3 USB Device(s) found
           scanning usb for storage devices... 0 Storage Device(s) found

    Device 0: unknown device
    Speed: 100, full duplex
    BOOTP broadcast 1

    Abort
    missing environment variable: pxeuuid
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/01-00-50-43-84-fb-2f
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/00000000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/0000000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/000000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/00000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/0000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/000
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/00
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/0
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/default-arm-meson
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/default-arm
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    missing environment variable: bootfile
    Retrieving file: pxelinux.cfg/default
    Speed: 100, full duplex
    *** ERROR: `serverip' not set
    Config file not found
    => <INTERRUPT>
    => <INTERRUPT>
    => 

     

  4. @rino so you connect the same screen via HDMI and "HDMI to DVI" and only the "HDMI to DVI" fails ?

    What is the resolution selected via HDMI and "HDMI to DVI" ? is that 1920x1200, 1920x1080 or 1600*1200 ?

     

    On 4.19 I added a "generic" support for all monitors, but I waited for feedback to know if it failed on some monitors.

     

    Let me check

  5. @TonyMac32the overalloc is for the fbdev variant only, which won't work at all on 4.19 (needs a dirty quirk to enable it back which will land on 4.20 https://www.spinics.net/lists/dri-devel/msg191151.html), if you plan to use the X11, Wayland or GBM variant you should use the CONFIG_DRM_FBDEV_OVERALLOC=100 default config

     

    For USB, this patch https://github.com/chewitt/LibreELEC.tv/blob/amlogic/projects/Amlogic/patches/linux/linux-9999-dwc2.patch should solve your issue for the K2 and C2. 

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines