Bug 1963

Summary: PCI probe on Linux fails if bus 0 isn't populated
Product: xorg Reporter: Egbert Eich <eich>
Component: Server/DDX/XorgAssignee: Egbert Eich <eich>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: roland.mainz
Version: 6.8.1   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
[FIXED_X11R68x] Fix roland.mainz: 6.8-branch+

Description Egbert Eich 2004-11-30 00:15:41 UTC
The OS specific PCI probing code for Linux has a heuristic to check for the
presence of /proc/bus/pci/00. This only works if bus 0 is really populated which
may not always be the case.
Comment 1 Egbert Eich 2004-11-30 00:18:33 UTC
Created attachment 1424 [details] [review]
[FIXED_X11R68x] Fix

Attached fix probes for presence of /proc/bus/pci/<bus_num>,
using the bus number we want to probe.
Comment 2 Egbert Eich 2004-11-30 00:43:59 UTC
Fixed in CVS head.
Comment 3 Roland Mainz 2004-12-08 05:54:56 UTC
Comment on attachment 1424 [details] [review]
[FIXED_X11R68x] Fix

Approved in the 2004-12-06 release-wranglers conference call.
Please do not commit it yourself, I'll do that later today...
Comment 4 Roland Mainz 2004-12-14 21:48:40 UTC
Comment on attachment 1424 [details] [review]
[FIXED_X11R68x] Fix

Patch checked-in into X11R6.8.x stable branch:

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.365.2.77; previous revision: 1.365.2.76
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
/cvs/xorg/xc/programs/Xserver/hw/xfree86/os-support/bus/linuxPci.c,v  <-- 
linuxPci.c
new revision: 1.3.4.1; previous revision: 1.3
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
Mailing the commit message to xorg-commit@lists.freedesktop.org...

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.