Summary: | [KBL] igt / kms_crtc_background_color is skip | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | cprigent <christophe.prigent> | ||||
Component: | DRM/Intel | Assignee: | Marius Vlad <marius.c.vlad> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | highest | CC: | daniel, intel-gfx-bugs, matthew.d.roper | ||||
Version: | unspecified | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | KBL | i915 features: | display/Other | ||||
Attachments: |
|
Description
cprigent
2016-02-16 17:25:43 UTC
Looks like this might be an IGT bug There's no support in the kernel "background_color" property. For later reference (patches posted on m-l): https://lists.freedesktop.org/archives/intel-gfx/2015-February/060343.html https://lists.freedesktop.org/archives/intel-gfx/2015-October/078687.html https://lists.freedesktop.org/archives/dri-devel/2016-February/100483.html As far as I understand from IRC, the patches were merged and later reverted. Increasing priority due to current milestone impact Marius is correct; the kernel patches haven't landed yet although the (now outdated) IGT patches did somehow. So skipping is the correct behavior for now. The kernel patches have been posted a couple times (last version at https://patchwork.freedesktop.org/series/3265/), but are in a bit of a holding pattern until there's an open source userspace that can take advantage of this feature. When we're ready to merge the kernel patches, there will be some IGT updates to this test as well since the userspace-facing interface has changed slightly. The latest version of this IGT test was last posted by Lionel here: https://patchwork.freedesktop.org/series/3970/ Closing this bug since feature is not yet completed /upstreamed and therefore skip result is expected behavior |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.