Re: Compiling Rage xlinit.c

[Steve Longerbeam <stevel@mvista.com>]

Richard Smith wrote:

> Steve Longerbeam wrote:
>
>> What kernel source tree and rev is this? Xlinit.c only supports the
>> Xpert98 card, nothing else, although it might be a simple matter
>> to get it working with other RageXL based cards. It has never been
>> ported to 2.6 either.
>>
>
> Someone chopped on it then because the only place I've ever seen it 
> was in the 2.6 tree.  In the 2.6 tree there is an xlinit.c file and a 
> config option to compile it but it never shows up in the makefile and 
> never gets compiled.  And if it did it would break anyway.
>
> These patches do not appear to be in the 2.4.25 tree.
>
> So I just assumed it was something added for 2.6.  That explains why 
> it dosen't compile.  Also the 2.6 tree xlinit.c mentions the Victoria 
> card as well as the Xpert98. Did someone add that? 


I added that originally, forgot to mention it. Yes, if you were
to by miracle get a hold of a Victoria card, you would see that
it gets initialized fine with xlinit. ATI lent me one for development.
It's very similar to the Xpert98, different video memory type and
pixel clocks though.

>
>
> I'm trying to adapt it to a Mobility M1 which is mach64 based.


Is the M1 Rage XL? If not, I'm not sure xlinit.c will be of much use
to you. Keep in mind that xlinit.c was a serious reverse engineering
hack job. I used a PCI bus analyzer to capture the bus I/O activity
created by the Xpert98's BIOS. Then converted the capture output
to C, and tried to make it look half sensible without breaking the
card init. Most of the delays in xlinit.c are the actual time deltas
reported by the bus analyzer between RageXL register accesses.
The point I'm trying to make is that xlinit.c is verbatim init
activity from specifically the Xpert98 card's BIOS. So I have
very little confidence that it will successfully init any other
type of mach64 card.

This reverse engineering job was necessary because ATI does not
publish documentation on how to initialize their chips, atleast not
for the mach64 family. Maybe that's changed now, but not when
I was doing the work.

Steve

>   I've ported it to a userspace app, fixed up the compile problems and 
> tried to get all the register settings relevant to an M1.  In most 
> cases they are identical.   The pll registers seem to be correct 
> because my hsync and vsync are good and the right frequency but 
> something still isn't right because I only get a blank screen.
>
> If I then load the 2.4.25 atyfb and try to write an image I get a 
> brief flash of some scrambled data and then back to a black screen.
>
> Loading X appears to work fine and I have a big white square for a 
> mouse cursor which moves around as it should  but still black screen.
>
> I suspect that I have something messed up with my memory settings.
>
>
>



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click