Can an Xfree developer apply this fix to Rage128 and Radeon drivers? I have tested it with the framebuffer drivers and it works without problem. It should have no downside in single card cases.
The problem is that after reset the Rage128/Radeon BIOSs may not leave the hardware ROM enabled. This code enables it. The extra INREG at the botton is needed to slow things down and give the hardware time to change. --- Steven Newbury <[EMAIL PROTECTED]> wrote: > On Thu, 2003-08-14 at 19:06, Alex Deucher wrote: > > I haven't tried multiple radeon cards, but I seem > to recall several > > people having this problem right around when 4.3.0 > was released. I > > don't think a "proper" fix ever went in and I > think the issue was to be > > revisited later. I don't know if it's needed > anymore or not. > > > It is still needed, Radeon as a secondary display > only works on the > first initialisation (it can not find ROM on > subsequent attempts) in all > XFree86 versions I have tried up to and including > current CVS. At least > on my hardware... :-/ > > > Alex > > > > --- Jon Smirl <[EMAIL PROTECTED]> wrote: > > > --- Alex Deucher <[EMAIL PROTECTED]> wrote: > > > > > 2) access ROM directly instead of relying on > copy > > > > > in low RAM. This allows multiple cards. > Required > > > > > MPP_TB_CONFIG fix in driver. > > > > > > > > Is this patch necessary for xfree86? It may > address > > > > some of the issues > > > > in the email threads I sent out yesterday (ie, > > > > problems with multiple > > > > radeon cards and xfree86). if so would you > consider > > > > making one? > > > > > > > > > > Xfree code does not have the patch, but is Xfree > > > experiencing the bug? Xfree accesses the > hardware very > > > differently than the framebuffer drivers. > > > > > > I suspect that you would see this problem if you > were > > > using something else for your primary video and > a > > > Radeon for secondary. The first time you ran > Xfree it > > > would work. But when you exited and restarted > Xfree it > > > would hang when starting the secondary display. > > > > > > Where does XFree reset the secondary card? The > code > > > below needs to run right after the reset in the > radeon > > > driver. I added it to my Rage128 driver too but > I have > > > not observed the problem with them. > > > > > > Framebuffer code is different and triggers the > bug the > > > first time the secondary display is accessed. > > > > > > /* Fix from ATI for problem with Radeon hardware > not > > > leaving ROM enabled */ > > > unsigned int temp; > > > temp = INREG(RADEON_MPP_TB_CONFIG); > > > temp &= 0x00ffffffu; > > > temp |= 0x04 << 24; > > > OUTREG(RADEON_MPP_TB_CONFIG, temp); > > > temp = INREG(RADEON_MPP_TB_CONFIG); > > > > > ===== Jon Smirl [EMAIL PROTECTED] __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
