Bug 17597 - Radeon X1250 0x1002,0x7942
Summary: Radeon X1250 0x1002,0x7942
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: x86 (IA32) Linux (All)
: medium enhancement
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2008-09-15 16:41 UTC by Rafi Rubin
Modified: 2010-03-27 11:28 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Patch against Mesa master describing Radeon 0x7942 as an RS690 (1.03 KB, patch)
2008-09-15 19:52 UTC, Corbin Simpson
no flags Details | Splinter Review

Description Rafi Rubin 2008-09-15 16:41:20 UTC
Hello, what can I do to help get my chip supported?  I'm not quite sure if its a RS600 or RS690.

(II) RADEON(0): ATOM BIOS Rom: 
        SubsystemVendorID: 0x1028 SubsystemID: 0x0204
        IOBaseAddress: 0xee00
        Filename: br26397.bin 
        BIOS Bootup Message: 
ATI Radeon Xpress 1250 for Dell/Parker
Comment 1 Corbin Simpson 2008-09-15 19:50:52 UTC
I'm attaching a patch that will detect 0x7942 as an RS690. Please use "lspci -v | grep VGA" to confirm that it's an RS690; use attached patch at your own risk and make sure that you're on Mesa 7.1 or newer.
Comment 2 Corbin Simpson 2008-09-15 19:52:24 UTC
Created attachment 18896 [details] [review]
Patch against Mesa master describing Radeon 0x7942 as an RS690
Comment 3 Alex Deucher 2008-09-16 07:37:34 UTC
RS600 will need drm updates to support 3D as the gart setup is very different from other asics.  We'll try and get those updates rolled out when we get the r6xx 3D stuff out.
Comment 4 Corbin Simpson 2010-03-27 05:48:52 UTC
Tagging patch; will triage later.

(Corbin, you lazy asshole, you don't remember if you applied this!? Don't forget to check the r300g chipset list too!)
Comment 5 Alex Deucher 2010-03-27 11:28:42 UTC
RS600 support is already in r300c and r300g.


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.