From: Oystein Haare <lkml-account@mazdaracing.net>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RadeonFB
Date: Thu, 18 Mar 2004 10:56:57 +1000 [thread overview]
Message-ID: <1079571417.12324.8.camel@dawn> (raw)
In-Reply-To: <Pine.LNX.4.44.0403172215240.19415-100000@phoenix.infradead.org>
Yes. The following is from 2.6.1:
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=12, xclk=22000 from BIOS
radeonfb: probed DDR SGRAM 65536k videoram
radeonfb: panel ID string: LCD
radeonfb: detected DFP panel size from BIOS: 1280x800
radeonfb: ATI Radeon M9 Lf DDR SGRAM 64 MB
radeonfb: DVI port LCD monitor connected
radeonfb: CRT port no monitor connected
radeonfb_pci_register END
If I understand correctly, radeonfb has gotten a rewrite some time after
2.6.1... (In the kernel configuration you have an option to choose
"Radeon (old driver)" in 2.6.4), so there might be a bug in the panel
size detection stuff in the new driver?
On Thu, 2004-03-18 at 08:17, James Simmons wrote:
> Is there any different in the dmesg output between each kernel version?
>
>
> On Tue, 16 Mar 2004, Oystein Haare wrote:
>
> > Hi!
> >
> > I'm having some problems with radeon framebuffer and the newer kernels.
> > I have a HP/Compaq nx7010 laptop computer, that is supposed to have a
> > Radeon 9200 graphics board.
> >
> > Now.. in 2.6.1, it seems to work ok. But in 2.6.4 it just flickers alot.
> > Are there anyone else than me experiencing this problem?
> >
> > This is what it outputs:
> >
> > radeonfb: Found Intel x86 BIOS ROM Image
> > radeonfb: Retreived PLL infos from BIOS
> > radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=250.00 Mhz,
> > System=220.00 MHz
> > Non-DDC laptop panel detected
> > radeonfb: Monitor 1 type LCD found
> > radeonfb: Monitor 2 type no found
> > radeonfb: panel ID string: Samsung LTN150P1-L02
> > radeonfb: detected LVDS panel size from BIOS: 1400x1050
> > radeondb: BIOS provided dividers will be used
> > radeonfb: Assuming panel size 1400x1050
> > radeonfb: Power Management enabled for Mobility chipsets
> > radeonfb: ATI Radeon Lf DDR SGRAM 64 MB
> >
> > Could the flickering have something to do with the fact that the lcd
> > panel on my laptop can only do 1280x800 resolution? Or doesn't the
> > 1400x1050 have anything to do with resolution at all?
> >
> > PS: Please CC replies to me as I am not on the list.
> >
> > thanks
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
next prev parent reply other threads:[~2004-03-18 0:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 16:01 RadeonFB Oystein Haare
2004-03-17 22:17 ` RadeonFB James Simmons
2004-03-18 0:56 ` Oystein Haare [this message]
[not found] ` <1080187819.2763.1.camel@kennedy>
2004-03-25 22:38 ` RadeonFB Benjamin Herrenschmidt
2004-03-26 4:19 ` RadeonFB Oystein Haare
2004-03-26 4:27 ` RadeonFB Benjamin Herrenschmidt
2004-03-26 4:49 ` RadeonFB Oystein Haare
2004-03-26 4:58 ` RadeonFB Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2002-01-13 16:02 radeonfb Jacek Popławski
2002-01-13 19:01 ` radeonfb Benjamin Herrenschmidt
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=1079571417.12324.8.camel@dawn \
--to=lkml-account@mazdaracing.net \
--cc=jsimmons@infradead.org \
--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