linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: torn@autistici.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [PATCH] New radeonfb fork
Date: 11 Apr 2003 10:02:37 +0200	[thread overview]
Message-ID: <1050048156.573.14.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <56639.80.180.244.42.1049891938.squirrel@squirrel.autistici.org>

On Wed, 2003-04-09 at 14:38, torn@autistici.org wrote:

> During the kernel compilation  I encountered some problems due tu missing
> #defines. In detail, the probles was in the replacement of
> PCI_DEVICE_ID_PDC_1841 in .._PDC_ADMA100 and of .._CMD_680 in .._SII_680.
> Adding the old lines solved the problem. Maybe you are using a kernel
> patch that modifies that code, and you did the diff against that sources.
> Or (more probably) there is another logic reason I don't see.

Yah, my patch brings pci_ids.h to 2.4.21 version, I'll fix that in
the next patch release

> Another thing I must tell you is that with your driver, but also with the
> old radeonfb and with the xfree86 driver, some strange screen flicker
> occours sometimes. When this happens I see several undefined horizontal
> lines all over the LCD screen. Changing video mode a couple of times makes
> the screen return to normality. I guessed that this behavoir is linked to
> pixclock changes (changing the pixclock value via fbset 2 or 3 times makes
> the screen flicker, another couple of pixclock changes make everyting
> return to normality). Many people with notebooks with mobility M6s graphic
> cards reported this problem. With windows this never happens. This is VERY
> annoying.
> I hope I can help the driver developement, if you want me to try something
> in particular, just tell me.

Looks like the PLL isn't locking properly. The latest driver I'll
release (today hopefully) includes a workaround that _might_ help

> Paride
> torn@autistici.org
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>


-------------------------------------------------------
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  8:01 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 [this message]
2003-04-11 12:47   ` paride
2003-04-11 12:57     ` 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=1050048156.573.14.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).