linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Osterlund <petero2@telia.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	ajoshi@kernel.crashing.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb patch for 2.4.22...
Date: 15 Jul 2003 14:02:42 +0200	[thread overview]
Message-ID: <m2ptkcknfh.fsf@telia.com> (raw)
In-Reply-To: <1058255052.620.2.camel@gaston>

Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> > >
> > > Which is what the original 0.1.8 patch included, his fixes were included.
> > 
> > Ah really? I though that his changes were not merged in your 0.1.8 patch.
> > 
> > So can I just revert his patch and accept your instead that all of his
> > stuff is in ? Whoaa, great.
> 
> No. 0.1.8 lacks a lot of my stuffs

I have a small problem with radeonfb in 2.4.22-pre5 (+manually created
radeonfb.h file). During boot, when the console is switched over to
the frame buffer device, the screen becomes corrupted. Mostly by white
squares in a grid pattern and some squares with other colors. Between
the squares, normal characters can be seen, but each character is
duplicated. Here is a picture: (not very sharp unfortunately)

        http://w1.894.telia.com/~u89404340/radeonfb.jpg 

Text added after the switch is not corrupted, so eventually the
corruption is scrolled off the screen and after that the framebuffer
appears to be working correctly.

2.4.22-pre3 does not have this problem. I haven't found a patch for
the vanilla 0.1.8 version, so I don't know if that version also has
this problem. I think someone has reported a similar problem in 2.5.x,
but I don't remember the details.

Here are some messages from the kernel log:

Jul 14 23:08:44 best kernel: radeonfb: ref_clk=2700, ref_div=12, xclk=18300 from BIOS
Jul 14 23:08:44 best kernel: radeonfb: panel ID string: Samsung LTN150P1-L02    
Jul 14 23:08:44 best kernel: radeonfb: detected LCD panel size from BIOS: 1400x1050
Jul 14 23:08:44 best kernel: Console: switching to colour frame buffer device 175x65
Jul 14 23:08:44 best kernel: radeonfb: ATI Radeon M7 LW DDR SGRAM 64 MB
Jul 14 23:08:44 best kernel: radeonfb: DVI port LCD monitor connected
Jul 14 23:08:44 best kernel: radeonfb: CRT port no monitor connected

-- 
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340

  reply	other threads:[~2003-07-15 11:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10307141237001.27519-100000@gate.crashing.org>
2003-07-14 18:11 ` Marcelo Tosatti
2003-07-14 18:30   ` ajoshi
2003-07-14 18:40     ` Marcelo Tosatti
2003-07-14 18:55       ` ajoshi
2003-07-14 19:11         ` Marcelo Tosatti
2003-07-14 19:34           ` Damian Kolkowski
2003-07-14 19:36             ` Marcelo Tosatti
2003-07-15  8:47         ` Benjamin Herrenschmidt
2003-07-15  7:44       ` Benjamin Herrenschmidt
2003-07-15 12:02         ` Peter Osterlund [this message]
2003-07-15 13:43           ` Benjamin Herrenschmidt
2003-07-16 10:59 Eric Blade
2003-07-17 17:29 ` James Simmons
2003-07-17 22:43   ` Eric Blade
2003-07-18 17:42     ` James Simmons

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=m2ptkcknfh.fsf@telia.com \
    --to=petero2@telia.com \
    --cc=ajoshi@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --subject='Re: radeonfb patch for 2.4.22...' \
    /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

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).