Jon Smirl wrote:
I'm fixing the Radeon framebuffer driver to work
correctly when multiple video cards are installed.
If the Radeon is the only card in the system there is
no problem. When framebuffer initializes it uses the
copy of the ROM down in low memory.
When the Radeon is a secondary card
This seems to work. Reading the register back slows
things down enough to make sure the ROM has time to
appear.
/* Fix from ATI for problem with Radeon hardware not
leaving ROM enabled */
unsigned int temp;
temp = INREG(RADEON_MPP_TB_CONFIG);
temp &= 0x00ffu;
temp |= 0x04 << 24;
OUTREG(RADEON_
There was a discussion about posting multiple radeon cards on the devel
and xfree86 MLs just before 4.3.0 was released (feb 2003). Marc and
Hui and several others were involved. If you can find the thread, it
might help you out.
http://marc.theaimsgroup.com/?t=10430550602&r=1&w=2
http://marc
I have verified that the missing ROM is definitely a
problem with RADEON_MPP_TB_CONFIG as referenced in the
posts. I'm still experimenting to find a reliable fix.
It seems that you can't read and set this register at
too high of speed.
Thanks for the pointer.
=
Jon Smirl
[EMAIL PROTECTED]
__
I can check, but my Rage128s don't have this problem.
It's only my Radeon cards.
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
> I seem to recall some discussion about a similar
> issue w/Rage128
> hardware on the old xpert list. I don't remember
> what the conclusion
> was, but the answer might