[SKL][HDMI] [Feature request] No overscan properties
Submitted by Tom Hacohen
Assigned to Intel GFX Bugs mailing list
Description
Created attachment 38040
Xorg log.
I don't have overscan properties. Talked to ickle on the IRC chan and he asked me to open a bug.
My Xorg-server version is 1.8.1.902 (latest on arch linux).
My system:
CP:U is core i3-530 which has the following graphic core (according to wikipedia):
Clarkdale GMCH Die:Ironlake
Wotherboard: H55M-USB3.
uname -a: Linux tompc 2.6.34-ARCH #1 (moved) SMP PREEMPT Wed Aug 11 00:23:15 CEST 2010 x86_64 Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz GenuineIntel GNU/Linux
Distro: ArchLinux x86_64
xf86-video-intel version: 2.12.0
Connector: HDMI (name HDMI2) but I guess it's relevant to all.
Attached are the Xorg log, dmesg and output of xrandr --prop --verbose.
Attachment 38040, "Xorg log.":
Xorg.0.log
Activity
added Community Enhancement feature: display/HDMI platform: ILK platform: SKL priority::low + 1 deleted label
Attachment 38041, "dmesg":
dmesgAttachment 38042, "xrandr --prop --verbose (relevant is HDMI2)":
xrandr
@ickleclosed a related bug:*** Bug 30050 has been marked as a duplicate of this bug. ***
@pzanonisaid:I will solve this problem.
For now, there are no Kernel patches, but there are tools that might help you:
- Look for the menus on your TV. Some TVs have options with weird names (like "just scan") that will turn off overscan. This won't require any patch, but won't work with all TVs.
- You can also try to use the "intel_panel_fitter" tool (patch here: http://lists.freedesktop.org/archives/intel-gfx/2012-February/014886.html) and enable the panel fitter to compensate for overscan.
You can also try to play with the AVI InfoFrames, but that's even more complicated: the kernel patches will be easier.
Maybe kernel 3.4 will have this fixed.- Look for the menus on your TV. Some TVs have options with weird names (like "just scan") that will turn off overscan. This won't require any patch, but won't work with all TVs.
@pzanonisaid:Patches proposed to the dri-devel list:
http://lists.freedesktop.org/archives/dri-devel/2012-March/020342.html
http://lists.freedesktop.org/archives/dri-devel/2012-March/thread.html
New versions based on the comments will be proposed soon.
In the meantime, the "intel_panel_fitter" tool is already part of intel-gpu-tools.@rossuploaded an attachment:Attached. It's a dismal monitor.
Attachment 83668, "Lilliput 10" HDMI touchscreen EDID":
edid.raw(In reply to comment 10)
ah, bad-ish news, this monitor doesn't support the overscan/underscan
infoframe (so the work I'm doing right now won't help). It needs the next
level where we play with the panel fitter to compensate the overscan on CE
modes, which should come next.
I got a SKYWORTH 50E780U 50" TV which supports 3840x2160. I can't find kind of "scan" options in the TV settings. I'm not sure how the intel_panel_fitter works.. Could you tell me how I can know if my TV supports the overscan/underscan infoframe?@damiensaid:As far as I know, to support telling the sink to underscan CE modes, you need to have a video capability data block in the EDID telling you the sink can do that.
For that you need the latest version of edid-decode with the patches I just pushed: http://cgit.freedesktop.org/xorg/app/edid-decode
For a samsung TV I have around:
Extended tag: video capability data block
YCbCr quantization: No Data (0)
RGB quantization: No Data (0)
PT scan behaviour: No Data (0)
IT scan behaviour: Support both over- and underscan (3)
CE scan behaviour: Support both over- and underscan (3)
Your 4k TV doesn't have that, so overscans all CE modes. I think we'll need the panel fitter at that point. Now that's not as easy as it seems, the amount of overscan is not defined in the spec.@damienuploaded an attachment:Hey Ross, could you test the attached patch (should apply on recent kernels, need my infoframe refactoring, say 3.12)
Attachment 89911, "Gently ask HDMI sinks to underscan":
0001-drm-Always-ask-the-HDMI-sink-to-underscan.patch@rossuploaded an attachment:Sadly this doesn't work for me. I've attached the EDID from my monitor which is aggressively overscanning when driven by a NUC. I'm sure when I connected it to my Minnow it didn't overscan but I'll replicate that behaviour soon.
Attachment 89962, "Lilliput 1011 EDID":
lilliput-fa1011-npct@jbarnesclosed a related bug:*** Bug 67027 has been marked as a duplicate of this bug. ***
Any update on this one?
How do you properly compensate for overscan with the Intel driver, i.e. how do you underscan?
There's a comment in a nouveau related bug saying:
https://bugs.freedesktop.org/show_bug.cgi?id=47846#c1
Kernel 3.3 introduced underscan control
After updating, you can enable and adjust it using xrandr
eg.
xrandr --output HDMI-1 --set underscan on
xrandr --output HDMI-1 --set "underscan hborder" 54 --set "underscan
vborder" 51"
But that does not seem to work with the Intel driver.
When trying this on an i7-6700K running Ubuntu 16.04 + Oibaf PPA, i.e. with the latest git snapshots of the graphics stack (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers), it results in the following error message:
> X Error of failed request: BadName (named color or font does not exist)
> Major opcode of failed request: 140 (RANDR)
> Minor opcode of failed request: 11 (RRQueryOutputProperty)
> Serial number of failed request: 41
> Current serial number in output stream: 41
Can someone please explain how to properly underscan?
Unfortunately there are still TVs out there which do now allow to disable overscan, so it would be important to have an option to underscan via the driver to compensate for the overscan.
