Please provide DT patch and I'll incorporate it into PR.
I also fixed deinterlacing, the only remaining issue I could find for H616. I'll push it later with your fix.
Posts by jernej
-
-
jernej I saw there were some commits in your fork branch allwinner-h616. Can you please let me know if they are working well?
I did quick check on x96-mate clone board and fixed some obvious issues. Now basic H616 support should work.
Please test:
-
I haven't tested them yet... Probably next week.
-
well, if you have a spare SD card, you can try it, why not? But driver wise, things are not yet improved. BTW, driver architecture basically didn't change between LE11 and LE12, so most likely cause for your issues is in Kodi audio handling.
-
Passthrough was never a functionality that was officially supported by Allwinner LE releases. There were also a lot of fixes for passthrough in last year or so on Kodi side. However, it's my plan to properly support passthrough in LE13. LE12 is not supported anymore.
-
This is the same issue as in Banana Pi M2U No boot
What I found is that U-Boot doesn't work for some reason. What you can do is to first boot known working image, e.g. 12.0.2 and then manually update it with higher versions like described here. That way you'll keep original working U-Boot and have new userspace.
-
Can you try playing some h264 video first? I noticed that if VP9 is played first, it can crash. I looked into it, but couldn't find any issue.
-
I meant LE13 nightly.
I've also have a problem with the media-cedrus-Implement-AFBC-YUV420-formats-for-H265.patch. My eachlink h6 mini does not support 8 Bit media in h265 only 10 Bit media like it is written on https://linux-sunxi.org/Cedrus#Supported_codec_matrix. So I had to remove that mode from cedrus_video.c
This doesn't make sense. If 10-bit is supported then also 8-bit is supported. It actually seems that you experience other way around. That patch introduces AFBC format support for H265, which is actually the only way to support 10-bit output currently (other 10-bit formats are not implemented).
In any case, if you remove that patch, you'll get only 8-bit format for 10-bit video. I've never heard that specific H6 device would have issues decoding with H265. Maybe it is some lower performance version of H6.
-
Hey,
I have Tanix TX6 where ddc-en is always enabled early enough. That being said, I recently fixed aforementioned patch in master branch since it was out-of-sync with latest upstream code. Can you try first nightly Tanix TX6 image to see if it works for you?
-
I found the issue, but I'm not sure how to solve it yet. It's extremely weird. U-Boot is not built correctly, that much is obvious. However, reason why is curious. If I put .git folder into source folder, then it builds correctly. It seems that some tool require git metadata to decide something. I have to find which tool causes that.
This is second weird build bug that I'm researching in last week or so...
-
Ok, so there is some issue with mainline U-Boot. R40 is so rare that nobody raised issue before. I guess some bisecting is in order...
-
-
leoneii Issue is solved by kernel update in nightly v12.2 images.
Fix: https://lore.kernel.org/linux-sound/87…[email protected]/
-
-
No. Display driver is being worked on, so it won't be supported for some time.
-
Hm... Not sure what could be wrong, but most likely U-Boot related. Since I don't have time to look into this anytime soon, can you make following experiment. Flash 12.2 image, extract first 1 MB from 12.0 image, remove first 8 KB of that 1 MB dump and flash resulting binary to 12.2 image at offset 8 KB. I hope you understand
otherwise I can provide set of dd commands to do that. -
Actually there is a way to support this chip with mainline driver. My most recent attempt (4 years old) is here:
Commits · jernejsk/linux-1Linux kernel source tree. Contribute to jernejsk/linux-1 development by creating an account on GitHub.github.comWifi worked but suspend was broken, which makes it ineligible to include it to LE. Any efforts on this front would be appreciated
-
Sure, but it's implemented if I understood the OP right:
You did not. VP9 HW decoding is supported only by H6. I guess compatibility matrix would be clearer.
We really need this project to continue. There is a bunch of h616/h618 devices (tv boxes) out there that are still waiting for official support.
Yeah, that won't happen anytime soon. Display driver accumulated so much technical debt that it needs to be considerably reworked in order to support H616 and newer SoCs properly. While obviously there are PoC versions out there, mostly based on my early work, none of that works good enough for Kodi needs (Kodi needs features most other software doesn't need). Videos wouldn't be rendered properly in plenty of cases, so this forum would be spammed with a lot of "it doesn't work" messages.
I started working on this redesign of display driver, but it's slow process, since I work on it only in my spare time. However, good thing is that redesign will also solve years old issues for existing devices like occasional glitches, especially during start or end of playback.
