Bug 51751

Summary:	(gen3-rendering-limit) Intel Gen3 rendering limits are pitiful
Product:	xorg	Reporter:	mikhail.v.gavrilov
Component:	Server/Ext/RandR	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED MOVED	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium	CC:	mikhail.v.gavrilov
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description mikhail.v.gavrilov 2012-07-05 07:21:48 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=699705

 The initial configuration heuristic places monitors horizontally adjacent.  That makes total display wider than 2048, which is the maximum size that the 3D engine in the 945 can render to.

This should be fixable, if not fixed, by xserver changes to allow each output to have its own memory allocation instead of sharing a single large one, and modifying the compositor to be aware of this.

Comment 1 Chris Wilson 2012-07-05 07:30:28 UTC

The 2D engine is not limited to the constraints of the 3D pipeline. If you look at SNA you can see precisely how that limit can be avoided, and for how operations can be split into pieces that can be handled by the 3D pipeline. The problem is that the 3D compositor has no (efficient) way to workaround those limitations as they are currently also enshrined into OpenGL limits.

The feature request for per-crtc-pixmaps was to be part of randr-1.4. And is better addressed to xorg-devel and Server/Ext/Randr.

Comment 2 mikhail.v.gavrilov 2012-07-05 07:42:52 UTC

Move feature request for per-crtc-pixmaps to Server/Ext/Randr component

Comment 3 GitLab Migration User 2018-12-13 18:33:30 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/228.

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.