Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
Equinix is shutting down its operations with us on April 30, 2025. They have graciously supported us for almost 5 years, but all good things come to an end. We are expecting to transition to new infrastructure between late March and mid-April. We do not yet have a firm timeline for this, but it will involve (probably multiple) periods of downtime as we move our services whilst also changing them to be faster and more responsive. Any updates will be posted in freedesktop/freedesktop#2011 as it becomes clear, and any downtime will be announced with further broadcast messages.
Project 'drm/intel' was moved to 'drm/i915/kernel'. Please update any links and bookmarks that may still have the old path.
[SKL][HDMI] [Feature request] No overscan properties
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.
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.
I have moved to a new country so I don't have access to my previous TV and setup. Unfortunately there's nothing I can do to confirm or deny the success.
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.
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?
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.
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.
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.
Yeah we need both the infoframe stuff (works for some sinks) and pfit based overscan compensation. The latter has a JIRA open for it too: VIZ-1627, which Paulo owns. Classifying this one as an RFE.
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.
> 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.
I'm still not seeing any native options available.
It would also help if the implementation of this provided underscanning outside of X (on the kernel framebuffer), and had some kind of boot option. nouveau's implementation of xrandr --set underscan on at least applies to the framebuffers. It's not exactly usable without running X to set it, though...
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.
Another thought came to mind: This needs to be implemented outside of X for Wayland to have underscanning.
Also, to clarify what the "this" is that I'm referring to: There are numerous TVs that do not honor overscan/underscan HDMI preferences, and do not provide any way to disable the overscanning that they are performing. The kernel framebuffer feature I am looking for is an option to force outputting an underscanned image to compensate for a display that forces overscanning on everything.
First of all. Sorry about spam.
This is mass update for our bugs.
Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!
If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
commit 6c4f52dca36f ("drm/connector: Allow creation of margin props alone")
decoupled the margin properties from the TV encoder stuff in drm core. Now we just need someone to hook them up to the i915 DP/HDMI/etc. code.
@banns and @knikkane
May I know any proposed solution for it? Our NSA customers make stand-alone Linux server in Intel platforms for HOME environment and it will work directly with TV. Most of TVs don’t provide underscan then need of mechanism of overscan compensation.
Thanks!
Gary
Yes. There is no this feature in i915. May I know any plan to support it?
Support AVI infoframe hints to control this, allow override with panel fitter on uncooperative sinks using properties.
Pipe scaler will be used for dynamic pipe scaling of blended data to CRTC. User space should be able to utilize pipe scaler dynamically without doing any modeset.
Example: xrandr --output HDMI-1 --set underscan on