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 Ben. - 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/
- Follow-Ups:
- References:
- Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Bodo Eggert <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Bodo Eggert <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Kyle Moffett <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Bodo Eggert <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Benjamin Herrenschmidt <[email protected]>
- Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- From: Bodo Eggert <[email protected]>
- Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- Prev by Date: Re: Highmemory Problem with RHEL3 .... 2.4.21-5.ELsmp
- Next by Date: Re: Logitech Quickcam Express USB Address Aquisition Issues
- Previous by thread: Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- Next by thread: Re: Regression: radeonfb: No synchronisation on CRT with linux-2.6.13-rc5
- Index(es):
