From: Bodo Eggert <7eggert@gmx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bodo Eggert <7eggert@gmx.de>, 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: Wed, 10 Aug 2005 01:13:57 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0508100113100.2027@be1.lrz> (raw)
In-Reply-To: <Pine.LNX.4.58.0508092140030.2096@be1.lrz>
On Tue, 9 Aug 2005, Bodo Eggert wrote:
> On Mon, 8 Aug 2005, Benjamin Herrenschmidt wrote:
> > On Mon, 2005-08-08 at 02:06 +0200, Bodo Eggert wrote:
> > > The wrong values are constant across reboots (see my first mail), and I
> > > have a CRT.
> > >
> > > Can you tell me where the timing values are read?
> >
> > radeon_write_mode() programs the mode. The monitor timing infos are read
> > by the various bits of code in radeon_monitor.c
> >
> > I'd be curious if you could identify what bit of code is misbehaving
>
> I added preempt_*able around radeon_probe_i2c_connector, and now I get the
> output from below and still no sync. Obviously you shouldn't msleep in
> preempt-disabled code. I'll try voluntary preemption, but that will at
> best hide the error.
Update: voluntary preemption does not cause bad readings.
--
Who is General Failure and why is he reading my disk?
prev parent reply other threads:[~2005-08-09 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 22:03 Bodo Eggert
2005-08-04 22:44 ` Benjamin Herrenschmidt
2005-08-05 17:38 ` Bodo Eggert
2005-08-07 7:51 ` Benjamin Herrenschmidt
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 [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=Pine.LNX.4.58.0508100113100.2027@be1.lrz \
--to=7eggert@gmx.de \
--cc=benh@kernel.crashing.org \
--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
all inboxes | Powered by JetHome®