From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
Date: Sun, 07 Aug 2005 09:51:07 +0200 [thread overview]
Message-ID: <1123401069.30257.102.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0508051935570.2326@be1.lrz>
On Fri, 2005-08-05 at 19:38 +0200, Bodo Eggert wrote:
> On Fri, 5 Aug 2005, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2005-08-05 at 00:03 +0200, Bodo Eggert wrote:
> > > My CRT is out of sync after radeonfb from 2.6.13-rc5 is initialized.
> > > 2.6.12 does not show this behaviour.
> >
> > I'm out of town at the moment, could you maybe diff radeonfb between
> > working & non-working and CC me the diff ? I don't have my work stuff at
> > hand not my kernel images so...
>
> There were no changes in radeonfb.c, but I could trace to to
> CONFIG_PREEMPT. With _NONE, it works as expected.
Ah ! Interesting... I don't see why PREEMPT would affect radeonfb
though ... Can you try something like wrapper radeon_write_mode() with
preempt_disable()/preempt_enable() and tell me if it makes a
difference ?
Ben.
next prev parent reply other threads:[~2005-08-07 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 22:03 Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5 Bodo Eggert
2005-08-04 22:44 ` Benjamin Herrenschmidt
2005-08-05 17:38 ` Bodo Eggert
2005-08-07 7:51 ` Benjamin Herrenschmidt [this message]
2005-08-07 13:45 ` Kyle Moffett
2005-08-07 16:13 ` Benjamin Herrenschmidt
2005-08-08 1:13 ` Kyle Moffett
2005-08-08 2:41 ` Kyle Moffett
2005-08-07 17:25 ` Bodo Eggert
2005-08-07 21:48 ` Benjamin Herrenschmidt
2005-08-08 0:06 ` Bodo Eggert
2005-08-08 8:19 ` Benjamin Herrenschmidt
2005-08-09 20:13 ` Bodo Eggert
2005-08-09 23:13 ` Bodo Eggert
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=1123401069.30257.102.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=7eggert@gmx.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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