[Bug 307079] New: restrict video mode within ES1000's capability
https://bugzilla.novell.com/show_bug.cgi?id=307079 Summary: restrict video mode within ES1000's capability Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: liswu@ati.com QAContact: sndirsch@novell.com Found By: --- this bug was originally found in RHLE5 When connect a digital monitor which supports max 1600x1200 resolution, radeon driver will set 1600x1200@24bit mode for output, however, this mode is out of ES1000's capacity. video corruption will occur in this case. How reproducible: Often Steps to Reproduce: 1. install RHEL5 2. connect a digital monitor with max 1600x1200 resolution 3. startX Actual results: video corruption will occur Additional info: Radeon driver has its own mode validation routine for digital monitors, this routine forget to check clock limations for output mode.we add clock range check in this routine to restrict output mode within chip's capability. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=307079#c1 --- Comment #1 from Lisa Wu <liswu@ati.com> 2007-09-02 23:53:40 MST --- Created an attachment (id=161411) --> (https://bugzilla.novell.com/attachment.cgi?id=161411) this patch is against xf86-video-ati 6.6.19x. add pixel clock check while validate mode for DDC mode -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=307079#c2 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |liswu@ati.com --- Comment #2 from Stefan Dirsch <sndirsch@novell.com> 2007-09-03 03:35:22 MST --- Hmm. I would like to see this bugreport discussed upstream first (X.Org bugzilla and possibly also ony xorg ML). Could you add Egbert, Matthias, Luc and me to the upstream bugreport? libv@skynet.be eich@pdx.freedesktop.org mhopf@suse.de sndirsch@suse.de Thanks. I'll set this one to NEEDINFO until the issue has been resolved upstream. The bugreport is reported against SUSE 10.1. I don't think that we'll still fix it for 10.1, but SLES10/SLES10-SP1 (which is based on SUSE 10.1) would be an option. Given we get feedback upstream in time I can also add it for openSUSE 10.3. Let me know, what you think about SLES10/SLES10-SP1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=307079#c3 --- Comment #3 from Lisa Wu <liswu@ati.com> 2007-09-03 03:49:53 MST --- Stefan, git source has now merged randr1.2 branch into master branch, I am not quite sure if legancy pre-randr1.2 driver is still maintained in upstream. Do you think this bug will be taken care of by upstream? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com