From: Alex Deucher <agd5f@yahoo.com>
To: Jon Smirl <jonsmirl@yahoo.com>,
dri-devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Cc: devel@xfree86.org
Subject: Re: [Linux-fbdev-devel] Re: [Dri-devel] Rage128 and Radeon patches
Date: Thu, 14 Aug 2003 11:06:07 -0700 (PDT) [thread overview]
Message-ID: <20030814180607.34519.qmail@web11305.mail.yahoo.com> (raw)
In-Reply-To: <20030814171311.84327.qmail@web14911.mail.yahoo.com>
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.
Alex
--- Jon Smirl <jonsmirl@yahoo.com> wrote:
> --- Alex Deucher <agd5f@yahoo.com> 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
> jonsmirl@yahoo.com
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
next prev parent reply other threads:[~2003-08-14 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 3:43 Rage128 and Radeon patches Jon Smirl
2003-08-14 10:42 ` [Dri-devel] " Benjamin Herrenschmidt
2003-08-14 16:00 ` Jon Smirl
2003-08-14 22:04 ` Benjamin Herrenschmidt
2003-08-14 22:47 ` Jon Smirl
2003-08-15 8:18 ` Benjamin Herrenschmidt
2003-08-14 13:22 ` Alex Deucher
2003-08-14 17:13 ` [Linux-fbdev-devel] " Jon Smirl
2003-08-14 18:06 ` Alex Deucher [this message]
2003-08-14 18:32 ` Steven Newbury
2003-08-14 18:26 ` dri fb drivers [was: Re: Rage128 and Radeon patches] Otto Solares
2003-08-14 18:55 ` dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
2003-08-14 19:33 ` dri fb drivers [was: " James Simmons
2003-08-14 20:18 ` Otto Solares
2003-08-14 21:45 ` Re: dri fb drivers [was: Re: [Linux-fbdev-devel] " Jon Smirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030814180607.34519.qmail@web11305.mail.yahoo.com \
--to=agd5f@yahoo.com \
--cc=devel@xfree86.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).