Posts by jernej

H313 is afaik same as H616, with less memory supported (2 GiB vs. 4 GiB). Anyway, neither are supported by upstream Linux, so there is nothing to help with creating DT. Patches exist for H616, but DT parts are subject to change.

no, why?

I suspect that problem is not with decoding as it should switch to SW decoding automatically for unsupported formats. Kodi 19 doesn't switch rendering method if resulting format can't be rendered using DRM planes (v20 will most probably support this). Try set EGL rendering method for DRMPRIME (in such case, DRMPRIME decoder/renderer has no benefit) However, as chewitt says, it will be a slideshow.

Ok, thanks for confirmation. I also tested latest nightly image on brand new OrangePi 3 board today. I get exactly the same issues with the fresh board, so boards most likely work as they should.

I'll PR fixes to master and LE10 branch as temporary fix. I have yet to figure out what to do exactly for upstream Linux.

yes, clue is in first post here: Nightly images for A64, H3, H5, H6 and R40 boards

Ok, thanks for info. I'll check if this change can be upstreamed.

LuRu Can you please determine which change helped? Was it CPU regulator voltage range or wifi power supply? Wifi power supply changes would be easy to upstream, while CPU regulator range might be harder.

Ok, thanks! I'll open PR for master and backport to LE10 with these two patches soon. Next LE10 bugfix release will have it.

Currently there is no addons built for nightly images. Use LE10 stable image instead. There is no functional difference.

Ah, you can play a bit with patch itself, or checkout 5.10.61 kernel, make same edits and create patch.

Quote from LuRu

Of course it's not certain yet (freezing is accidental), but it looks good!

Unfortunately, next day it didn't work anymore for me, even with CPU devfreq totaly thrown out. I'll borrow another OPi3 to check again. I have a feeling that this is not so common issue, otherwise there would be more complaints, either here or IRC #linux-sunxi.

Quote from LuRu

How can I compile LE10 with the necessary changes?

just make patch file from link I posted above and put it in projects/Allwinner/devices/H6/patches/linux/ It should just work...

Output is actually RGB. YUV output is not yet supported by the display driver. HDMI driver automatically converts image to limited RGB, if needed by standard (99% of the time) and that's not possible to override.

I suggest you test this video: http://jernej.libreelec.tv/videos/h264/2-APL%20Clipping.mp4 If you see range about 16 - 235, then limited range works fine.

LuRu I think I found important difference. While it's true that wireless power supply is a mess, really important bit is CPU voltage range. I copied over One Plus values and my OPi3 seems to be much more stable. Please test this update:

Index of /test/opi3-stability/

Apply it to ordinary OrangePi 3 image.

DT changes: http://ix.io/3yMQ

If that doesn't work for you, I have one additional DT change to test. But I would really hope it's not the culprit.

Interesting analysis, thanks!

I compared OrangePi One Plus and OrangePi 3 DTs and one detail caught my attention immediately. BLDO3 power supply is marked as unused and not connected anywhere in OrangePi 3 DT . However, schematic shows it should be used for VCC-PG, VCC-PM and VCC-WIFI-IO. I'm not sure if this is the culprit of instability but certainly something to look into.

Unfortunately I'm busy with some other, more pressing issues. Would you please look into this matter a bit further and try to pinpoint exact issue? As you already noticed, OrangePi 3 and OrangePi One Plus DTs are pretty similar, so there is not much things to change and test. All you need to do is to make some changes in OrangePi 3 DT, create a patch, build your own image with that patch, update your system and test. Rinse and repeat until your board becomes stable. If you need help with that, just ask.

Composite TV out literally supports only PAL and NTSC modes (720x576i and 720x480i, respectively). No amount of tricks on your part will change that, sorry.

I find it surprising that your TV wouldn't support at least of one of those modes. They are few decades old standards. I tested this on some camera display from ebay and it worked fine, but it has normal RCA connector, without any resistors in between. I can probably get RCA to SCART adapter, but no promises when.

All known Allwinner SoCs to me supports only PAL and NTSC on composite output. You can select only between these two.

EDIT: how did you enable composite output? using provided overlay?

Since everything is done in spare time, it could be 1 month or 1 year or more. Most things work more or less, only DRM driver needs to be finished up and at least one audio output needs to be added. Currently it seems analog will be easier to support, since driver already exists for similar variant.

Summer is time for vacations and travels, so no.