Bug 107840 - Framebuffer: Driver reports wrong max dimensions
Summary: Framebuffer: Driver reports wrong max dimensions
Status: RESOLVED DUPLICATE of bug 102508
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/modesetting (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL: https://cgit.freedesktop.org/drm-tip/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-05 12:46 UTC by Kristian Robertsen
Modified: 2018-09-06 02:18 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Kristian Robertsen 2018-09-05 12:46:14 UTC 
The driver reports wrong maximum framebuffer dimensions for newer generation GPUs. 

While (at least) 7th gen and up support 16384x16384 the driver reports 8192x8192 for any 4th gen GPU or higher.

Causes display servers to crash with ultrawide and 4K monitors.
Comment 1 Chris Wilson 2018-09-05 13:03:10 UTC 
What the kernel reports is the maximum of an individual pipe. That -modesetting cannot stitch together per-crtc pixmaps to overcome HW limitations is a functional regression in switching to -modesetting. There are different ways to overcome that, Ville has a plan to transparently hide the limitation, the one advantage to handling it inside userspace (where it has been done previously) is that it just works against any kernel and device.
Comment 2 Daniel van Vugt 2018-09-06 02:18:14 UTC 
Duplicate of bug 102508 ?
Comment 3 Daniel van Vugt 2018-09-06 02:18:38 UTC 

*** This bug has been marked as a duplicate of bug 102508 ***

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.