jernej

  • Posts

    1033
  • Joined

  • Last visited

Reputation Activity

  1. Like
    jernej got a reaction from lanefu in H3/H5/A64 DRM display driver   
    Today A83T HDMI driver was merged Now to the H3/H5 driver, which should be more straightforward for mainlining. Seems like with 4.17 there will be no need for DRM patches, except maybe for A64 (depends when Icenowy can get DE2 clocks & SRAM patches merged).
  2. Like
    jernej got a reaction from zador.blood.stained in H3/H5/A64 DRM display driver   
    Today A83T HDMI driver was merged Now to the H3/H5 driver, which should be more straightforward for mainlining. Seems like with 4.17 there will be no need for DRM patches, except maybe for A64 (depends when Icenowy can get DE2 clocks & SRAM patches merged).
  3. Like
    jernej got a reaction from MX_Master in OpenRISC core (AR100) for the real-time tasks   
    AFAIK, mainline kernel runs in unsecure mode, where you can't write to secured registers like R_CPUCFG.
  4. Like
    jernej got a reaction from TonyMac32 in Kickstarter: Allwinner VPU support in the official Linux kernel   
    While they still don't cooperate with open source community as good as Rockchip, they at least are more cooperative. I asked for HDMI/DE2/DE3 documents and received all of them. Someone else asked about AC200 doc and also receive it. Or better said, they were uploaded to linux-sunxi.org. I would say that is a very good improvement.
  5. Like
    jernej got a reaction from Tido in Kickstarter: Allwinner VPU support in the official Linux kernel   
    While they still don't cooperate with open source community as good as Rockchip, they at least are more cooperative. I asked for HDMI/DE2/DE3 documents and received all of them. Someone else asked about AC200 doc and also receive it. Or better said, they were uploaded to linux-sunxi.org. I would say that is a very good improvement.
  6. Like
    jernej got a reaction from pfeerick in Kickstarter: Allwinner VPU support in the official Linux kernel   
    While they still don't cooperate with open source community as good as Rockchip, they at least are more cooperative. I asked for HDMI/DE2/DE3 documents and received all of them. Someone else asked about AC200 doc and also receive it. Or better said, they were uploaded to linux-sunxi.org. I would say that is a very good improvement.
  7. Like
    jernej got a reaction from MX_Master in OpenRISC core (AR100) for the real-time tasks   
    No, you have to either change u-boot code or edit boot script and add memory write command (mw.l), which writes right value to register.
  8. Like
    jernej got a reaction from MX_Master in OpenRISC core (AR100) for the real-time tasks   
    Yeah, that's tzpc. I forgot to mention, bsp kernel runs in privileged mode and mainline in unpriviledged mode. That's why you see a difference in behaviour.
  9. Like
    jernej got a reaction from chwe in 1366x768 HDMI Orange Pi PC Plus?   
    You mean predefined resolutions for old BSP kernel 3.4? Mainline kernel should in theory support all resolutions, albeit in practice some may not work correctly.
     
    How did you test that?
     
    If you go with mainline image, it should work. But then, mainline images for H3 are considered WIP and thus not directly supported, e.g. you are on your own with issues. If you go with old BSP 3.4 kernel, you have to patch the kernel to add your resolution. Procedure was already explained on this forum.
  10. Like
    jernej got a reaction from MX_Master in OpenRISC core (AR100) for the real-time tasks   
    Here is attempt to make mainline driver for AR100: https://github.com/mripard/linux/commits/sunxi/wip/ar100 But as branch name says, it's wip and not necessarly working. I didn't try it, I just though it might interest you.
  11. Like
    jernej got a reaction from Naguissa in Banana Pi: Mainline kernel with hw video acceleration / decoding   
    I'm not sure if I completely understand the issue, but recently I came across this LE PR: https://github.com/LibreELEC/LibreELEC.tv/pull/2382
     
    Long story short, kernel from 4.9 onwards has latency issues on USB, which could cause visible artifacts when using DVB dongles. It is not clear what is correct solution, but in this thread some possible workarounds are proposed: https://www.spinics.net/lists/linux-usb/msg163892.html
     
    I think that most promising workaround can be found in LE PR mentioned at the beginning.
     
    Let me know if this is what you're after.
  12. Like
    jernej got a reaction from zador.blood.stained in Banana Pi: Mainline kernel with hw video acceleration / decoding   
    I'm not sure if I completely understand the issue, but recently I came across this LE PR: https://github.com/LibreELEC/LibreELEC.tv/pull/2382
     
    Long story short, kernel from 4.9 onwards has latency issues on USB, which could cause visible artifacts when using DVB dongles. It is not clear what is correct solution, but in this thread some possible workarounds are proposed: https://www.spinics.net/lists/linux-usb/msg163892.html
     
    I think that most promising workaround can be found in LE PR mentioned at the beginning.
     
    Let me know if this is what you're after.
  13. Like
    jernej got a reaction from valant in Cheap HDMI monitor -1   
    @valant
     
    Yeah, I mean that, but if I understand you correctly, you need just a basic (static?) setup, without any bells and whistels. Then you should probably check U-Boot implementation located here. It is much more basic and it can be reduced even further if you remove audio related stuff. If you want to support only one predefined resolution, then you could also remove all DDC/EDID related stuff. Both changes will probably leave you with only half of the code. I think this is really bare minimum for DW HDMI.
     
    i.MX6 documentation should suffice for such setup. You can even find original pre-release version of DW HDMI documentation on some Chinese forum (I don't know which), but as I said, i.MX6 doc is enough for probably everything you need.
  14. Like
    jernej got a reaction from valant in Cheap HDMI monitor -1   
    @valant
    I can give you some help since I'm working on Allwinner DW-HDMI implementation, but what you asking is totally platform dependant. At least on Allwinner, LCD controller (called TCON) is just something which outputs raw data on parallel or LVDS interface. If you want anything else (TV, HDMI, MIPI-DSI) you must chose pipeline which has encoder right behind LCD controller. So it looks something like:
     
    LCD:
    Display Engine (HW composer) -> TCON (LCD controller) -> LCD panel
     
    HDMI:
    Display Engine -> TCON -> HDMI
     
    I took a quick look at your BSP code and it seems that you have same situation. That means that LCD controller needs to be enabled and properly set up in order to use HDMI.
     
    If you are writing driver for mainline kernel or U-Boot, you are fortunate that most heavy lifting is already done for DW HDMI. You just use library provided inside. If your SoC uses Synopsys PHY, you just need to provide few numbers extracted from BSP driver and some boilerplate code. Unfortunatelly, you have to write full DRM driver for, I'm not sure how there is called, Display Engine and/or (only?) LCD controller.
  15. Like
    jernej got a reaction from zador.blood.stained in Neo2 usually doesn't cold start on first attempt   
    Apart from DT changes, driver shouldn't need much adjustements for 4.14, if any. 4.15 (current linux-next) is a different story though.
  16. Like
    jernej got a reaction from TonyMac32 in Getting LibreElec to work with my RK3288 tablet   
    That probably won't work, unless both kernels were built from exactly the same kernel source. Additionally, drivers in LE reside in read only part of filesystem. So you have to have LE sources and put those drivers there. But since you have to build whole image, it makes much more sense to add those drivers as a source in build system and build them.
     
    BTW, part of LibreELEC team (me and omegamoon (builder of ugoos images) included) works on official LE support for Allwinner, Rockchip and Amlogic devices. RK3288 is included in that effort, so if you can wait a bit, you will get official LE image. You can ask at LE forum in Rockchip subforum what can be done. Please specify details, for example exact tablet model, which wifi driver you need, etc. If problems are minor, like enabling already present wifi driver, they will probably be resolved quickly, but of course I can't guarantee that.
  17. Like
    jernej got a reaction from zador.blood.stained in Mali support announced for mainline (Allwinner SOC's)   
    I can tell that I tested Mali wayland/gbm driver version and it works well.
  18. Like
    jernej got a reaction from manuti in H3/H5/A64 DRM display driver   
    @Da Alchemist
    I prepared another test patch for multichannel audio support. Can you test it?
    http://sprunge.us/gcbB
  19. Like
    jernej got a reaction from manuti in H3/H5/A64 DRM display driver   
    Yeah, I'll fix that. Usually I'm lazy when it comes to DT...
     
    I tested it already. Just one line fix was required to make it work, which is already included on my github:
    https://github.com/jernejsk/linux-1/commit/5de498da7efd4593976c4e41ca7367ac23352616#diff-0dd6c05e592804ae87e06c218a333a37R318
  20. Like
    jernej got a reaction from zador.blood.stained in H3/H5/A64 DRM display driver   
    Yeah, I'll fix that. Usually I'm lazy when it comes to DT...
     
    I tested it already. Just one line fix was required to make it work, which is already included on my github:
    https://github.com/jernejsk/linux-1/commit/5de498da7efd4593976c4e41ca7367ac23352616#diff-0dd6c05e592804ae87e06c218a333a37R318
  21. Like
    jernej got a reaction from Naguissa in Mali support announced for mainline (Allwinner SOC's)   
    Which is not possible with all Mali GPUs Allwinner used till H6.
  22. Like
    jernej got a reaction from willmore in Mali support announced for mainline (Allwinner SOC's)   
    Which is not possible with all Mali GPUs Allwinner used till H6.
  23. Like
    jernej got a reaction from zador.blood.stained in H3/H5/A64 DRM display driver   
    But is needed anyway.
     
    My findings also.
     
    I hope I can play a bit with Mali in the evening.
  24. Like
    jernej got a reaction from zador.blood.stained in H3/H5/A64 DRM display driver   
    I think you must go trough all uargs->... references and replace it to job->uargs->... except for https://github.com/Icenowy/sunxi-mali/blob/master/r6p0/src/devicedrv/mali/common/mali_gp_job.c#L93, obviously.
  25. Like
    jernej got a reaction from zador.blood.stained in H3/H5/A64 DRM display driver   
    Some clock patches are also needed. Take a look at my patches from 1. Avgust here: https://github.com/jernejsk/linux-1/commits/h3_hdmi_audio_v1/drivers/clk/sunxi-ng
    Without them, resolution switching to resolutions like 1080p or 720p won't work.