Is this really true?
n5105 (Jasper Lake) does not support VAAPI-MADI and VAAPI-MCDI methods. VAAPI-BOB is low quality.
why intel, a company with huge $$$ problems, destroys all new cpus for watching proper deinterlaced video content?
All new Intel CPUs except EHL/JSL can do proper hw deinterlacing. See here. "* EHL/JSL only support BOB DI"
The good news is that you can enable high quality "BWDIF" software deinterlacing. Switch "Deinterlace method" to "Deinterlace", that would enable BWDIF.
there is always a blank screen
A blank screen for a second during a channel switch? This is normal.
but when used Hardware decoding Inactive there is no black screen
There is a frozen frame instead of a black screen. I don't see how this is better than a black screen.
git diff intel_hdmi.c.original intel_hdmi.c.edited > linux-force-yuv.patch
then edit the patch to fix the path to intel_hdmi.c (drivers/gpu/drm/i915/display/intel_hdmi.c)
I see this issue this with some rare DVB-S streams, eg. MBC feeds from Eutelsat 21.6e.
As a workaround you can enable "Use HTTP streaming for channels" in HTSP client addon settings.
Can anyone please help with GUI instructions how to have this remote work with LE? Thanks!
Try LE 13 nightly.
So maybe my device simply(?) has a defect.
The most likely issue is an ancient AMD GPU based on TeraScale 2 architecture from 2009.
Try this:
Add
vm.overcommit_memory=2
vm.overcommit_ratio=100
vm.vfs_cache_pressure=1000
to /storage/.config/sysctl.d/sysctl.conf
Also add
MALLOC_ARENA_MAX=1
to /storage/.config/kodi.conf (create the file if it's not there)
Reboot.
when the issue occurs, the system is unresponsive and I have to switch it off to get it to work again
Wyse Thin Client
How much RAM does it have? 1Gb? Unresponsive system could be caused by OOM.
I found a piece of sample content that you can download and try that also exhibits this same issue.
The sample plays on LE13 on my Intel system.
can reliably do end to end true Dolby Vision
It can't, reliably or otherwise.
It wouldn't work on anything other than Android.
(sync playback to display is for a pal user of course enabled).
"Sync playback to display" should never be enabled. "Adjust display refresh rate" should be set to "On start/stop" + fill the whitelist.
Don't enable DRM PRIME on x86. It never worked properly and the option is no more there in LE13.
If you have something that does not play in VAAPI then you'd better open a Kodi github issue (with all the relevant info, log, sample video).
[PATCH net-next v4 00/14] yt6801: Add Motorcomm yt6801 PCIe driver [LWN.net]
https://gitee.com/openeuler/kernel/pulls/16346 < I think this is the latest version of that source.
I attached the kernel patch. It builds successfully with kernel 6.16.4 with the following config options:
CONFIG_NET_VENDOR_MOTORCOMM=y
CONFIG_YT6801=m
CONFIG_DCB=ydiff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c
index 9803347..1ada7b4 100644
--- a/drivers/gpu/drm/i915/display/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
@@ -1927,7 +1927,7 @@ static bool intel_hdmi_source_bpc_possible(struct intel_display *display, int bp
{
switch (bpc) {
case 12:
- return !HAS_GMCH(display);
+ return !HAS_GMCH(display) && DISPLAY_VER(display) <= 10;
case 10:
return DISPLAY_VER(display) >= 11;
case 8:This would apply to kernel 6.16. The change is harmless but I'd rather not merge it to LE, even as a temporary patch.
I've seen weird issues when a 100Mbit device and a 1000Mbit device are connected to the same 1000Mbit switch. Try to limt the RPI's port speed to 100Mbit (100baseT/Full) so both Telestar and RPI would connect at 100Mbit.