Bug 6872 - Radeon 7000 option ROM inaccessible w/ digital output enabled
Summary: Radeon 7000 option ROM inaccessible w/ digital output enabled
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: * Other (show other bugs)
Version: git
Hardware: PA-RISC (HP) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2006-05-10 00:51 UTC by Alex Williamson
Modified: 2006-07-03 04:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Radeon 7000 errata (408.72 KB, text/plain)
2006-05-10 00:56 UTC, Alex Williamson
no flags Details
proposed patch (1.40 KB, patch)
2006-05-10 01:47 UTC, Alex Williamson
no flags Details | Splinter Review

Description Alex Williamson 2006-05-10 00:51:34 UTC
ATI has recently released an errata for Radeon 7000 (PCI device ID 0x5159) to
indicate that the video BIOS is inaccessible from an attached serial EPROM when
digital video out is enabled on the chip (ie. when FP2_ON is set).  ia64 systems
have a problem with this as they cannot tolerate the read failure from the PCI
option ROM space.  The workaround is to disable digital video out around the
int10 initialization, allowing the BIOS to be read.  I'll attach the errata
document and a proposed patch.
Comment 1 Alex Williamson 2006-05-10 00:56:37 UTC
Created attachment 5581 [details]
Radeon 7000 errata

ATI has approved distribution of this errata to X.org
Comment 2 Alex Williamson 2006-05-10 01:47:08 UTC
Created attachment 5582 [details] [review]
proposed patch
Comment 3 Michel Dänzer 2006-07-02 14:18:52 UTC
Any reason why this code shouldn't be active on other architectures as well?
Comment 4 Alex Williamson 2006-07-02 22:13:37 UTC
No, this could be activated on all architectures.
Comment 5 Michel Dänzer 2006-07-03 04:13:58 UTC
Thanks, pushed to xf86-video-ati git.


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.