linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Louis Garcia <louisg00@bellsouth.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb and 2.5.66
Date: 26 Mar 2003 14:34:26 -0500	[thread overview]
Message-ID: <1048707266.2533.1.camel@tiger> (raw)
In-Reply-To: <1048668763.10474.27.camel@zion.wanadoo.fr>

This change had no effect. This is what I get

--Lou


Mar 26 14:28:02 tiger kernel: Journalled Block Device driver loaded
Mar 26 14:28:02 tiger kernel: radeonfb_pci_register BEGIN
Mar 26 14:28:02 tiger kernel: radeonfb: ref_clk=2700, ref_div=12,
xclk=23000 defaults
Mar 26 14:28:03 tiger kernel: radeonfb: probed DDR SGRAM 65536k videoram
Mar 26 14:28:03 tiger kernel: radeonfb: detected DFP panel size from
registers:
1280x1024
Mar 26 14:28:03 tiger kernel: radeonfb: ATI Radeon 7500 QW DDR SGRAM 64
MB
Mar 26 14:28:03 tiger kernel: radeonfb: DVI port DFP monitor connected
Mar 26 14:28:03 tiger kernel: radeonfb: CRT port no monitor connected
Mar 26 14:28:03 tiger kernel: radeonfb_pci_register END
Mar 26 14:28:03 tiger kernel: hStart = 680, hEnd = 960, hTotal = 1056
Mar 26 14:28:03 tiger kernel: vStart = 402, vEnd = 421, vTotal = 442
Mar 26 14:28:03 tiger kernel: h_total_disp = 0x4f0083^I   hsync_strt_wid
= 0xa302a2
Mar 26 14:28:03 tiger kernel: v_total_disp = 0x18f01b9^I  
vsync_strt_wid = 0x930191
Mar 26 14:28:03 tiger kernel: post div = 0x8
Mar 26 14:28:03 tiger kernel: fb_div = 0x59
Mar 26 14:28:03 tiger kernel: ppll_div_3 = 0x30059
Mar 26 14:28:03 tiger kernel: ron = 712, roff = 16464
Mar 26 14:28:03 tiger kernel: vclk_freq = 2503, per = 588
Mar 26 14:28:03 tiger kernel: Console: switching to colour frame buffer
device 80x25
Mar 26 14:28:03 tiger keytable: Loading keymap:



On Wed, 2003-03-26 at 03:52, Benjamin Herrenschmidt wrote:
> On Wed, 2003-03-26 at 00:07, Louis Garcia wrote:
> > When I use video=radeonfb:dfp my monitor just goes into power saving
> > mode (shuts off). This is what I get in the logs: If someone needs more
> > info let me know. By the way I'm on a Intel x86 box.
> 
> Try that: around line 2065, change:
> 
> 	newmode.tmds_transmitter_cntl = (TMDS_RAN_PAT_RST |
> 					 ICHCSEL | TMDS_PLL_EN) &
> 					 ~(TMDS_PLLRST);
> 
> to:
> 
> 	newmode.tmds_transmitter_cntl = (TMDS_RAN_PAT_RST | ICHCSEL) &
> 					 ~(TMDS_PLLRST);
> 
> And tell me if that helps
> 
> Ben.
> 



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

  reply	other threads:[~2003-03-26 19:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  4:39 radeonfb and 2.5.66 Louis Garcia
2003-03-25 15:00 ` Benjamin Herrenschmidt
2003-03-25 15:08   ` Geert Uytterhoeven
2003-03-25 23:07     ` Louis Garcia
2003-03-26  8:52       ` Benjamin Herrenschmidt
2003-03-26 19:34         ` Louis Garcia [this message]
2003-03-27 19:04     ` Louis Garcia
2003-03-27 20:41       ` Benjamin Herrenschmidt
2003-03-27 22:29         ` Louis Garcia
2003-03-25 15:31   ` Sven Luther
2003-03-25 15:34     ` Benjamin Herrenschmidt
2003-03-25 15:35       ` Sven Luther

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=1048707266.2533.1.camel@tiger \
    --to=louisg00@bellsouth.net \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --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).