linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: paride <torn@autistici.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH] New radeonfb fork
Date: 11 Apr 2003 14:57:10 +0200	[thread overview]
Message-ID: <1050065830.559.25.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <3E96B979.8030007@autistici.org>

On Fri, 2003-04-11 at 14:47, paride wrote:
> Benjamin Herrenschmidt wrote:
> > Looks like the PLL isn't locking properly. The latest driver I'll
> > release (today hopefully) includes a workaround that _might_ help
> 
> I hope so, fixing this issue will make many toshiba and hp users very 
> happy. There are two more thing I think it's better to tell you:
> 
> 1) This happened also with the standard radeonfb. When the driver is 
> loaded, the whole screen image is moded up of about 3 or 4 mm. So the 
> upper part of the screen is cut, and at the bottom there is a black 
> strip. "fbset -vsync high" fixes this perfectly, so this isn't a real 
> problem, maybe is just a characteristic of my hardware, telling you 
> shouldn't hurt.

Just to make sure I understood you, this also happens with my
driver or not ? It's possible that your monitor EDID information
as provided by the BIOS is slightly incorrect, I'll look if there
is no parsing error on my side. Can you send me a dmesg output ?

> 2) when switching from x to console, happens that when the text scrolls 
> outside the screen, it reappears in the bottom part of the screen, very 
> bigger, and everything gets messed up. I don't know if this could be 
> related to the flicker problem, but it never happened with the old 
> radeonfb. Playing a bit with fbset solves the problem. I didn't 
> understand exactly what causes this, I'm investigating.

Isn't fixed by my latest version (URL below) ? 
http://www.penguinppc.org/~benh/radeonfb-041103-2.4.20.diff
http://www.penguinppc.org/~benh/radeonfb-041103-2.4.21-pre7.diff


Ben.



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

      reply	other threads:[~2003-04-11 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 12:38 [PATCH] New radeonfb fork torn
2003-04-11  8:02 ` Benjamin Herrenschmidt
2003-04-11 12:47   ` paride
2003-04-11 12:57     ` Benjamin Herrenschmidt [this message]

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=1050065830.559.25.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=torn@autistici.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;
as well as URLs for NNTP newsgroup(s).