What motherboard?
Posts by smp
-
-
That image was intended for Noumenon for troubleshooting his projector issue with his NUC11. The reason for tigerlake optimization flag is that I use it in my personal builds and I don't really have time to do a clean build with default gcc optimization flags.
-
It should boot on NUC11. It boots fine on my Tiger Lake box.
The image was built with -march=tigerlake gcc flag. It would probably be unbootable on non-tigerlake CPUs.
-
is there a way to force YCbCr 4:4:4 output?
This image will use YCbCr 4:4:4.
-
What's the point? YCbCr 4:4:4 is the same as RGB
Diff
Display Morediff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c index 821411b..557bd91 100644 --- a/drivers/gpu/drm/i915/display/intel_hdmi.c +++ b/drivers/gpu/drm/i915/display/intel_hdmi.c @@ -2423,7 +2423,7 @@ int intel_hdmi_compute_config(struct intel_encoder *encoder, if (adjusted_mode->flags & DRM_MODE_FLAG_DBLSCAN) return -EINVAL; - pipe_config->output_format = INTEL_OUTPUT_FORMAT_RGB; + pipe_config->output_format = INTEL_OUTPUT_FORMAT_YCBCR444; pipe_config->has_hdmi_sink = intel_has_hdmi_sink(intel_hdmi, conn_state); -
Yes, but 4:2:0 is still only at 8-bit.
-
From JVC NX5 manual:
When the color space is RGB/YCbCr(4:4:4), only 8-bit input is supported.
^ There's your answer. You will have to use 8-bit for 4k/24Hz.
systemctl stop kodi
./proptest -M i915 -D /dev/dri/card0 308 connector 314 8
systemctl start kodi
try if 4K/24 now works
Upd: the manual actually refers to 4K 50/60Hz modes, so deep color should be supported with 4K/24. Try also 10-bit (./proptest -M i915 -D /dev/dri/card0 308 connector 314 10)
-
It seems that 4k23.98hz files won’t output video.
My best guess is that your projector does not like the 4K RGB 12-bit mode.
Try to reduce it to 10-bit. You can do that with libdrm proptest tool.
Copy proptest to /storage, then
chmod 755 proptest
./proptest
and post the output here
-
24hz 4:2:2 is supported though?
No. RGB 12-bit.
-
RGB 8bit,
On Intel hardware 4K 50/60Hz HDMI video modes will always be RGB 8-bit because Intel driver does not support YCbCr 4:2:2. Some type of dithering would be required.
the colorimetry is labelled sRGB instead of bt2020
Wrong colorimetry issue was discussed a few posts back. BT.2020 works with this unmerged PR. It will not be included in Kodi 20/LE 11.
-
This is needed for BT2020. It's not merged yet.
-
It should work. Try older nightlies, maybe something is broken for Jasper Lake in current Mesa 3D.
-
If you are able to compile your own LE image - TBS5922 driver should be rather trivial to port from TBS repo.
-
do you reckon this one will work?
I doubt it has an HDMI 2.0 chipset. Also, in the description it says:
"5.184 or 8.64 Gbit/s forward link channel supports high resolution displays with a single cable."
-
I presume I'd still get 4k/HDR
You will have to use an active DP to HDMI 2.0 converter.
-
-
Add i915.force_probe=56a1 to syslinux.cfg
-
This issue has nothing to do with the colorspace. AMD driver doesn't even allow setting the specific colorspace via drm properties.
QuoteThe Colorspace property is only exposed on intel hardware and vc4 (RPi4).
