jernej

Members
  • Content Count

    702
  • Joined

  • Last visited

1 Follower

About jernej

  • Rank
    Embedded member

Recent Profile Visitors

1823 profile views
  1. Then U-Boot doesn't have anything to do with your Linux display issues. Linux driver re-initializes all peripherals responsible for video output. There are 2 possible solutions: 1. disable display driver in U-Boot (there are some handover issues, which might prevent Linux driver from working correctly) 2. backport clock patches from 4.20 or use 4.20 (there was a bug which prevented correct initialization for some resolutions) Possibly you have to do both...
  2. jernej

    OP zero+ Tv Out

    Sorry, no instructions from me. But I remember that someone gave them some time ago on this forum for mainline kernel.
  3. jernej

    OP zero+ Tv Out

    For which kernel? If it is for mainline, then same instructions as for H3 applies.
  4. There is no need to do that on mainline based images (you posted 4.19, which qualifies for that). Display should be configured properly automatically. If not, then there is a bug either in the HDMI/display driver or in EDID data stored in your screen. That said, there was one HDMI bug which was fixed in 4.20. In short, some resolutions didn't work.
  5. jernej

    Orange Pi One Plus Desktop Enviroment

    I have H6 DRM patches prepared for 4.20, so you can just copy them over. However, I think you would need some more of them for 4.19. Currently, we're investigating some troubles with HDMI, so it's not stable yet anyway.
  6. jernej

    Orange Pi One Plus Desktop Enviroment

    @Igor H6 HDMI driver will be in 5.0. Did I miss anything?
  7. jernej

    [WIP]hdmi cec driver for H3

    I would suggest option 3 - do it after you installed Armbian directly on board. It is the easiest way and ok for one time thing.
  8. jernej

    [WIP]hdmi cec driver for H3

    I haven't used kernel 3.4 for years, but I remember some things. 1. load kernel module and check if /dev/sunxi_hdmi_cec exists. If not, you are missing some kernel patches. 2. You have to patch libcec with https://raw.githubusercontent.com/jernejsk/OpenELEC-OPi2/openelec-7.0/packages/devel/libcec/patches/libcec-04-sunxi-support.patch (works with libcec 3.0.1) 3. Add "-DHAVE_SUNXI_LIB=1" during cmake build Generally, I don't support kernel 3.4 anymore, so if there are any issues, you are pretty much on your own.
  9. jernej

    [WIP]hdmi cec driver for H3

    Which kernel version do you use? Take a look at output of "uname -a". If it is 3.4 then you can use libcec, but if it is 4.x, then libcec is useless without additional patches and possibly some kernel patches too.
  10. jernej

    H2+/H3/H5/A64 Disp2 U-Boot video driver

    I gave you new link few posts back. This work has been done about 2 years ago, so I forgot many details. It seems CONFIG_VIDEO_DE2=y is enough to enable driver, TV plug-in is auto-detected at boot only and only PAL is supported. It seems that that branch also doesn't have simplefb support. I don't know when I will get back to this, since I'm busy with Linux kernel stuff, mostly Cedrus and DE2 driver.
  11. jernej

    H2+/H3/H5/A64 Disp2 U-Boot video driver

    Yes, there is no official support for H3 TV out in mainline Linux on any board. And patch provided in that topic probably needs to be updated, depending on the sources you use.
  12. jernej

    H2+/H3/H5/A64 Disp2 U-Boot video driver

    The reason why that patch is still not merged in U-Boot is that it's hardcoded to PAL. BTW, that U-Boot branch doesn't exist anymore. Use that one instead: https://github.com/jernejsk/u-boot/tree/tv_out_v2
  13. That depends on chip itself and only H6 support 10 bit HEVC.
  14. I'll try to add support for it soon. But it will be in the same boat as others at first. Don't expect to have 10 bit HEVC support at the beginning. BTW, VP9 is separate peripheral so it needs separate driver. Since nobody did reverse engineering yet, it will take a long time to be supported. However, it seems to be Webm project reference VP9 HW decoder, so there is a great chance that other SoCs from other manufacturers have same unit and someone else might write a driver for it.