From: Jurriaan <thunder7@xs4all.nl>
To: linux-fbdev-users@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Radeon 7000 problems with kernels after 2.6.3
Date: Fri, 26 Mar 2004 12:47:39 +0100 [thread overview]
Message-ID: <20040326114739.GA32596@middle.of.nowhere> (raw)
On recent kernel (2.6.4 and later) my Radeon 7000 doesn't display
anything. My Eizo monitor warns me of really incompatible frequencies
(fV 217.2 Hz, fH 271.5 kHz). fbset returns normal values, by the way.
I've found out that this chunk in patch-2.6.4, applying to
drivers/video/aty/radeon_base.c, causes my problems:
@@ -1329,6 +1320,16 @@
* not sure which model starts having FP2_GEN_CNTL, I assume anything more
* recent than an r(v)100...
*/
+#if 0
+ /* XXX I had reports of flicker happening with the cinema display
+ * on TMDS1 that seem to be fixed if I also forbit odd dividers in
+ * this case. This could just be a bandwidth calculation issue, I
+ * haven't implemented the bandwidth code yet, but in the meantime,
+ * forcing uses_dvo to 1 fixes it and shouln't have bad side effects,
+ * I haven't seen a case were were absolutely needed an odd PLL
+ * divider. I'll find a better fix once I have more infos on the
+ * real cause of the problem.
+ */
while (rinfo->has_CRTC2) {
u32 fp2_gen_cntl = INREG(FP2_GEN_CNTL);
u32 disp_output_cntl;
@@ -1362,6 +1363,9 @@
uses_dvo = 1;
break;
}
+#else
+ uses_dvo = 1;
+#endif
if (freq > rinfo->pll.ppll_max)
freq = rinfo->pll.ppll_max;
if (freq*12 < rinfo->pll.ppll_min)
If I change that #if 0 to #if 1, I get a normal image. This is with the
following video-card:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Radeon 7000/Radeon
Flags: bus master, stepping, 66Mhz, medium devsel, latency 64, IRQ 16
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at a000 [size=256]
Memory at e5000000 (32-bit, non-prefetchable) [size=512K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
I've seen other messages about problems with radeonfb. Can other people
confirm this problem, and confirm that removing this chunk fixes the
problem?
Kind regards,
Jurriaan
--
Don't like these taglines? Steal your own...
Debian (Unstable) GNU/Linux 2.6.5-rc2-mm3 3940 bogomips 0.18 0.28
reply other threads:[~2004-03-26 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040326114739.GA32596@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-fbdev-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®