Bug 1928

Summary: Bail out early of atiprobe when no PCI chips are found PCI
Product: xorg Reporter: Egbert Eich <eich>
Component: Driver/mach64Assignee: Egbert Eich <eich>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: roland.mainz
Version: 6.8.1   
Hardware: All   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
[FIXED_X11R68x] Fix roland.mainz: 6.8-branch+

Description Egbert Eich 2004-11-26 05:56:01 UTC
Added some early bailouts to atiprobe if PCI structure pointer is
NULL to prevent sig11.
Comment 1 Egbert Eich 2004-11-26 05:57:42 UTC
Created attachment 1387 [details] [review]
[FIXED_X11R68x] Fix

Committed to head already. Submitted for nomination for 6.8.2.
Comment 2 Roland Mainz 2004-12-08 05:57:53 UTC
Comment on attachment 1387 [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 3 Roland Mainz 2004-12-15 00:04:33 UTC
Comment on attachment 1387 [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.85; previous revision: 1.365.2.84
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/drivers/ati/atiprobe.c,v  <-- 
atiprobe.c
new revision: 1.3.2.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...
Comment 4 Roland Mainz 2004-12-15 00:05:48 UTC
Patch checked-in into Xorg trunk and X11R6.8.x stable branch...

... marking bug as FIXED (please reopen this bug report if there are any
outstanding problems etc. etc.) ...

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.