Bug 2778

Summary: Support for RageTheatre200 added
Product: xorg Reporter: Bogdan Diaconescu <b_diaconescu>
Component: Driver/RadeonAssignee: Bogdan Diaconescu <b_diaconescu>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: ajax, alexdeucher, mharris
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
RageTheatre200 patch
none
New files for rt200 support none

Description Bogdan Diaconescu 2005-03-20 07:53:58 UTC
The patch adds support for RageTheatre 200 video decoder.
Comment 1 Bogdan Diaconescu 2005-03-20 08:16:31 UTC
Created attachment 2163 [details] [review]
RageTheatre200 patch
Comment 2 Bogdan Diaconescu 2005-03-20 08:19:05 UTC
Created attachment 2164 [details]
New files for rt200 support
Comment 3 Adam Jackson 2005-03-22 11:21:06 UTC
this patch has some whitespace issues.  it looks like you're setting your tab
stops to a weird width and then using ^I to do indentation.  in general explicit
^I characters to mean anything other than "indent eight spaces" are a mistake.

beyond that, how much testing has this patch had?
Comment 4 Bogdan Diaconescu 2005-03-22 14:50:54 UTC
I'm using vim as favourite editor with a diferent than 8 tabstop. The patch is
created with cvs diff command which seems to expand the tab character to 8
spaces. The wrong indentation can be easily fixed with expand tool. I'll do that
when cvs acces will be granted.

The RT200 code in GATOS cvs was tested with success on couple of boards (see the
GATOS mailing lists). The ideea is to broaden the testing by integrating the
code into X.org.
Comment 5 Mike A. Harris 2005-04-27 23:15:37 UTC
Didn't this recently get added to CVS head already?
Comment 6 Bogdan Diaconescu 2005-04-28 00:39:37 UTC
The patches have been added into cvs head.
Comment 7 Bogdan Diaconescu 2005-04-28 00:48:30 UTC
The patch has been added into cvs head. They were tested only on my card 
AIW9600 PRO (PAL).

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.