I've heard people going on about HDR for years, but I've never quite understood what the big deal was.
The big deal is that ~90% of the 4K UHD stuff you find on the internet is HDR. So if you have a 4K HDR capable TV you'd want your LE device to be able to pass through the HDR metadata.
If Nvidia support is coming back with this driver, maybe the userbase will come back too?
Not gonna happen. "Userbase" wants HDR which will only work with Kodi-GBM. Nvidia does not support GBM.
No. Too much stuff to backport.
Intel are now EOL'ing Gemini Lake
Intel just released Gemini Lake Refresh SoCs (J5040, J4115...).
You will have to use CoreELEC for the foreseeable future.
LE does use the NVidia proprietary driver.
Hisilicon and Broadcom (that is used in STBs) are not supported by LibreELEC.
will i be able to install LibreELEC on it ????
No.
better question, why does Hardkernel sells something that can't be used at release
It can be used with out-of-tree Realtek driver. Not to mention Windows 10.
Yeah, looks like you will have to wait for the updated r8169 in-kernel driver.
It's there... It's a hidden .update folder.
You can also use LibreELEC USB-SD Creator tool.
Use a nightly build. RTL8125 network should work with it.
LibreELEC-Generic.x86_64-9.80-nightly-20200625-cc6e86c.img.gz
You can also use one of my builds with experimental HDR support for Intel Gemini Lake that I posted in this thread. RTL8125 should also work.
LibreELEC-Generic.x86_64-9.80-devel-20200624071923-38764c8.img.gz
Just wanted to ask a quick question, so as it stands right now even IF my tv flips to HDR mode with intel hardware i'm not really getting "proper" HDR?
We were only talking about the optimal HDMI output for 50/60hz modes. Don't worry too much about it.
When you say it 'prefers RGB 8-bit' - what happens if RGB isn't available as an option? Does it then flip to 4:4:4 YCrCb 8-bit? (I'm thinking if you did a custom EDID that said 'YCrCb only'?) I wonder if it's possible to create an EDID that says 4:2:2 and 4:2:0 only at 2160p50/60?
I don't think RGB can be removed from EDID, looks like it is mandatory.
YCbCr 4:4:4 can be forced with a driver hack but I suppose there is not much use for this mode.
4:2:2 is not even present in the driver source code, so it can't be forced.
4:2:0 12-bit can probably be forced with a driver hack but I'm not sure. Driver assume that RGB 8-bit is the highest quality mode for 2160p50/60 and use it instead of 4:2:0 12-bit.
Is this discussion here relevant to this issue [GLK] no signal - with samsung 4k TV - HDMI UHD Color (ENABLED) (#271) · Issues · drm / intel · GitLab ?
It appear to be some sort of compatibility issue with Gemini Lake's HDMI 2.0 implementation and some Samsung TVs.
I wonder if Intel don't 'get' this issue yet?
HDR on Linux with Intel hardware is not a thing yet. I'm sure things will change.
Personally I think 4:2:0 10-bit/12-bit or 4:2:2 12-bit are the only routes really worth following for 10-bit SDR and HDR content at 2160p50 and above.
The thing with Intel driver is that it does not allow deep color 4:2:0/4:2:2 2160p50/60 modes. It prefers RGB 8-bit and I'm not sure this will ever change. I think the driver can be hacked to allow 4:2:0 but I didn't test it.
10-bit SDR and HDR sources don't look very good when downconverted to 8-bit without dithering (e.g.sky almost always look terrible with tons of banding). With dithering enabled in the driver the banding is not really an issue anymore.
Some new patches for LSPCON HDR just showed up.
[v5,08/11] drm/i915/lspcon: Create separate infoframe_enabled helper - Patchwork
[v5,09/11] drm/i915/lspcon: Do not send infoframes to non-HDMI sinks - Patchwork
[v5,10/11] drm/i915/lspcon: Do not send DRM infoframes to non-HDMI sinks - Patchwork
If you feel like trying them here's an image.
Okay so Nvidia seems a nogo. What about AMD?
Another option is to wait for the Intel discrete card. They should be out soon. Intel's Linux drivers are excellent. AMD is ok, but drivers are not nearly as good as Intel's.
At Archlinux and KODi Forum
By "quality of video is not as good as on X11" he means that some features like dithering and color management are not (yet) implemented in Kodi-GBM because it would require OpenGL.Kodi-GBM use OpenGLES. Normally those features shouldn't be touched anyway, so no big loss.
