Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 116666

Summary: Xorg needs PCI domain support
Product: Gentoo Linux Reporter: Evan Langlois <evan>
Component: [OLD] UnspecifiedAssignee: Gentoo X packagers <x11>
Status: RESOLVED UPSTREAM    
Severity: major CC: sparc
Priority: High    
Version: unspecified   
Hardware: Sparc   
OS: Linux   
URL: https://bugs.freedesktop.org/show_bug.cgi?id=2368
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Here's the fix!

Description Evan Langlois 2005-12-24 23:23:50 UTC
Xorg 6.8.2 does not have PCI Domain support and this will break when using a 2.6 kernel on a Sparc, and quite possible other server systems that have multiple PCI domains.  The existing code only works if the video card is in PCI domain 0, and domains outside domain 0 are not scanned.
Comment 1 Evan Langlois 2005-12-24 23:26:17 UTC
Created attachment 75483 [details, diff]
Here's the fix!

This patch is largely the work of others, just cleaned up, bugs fixed, and tested.  This has been sent upstream to freedesktop.org's bugzilla into bug #2368, but I would prefer if gentoo could include it as one of Xorg's many patches since it may take some time before it goes official.

If you have a 2.6 kernel and multiple PCI domains, you likely need this patch to run Xorg.
Comment 2 SpanKY gentoo-dev 2005-12-24 23:33:22 UTC
i'm pretty sure we already have a patch in place which hacks around the issue so that xorg is at least usuable for the most part
Comment 3 Evan Langlois 2005-12-25 01:49:28 UTC
The existing work-around only works for domain 0.  I cannot get a video card into domain 0 on my system, and I'm pretty sure there are likely other people with the same problem.  A 14K patch and no one has to move around video cards trying to get into domain 0 again - it will just work.
Comment 4 Joshua Baergen (RETIRED) gentoo-dev 2005-12-25 22:59:33 UTC
We don't add patches to any X packages without them being accepted upstream first.  I'll mark this bug upstream since that's where this has to be pushed first.

6.8.2 is purely in maintenance mode right now - we won't add the patch there regardless.  It'll go into 7.0 (modular) once upstream accepts it.