Summary: | ati/radeon_mergedfb.c won't build without Xinerama | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Simon 'corecode' Schubert <corecode> | ||||
Component: | Driver/Radeon | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | high | CC: | alexdeucher, kem, thomas | ||||
Version: | git | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 351 | ||||||
Attachments: |
|
Description
Simon 'corecode' Schubert
2004-08-25 02:41:16 UTC
Created attachment 723 [details] [review] fix compilation without Xinerama This might get around the compilation problem, but if Xinerama is not compiled in, then should the Radeon MergedFB Xinerama support be compiled in? Probably not. Adding Alex Deucher for comments. I think we should be ok. the sis and radeon drivers provide their own xinerama extension by default, but it gets disabled if the real xinerama extension is active. this fix will probably do it since the "pseudo-xinerama" extension is self-contained in the driver. Thomas might have more insight as he initially wrote most of this code. The SiS and radeon pseudo-Xinerama is, as Alex correctly mentioned, entirely driver-contained. Hence, it is in fact a driver feature. Without this feature, MergedFB mode is pretty much useless for the end user. This feature takes about 10k of the compiled binary, and it can be disabled by an option. I do not see any reason for skipping compilation if the server-internal Xinerama (which is much more complicated and therefore bug-prone) is not being compiled. There is not the slightest connection between them. That sounds reasonable. Patch checked in. Closing. |
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.