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? 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to