dale can you test please? https://jernej.libreelec.tv/images/h616/
code: https://github.com/jernejsk/Libre…allwinner-h616/
This wasn't tested on my side yet.
dale can you test please? https://jernej.libreelec.tv/images/h616/
code: https://github.com/jernejsk/Libre…allwinner-h616/
This wasn't tested on my side yet.
The only other H616 family board with LPDDR3 is Tanix TX1. However, it uses higher speed memory and has no SD card slot. So you would have to make U-Boot configuration and Device Tree based on TX1, which will fit your board.
ok, this needs AC300 integration. It will take a while to do it properly and you'll have to test it.
dale Can you please run devmem 0x0300622C 32in console and report back? H616 has two types of internal ethernet PHYs and currently on AC200 is supported.
I'll generate test image for both issues after you provide value.
It has 32 GB of flash storage and (theoretically) 4GB of RAM, but LE can only see 3 GB, I still don't know why.
H6 can address only 3 GB of memory, despite having 4 GB installed. It's normal (HW limitation). I believe Android usually displayed installed memory, not usable, to produce better numbers.
Regarding your DT changes - you can post modified DT to upstream Linux as a patch (with all submission rules followed) and get it accepted. Then we can make separate board target. This is good exercise for Linux contribution. Alternatively, you can create DT overlay and apply it via extlinux.conf, so you don't need to repeat exercise of modifying DT every time you update LE.
Yasai-san Thanks for testing! H616 images are already included in nightly builds and will be available in next release.
I'll make general update in AXP313A driver, since that seems to be universal solution for all boards.
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.
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.
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...