Jump to content

jernej

Members
 View Profile  See their activity

  • Posts

    1144

  • Joined

  • Last visited

 Content Type 

Everything posted by jernej

  1. jernej
    No, you have to enable x11. Then Kodi should be able find your display.
  2. jernej
    Great, but while it works, IMO it doesn't have correct concept. Proper way would be to select 1080p or lower resolution, as reported by EDID. I guess current approach will work for 99% displays, because probably all high respolution displays also support 1080p.
  3. jernej
    @Igor, here is my attempt at limiting resolution for older SoCs: http://sprunge.us/iJBBBe aware that I don't have any such hardware to test it. But because patch is small, I hope it will work. I really couldn't find any HW limitation in datasheets. According to them, all SoCs should support 4K. However, if I remember correctly, they have too little memory bandwith to be capable of something more than FullHD. I think I even heard that even FullHD can be a bit much.
  4. jernej
    As would tkaiser suggest, use etcher, which will detect issues with writting. dd will just ignore or missed them.
  5. jernej
    Yes, just to see if there is some issue in latest code.
  6. jernej
    Internally, HDMI has type 4. Confusing, I know. Only last line indicate a possibility for some kind of error. Can you try clean desktop image?
  7. jernej
    Sorry, 35 is correct one for your resolution. I looked at wrong number in patch. Does U-Boot show logo correctly? Can you try another cable?
  8. jernej
    BTW, 1440x900 is mode 39. If that doesn't work, you can try 720p with pll_video=297 and screen0_output_mode=5
  9. jernej
    Be aware that GPIO pin is capable sourcing only about 20 mA of current which is waaaaay too low for running any kind of motor. You need to put some kind of transistor in betweeen, like MOSFET. You have plenty tutorials on the net.
  10. jernej
    Did you check voltage levels with multimeter? How did you connect motor? Through MOSFET?
  11. jernej
    I will update audio drivers from tinaos, which improves I2S (reported in another thread). Based on the fact that HDMI also uses I2S internally, I hope this will improve situation. From what I know, tinaos and H5 BSP codebases are not very far apart.
  12. jernej
    Nothing useful, sorry. If I were you, I would try to compile Mosterta version of Kodi.
  13. jernej
    I doubt there is enough interest to fix such issue, but you can always open an issue in vdpau-sunxi repo. You can also try my OpenELEC fork if you want, where there is no such problems.
  14. jernej
    vdpau-sunxi uses "always on top" overlay for video. If you want subtitles, you have to execute export VDPAU_OSD=1 before playing video. Subtitles are then SW rendered on video image.
  15. jernej
    Ok, I will try to make something next week.
  16. jernej
    Then just be sure that you enable DVI mode with h3disp tool.
  17. jernej
    Do you want to say it is 4K capable? It seems that they have HDMI 1.3, which have this limitations: http://superuser.com/a/119756However, I'm not sure what to check. Frequency? Maybe you can increase framebuffer size in U-Boot like I have done and see what happens. To me, this looks like more video encoder limitation (like H264), if you check meaning at other chips.
  18. jernej
    This driver is only for H3 (for now), so this shouldn't be an issue. Older SoCs like A20 have separate driver. Is there any hard fact like max resolution by datasheet on which we could base the decision? BTW, where is an official statement that H2+ doesn't support 4K? BSP code definetly doesn't limit it. For now, there is only one H2+ board, which has no HDMI output at all.
  19. jernej
    @Igor, what is the status of the 4K on the legacy kernel? I could port same change as it was made for U-Boot.
  20. jernej
    Ok, I'm out of ideas. I guess your monitor doesn't support downscaling? If it did, you could just set 1080p and it would get along. You could also try with 720p as compromise solution. Anyway, if U-Boot works but not the kernel, then something is wrong with the drivers. P.S.: Maybe you can check last Armbian image which didn't include U-Boot with splash screen. Maybe kernel driver has some assumptions which gets broken in the process of executing U-Boot driver.
  21. jernej
    Did you set correct resolution by h3disp first? If you did, then this topic probably applies: https://forum.armbian.com/index.php/topic/2991-opi-pc-2e-h3disp-1680x1050-dvi-display-issues
  22. jernej
    What is your screen resolution?
  23. jernej
    What means "fiddling" here? What exactly did you change?
  24. jernej
    It is already fixed and it will be included in nightly build.
  25. jernej
    Little bug here. You rounded to commonly used 148.5 MHz, which also might be fine, however, in this case you have to change pll_video to 297 (148.5 * 2 = 297). Another, originally recommended, option would be to use 147000000 Hz (lesser error) and pll_video set to 294 (as it is now).
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept