jernej

Members
  • Content count

    657
  • Joined

  • Last visited

1 Follower

About jernej

  • Rank
    Embedded member

Recent Profile Visitors

1187 profile views
  1. I don't know actual implementation details, but defining "bootargs" variable with "booti" command works, since I'm using that during development... I think I heard that bootm doesn't work with aarch64 kernels and I didn't even try it.
  2. Same as with other Cortex-A53 AW SoCs, it starts in aarch32 mode. I doubt they changed BROM functionality much. If you are using mainline U-Boot, that shouldn't bother you, since SPL switches to aarch64.
  3. jernej

    OrangePi PC - 240p timings/resolution via Composite possible?

    Only PAL and NTSC are possible.
  4. jernej

    mali node missing from dtb's on H5?

    It has string inside, so I guess it's x11 version. However, I'm not sure what drm in this case would mean. Not there yet (for normal, everyday use). However, progresss is nice.
  5. jernej

    mali node missing from dtb's on H5?

    Of course there is a way. Fortunately, Rockchip prepared a lot of Mali blobs with permissive license (they can be used on AW SoCs), among them all possible mali450 versions: https://github.com/rockchip-linux/libmali/tree/rockchip Usually, mali blobs are distributed by SoC vendor. I'm pretty sure that AW can prepare those blobs. However, someone have to ask for them. That would be SBC vendor job. I'm not sure if any SBC vendor redistributed mali450 blobs, I didn't check since I found RK blobs with right license. Be aware that even if you manage to put everything together, there is a chance that it doesn't work properly. I'm working on H5 mali450 currently (for LibreELEC) and I have some rendering issues with GBM version. Investigation is ongoing.
  6. jernej

    mali node missing from dtb's on H5?

    Here you have H5 mali DT node patch. Kernel side driver can be found on @Icenowy github page here. However, the biggest question is where to find appropriate userspace drivers if you care about licensing stuff. For private builds you can take them from anywhere you can find them, but it won't be redistributable. Don't forget that mali kernel driver version has to match to userspace version. About how to add your own patches to build system - you can find some documentation here.
  7. As you wish. There is still simplefb and dev images are not supported anyway and problem will mostly correct itself in 2 months
  8. I'm not sure I'm following you. To be clear, what kind of patches would you like to see for 4.16? Old, new or none? With old or new I mean old out of tree driver and with new new driver which was merged for 4.17. This is just me being lazy. Old DT HDMI audio changes should be equaly useful for this, since the idea is the same. They just need to be rebased and new boards have to be added. That's why the commit has work "hack" in it.
  9. You mean using old patches? Why? Check top 3 patches here what needs to be done for HDMI audio. Not much. I2S driver is good enough.
  10. @zador.blood.stained @Igor Do you prefer having each patch in separate file or can I join patches in one file? If we decide to backport, there will be around 30 new patches.
  11. audio works with two small DRM patches and few DT changes, so not a big deal, except resolving DT changes.
  12. HDMI may work from u-boot+simplefb, unresolved patches are for the DRM. @Igor zador is correct. Patches can be dropped only when 4.17 is released, so in about 2 months. However, there are many DRM changes in 4.16 so it may be better to backport patches from 4.17, but there are many, including in clocks subsystem. Maybe I can find time to look into that later this week.
  13. jernej

    1280X1024 resolution Orange Pi

    It's a bit harder than that, since A64 has a binary blob for HDMI in BSP. However, ayufan successfully replaced that blob with a code ported from H3. I'm not sure this patch is present in Armbian.
  14. jernej

    Armbian for OrangePi PC2, AllWinner H5

    Fortunately, VPU driver is around 95% usable also for newer SoCs. I have a feeling that H6 support will become useful a bit quicker.
  15. They only reach decoding goals on kickstarter, not encoding, so there is no guarantee they will make such driver. At least in proposed time frame.