On 6/18/05, Nicolai Haehnle <[EMAIL PROTECTED]> wrote: > On Saturday 18 June 2005 08:20, Benjamin Herrenschmidt wrote: > > On Fri, 2005-06-17 at 18:37 +0200, Jerome Glisse wrote: > > > Correct value (previous were ones of a dumb test :)): > > > > > > 0x0148 0xf7fff000 RADEON_MC_FB_LOCATION > > > 0x014c 0xfdfffc00 RADEON_MC_AGP_LOCATION > > > > Those look much better. If changing those help for us, then I was right > > saying that our hacks are no good :) More specifically, for r300, for > > some reason, we still put the FB at 0 in card space, which isn't a > > terrific idea, and for both r200 and r300, we incorrectly use > > CONFIG_APER_SIZE for sizing the memory controller apertures instead of > > the actual memory size. > > Consider the following steps: > 1. Load fglrx > 2. Unload fglrx > 3. Load r300 (without reboot) > 4. r300 runs just fine without lockups > > However, r300 obviously overwrites the RADEON_MC_FB/AGP_LOCATION registers. > So while it is obviously a good idea to fix our behaviour here, I'm afraid > it would be highly surprising if those registers were the cause of lockups.
Yes if they are in my list this is because the dump i diffed were before the r300 restart anyway after the r300 restart other reg of my list keep their value. Right now i am writting random stuff in random place near unknow reg hopping to see their value change, i only succeed in lockup the computer :( Hope the reg related to the one in my list aren't too far in address space... Jerome Glisse ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
