[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #76 from Krister [EMAIL PROTECTED] 2008-11-27 04:51:55 PST --- This fix solved my problem. Thanks. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #75 from Krister [EMAIL PROTECTED] 2008-11-26 05:16:45 PST --- Sweet. Will upgrade to Ubuntu 8.10 (as the 6.9.0 git won't compile on my 8.04)and try this on my arcade system tonight. I have the exact same probs with the driver as it is today. Let you know the result -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #72 from Andy Burns [EMAIL PROTECTED] 2008-11-24 00:34:28 PST --- (In reply to comment #70) While checking why the mode-CrtcV values are halve of what they should be (like they were in version 6.6.3) I came across the following comment in the function xf86InitialCheckModeForDriver That looks like a much better attempt to stop the problem happening, rather than my approach of fixing it after it has happened, I'm no longer using my VGA-SCART cable, having upgraded to HDMI and switched from Radeon PCIe to a motherboard with Intel video onboard. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #73 from Thomas Dekker [EMAIL PROTECTED] 2008-11-24 03:21:31 PST --- You are a hero! This fixes the resolution and the mouse pointer. Even on my older card which uses the legacy part of the driver. I concern this bug closed \o/ -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 Alex Deucher [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #74 from Alex Deucher [EMAIL PROTECTED] 2008-11-24 23:25:41 PST --- pushed thanks! 065938617c0feab17f4274a5350de02a692ba065 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 Ramon van der Stelt [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #70 from Ramon van der Stelt [EMAIL PROTECTED] 2008-11-23 18:48:29 PST --- While checking why the mode-CrtcV values are halve of what they should be (like they were in version 6.6.3) I came across the following comment in the function xf86InitialCheckModeForDriver (file hw/common/xf86Mode.c): /* * NOTE: We (ab)use the mode-Crtc* values here to store timing * information for the calculation of Hsync and Vrefresh. Before * these values are calculated the driver is given the opportunity * to either set these HSync and VRefresh itself or modify the timing * values. * The difference to the final calculation is small but imortand: * here we pass the flag INTERLACE_HALVE_V regardless if the driver * sets it or not. This way our calculation of VRefresh has the same * effect as if we do if (flags V_INTERLACE) refresh *= 2.0 * This dual use of the mode-Crtc* values will certainly create * confusion and is bad software design. However since it's part of * the driver API it's hard to change. */ In version 6.6.3 the function RADEONPreInitModes (file src/radeon_driver.c) calls xf86SetCrtcForModes which in turn calls xf86SetModeCrtc for each mode with adjustFlag 0. However in version 6.9.0 the new function radeon_mode_fixup (file src/radeon_output.c) only recalculates the mode-Crtc* values for a few specific conditions. Namely when MonType is MT_LCD or MT_DFP and the display resolution is smaller then the panel resolution (and rmx_type is not RMX_OFF and either IS_AVIVO_VARIANT or radeon_crtc_id == 0 is true). This means that at least for CRT monitors the CrtcV* values are left halve from what they should be. To fix this I placed a call to xf86SetModeCrtc with adjustFlag 0 at the start of the radeon_mode_fixup function. But I'm not sure whether this is correct for all radeon cards because as I gather from the previous comments that this problem only seems to show up on older cards (I have a R350). Note that the function radeon_mode_fixup contains two calls to xf86SetModeCrtc with the INTERLACE_HALVE_V flag. But after the call the Crtc* values are recalculated (without adjusting for interlacing or double scanning). However the values CrtcVBlankStart, CrtcVBlankEnd, CrtcHBlankStart and CrtcHBlankEnd are left untouched. The problem with the pointer image placed to high is caused by the halving of the y coordinate in the function radeon_crtc_set_cursor_position when the V_INTERLACE flags is set. This wasn't done in version 6.6.3. Removing it fixes the problem. Note that the y coordinate is doubled when the V_DBLSCAN flag is set. This matched the doubling of the CrtcV values in xf86SetModeCrtc. But the y coordinate is not multiplied with mode-VScan. Also note the corrected values in the 'adjusted_mode' don't seem to be propagated to the various copies of the mode in the xserver data structures. The adjusted_mode is just dropped at the end of the xf86CrtcSetMode function. So when the function RADEONDisplayVideo (radeon_video.c) uses crtc-mode.CrtcVDisplay it gets the halved valued. Unfortunately this is not the cause of xv corruption I am experiencing on the second head (it is not related to interlacing). Attached a patch. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #71 from Ramon van der Stelt [EMAIL PROTECTED] 2008-11-23 18:51:22 PST --- Created an attachment (id=20529) -- (http://bugs.freedesktop.org/attachment.cgi?id=20529) Proposed patch to fix split screen and wrong pointer image placement -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #69 from Thomas Dekker [EMAIL PROTECTED] 2008-10-10 01:18:52 PST --- I opt to commit Andy's fix to git. Nobody new is going to come up with a proper fix for these old drivers. At least this makes it work for a few, and it has no drawbacks. If it breaks again in a future Xorg version we have a better chance of bisecting the real problem. This also prevents users with a similar problem but a different bug from diluting this report and never find help themselves. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #68 from [EMAIL PROTECTED] 2008-10-09 14:19:55 PST --- I've had similar problems getting VGA-Scart (PAL RGB) to work. I have found one and only one way of getting a picture on my TV: add a PAL compatible mode in xorg.conf (not with xrandr), but make sure X starts with a non-interlaced mode on the VGA output (e.g. the automatically added [EMAIL PROTECTED] VESA mode). This gives me an un-synced scrolling picture on the TV. Then use xrandr to change to the PAL mode added in xorg.conf. Any other procedure (starting X with the PAL mode set from the beginning or adding the mode with xrandr) just gives me a black screen (with sync if the mode I set is PAL compatible, without sync otherwise, but always just black). And the TV seems to display whatever it is sent even if it cannot sync to the signal, so it is probably sent a black picture by the graphics card. When it works, the mouse pointer is shown in the wrong position on the TV: at half the y position compared to the correct position. (I.e. if I want to click something at the bottom of the TV screen I have to position the mouse pointer in the middle of the TV screen.) The mouse pointer is not visible in black mode. Using X Window System Version 1.3.0 and xf86-video-ati-6.9.0 (or ati-git-080929; same result). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #59 from Thomas Dekker [EMAIL PROTECTED] 2008-07-22 03:50:31 PST --- I think vsync is calculated wrong when an interlaced modeline is read, since xrandr sets it correctly. Anything i can do to help you? As to pre-avivo chips, unfortunately, I cannot reproduce any problems with with interlaced modes here. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #60 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 08:00:30 PST --- Created an attachment (id=17820) -- (http://bugs.freedesktop.org/attachment.cgi?id=17820) Picture of X1250 with interlaced mode showing VDR. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #61 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 08:01:17 PST --- Created an attachment (id=17821) -- (http://bugs.freedesktop.org/attachment.cgi?id=17821) Picture of X1250 with interlaced mode showing plain X screen. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 Mike Pieper [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #62 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 08:03:21 PST --- (In reply to comment #58) Sorry but the latest git shows exactly the same behavior like before. I've attached two screenshots showing the problem. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #63 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 12:45:28 PST --- With this patch I get on my hardware (X1250 IGP) at least the same behavior like the others, i.e. after switching resolution with xrandr I have a correct picture: diff --git a/src/atombios_crtc.c b/src/atombios_crtc.c index 70650e1..18885e6 100644 --- a/src/atombios_crtc.c +++ b/src/atombios_crtc.c @@ -493,7 +493,7 @@ atombios_crtc_mode_set(xf86CrtcPtr crtc, OUTREG(AVIVO_D1GRPH_X_END + radeon_crtc-crtc_offset, x + mode-HDisplay); OUTREG(AVIVO_D1GRPH_Y_END + radeon_crtc-crtc_offset, y + mode-VDisplay); OUTREG(AVIVO_D1GRPH_PITCH + radeon_crtc-crtc_offset, - crtc-scrn-displayWidth); + crtc-scrn-displayWidth ((adjusted_mode-Flags V_INTERLACE)?1:0)); OUTREG(AVIVO_D1GRPH_ENABLE + radeon_crtc-crtc_offset, 1); OUTREG(AVIVO_D1MODE_DESKTOP_HEIGHT + radeon_crtc-crtc_offset, -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #64 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 13:11:16 PST --- (In reply to comment #63) This patch is not quite correct. Now I can see the whole picture, but I can see only every second line. That means that the lines are doubled by the hardware (like doublescan) and by doubling the pitch in the patch I skip every second line. I played around with the line: src/atombios_crtc.c:655 OUTREG(AVIVO_D1MODE_DATA_FORMAT + radeon_crtc-crtc_offset, AVIVO_D1MODE_INTERLEAVE_EN); It makes no difference if the AVIVO_D1MODE_INTERLEAVE_EN bit is set or not. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #65 from Alex Deucher [EMAIL PROTECTED] 2008-07-22 13:39:59 PST --- How are you adding the interlaced mode? Is it part of the edid from your monitor or a modeline or added at runtime using xrandr? As has been noted, I suspect the xserver may be mangling interlaced modes. Can you attach your xorg log? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #66 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 21:36:20 PST --- Created an attachment (id=17827) -- (http://bugs.freedesktop.org/attachment.cgi?id=17827) Xorg.log for Interlaced mode with two xrandr -s x calls This is the Xorg.log when starting the X-server in interlaced mode. Short after starting I switch the resolution with xrandr -s 1 ; xrandr -s 0. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #67 from Mike Pieper [EMAIL PROTECTED] 2008-07-22 21:40:09 PST --- Created an attachment (id=17828) -- (http://bugs.freedesktop.org/attachment.cgi?id=17828) xorg.conf for X1250 igp with interlaced mode. This is the xorg.conf. The interlaced mode is defined by myself. The same timing works with fglrx. radeonhd doesn't like this mode at all. Only difference to fglrx is that I had to change sync polarity (+hsync - -hsync ...) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #57 from Mike Pieper [EMAIL PROTECTED] 2008-07-21 09:00:56 PST --- Hello, I can confirm that this bug still exists in todays git. I'm using an interlaced mode. As output a TV is connected via SCART. I see the picture doubled with a black line in the middle. The picture is streatched 2 times, i.e. I see two times the first quarter of the picture. Horizontally the picture is correct. My hardware is a Gigabyte Mobo with a X1250 IGP. It would be great if someone could try to fix this. The patch above doesn't work for me. Thanks Mike -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #58 from Alex Deucher [EMAIL PROTECTED] 2008-07-21 21:01:31 PST --- (In reply to comment #57) My hardware is a Gigabyte Mobo with a X1250 IGP. I just fixed some issues with interlaced and avivo cards in git. So the x1250 should work fine now with ati from git master. As to pre-avivo chips, unfortunately, I cannot reproduce any problems with with interlaced modes here. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #54 from Thomas Dekker [EMAIL PROTECTED] 2008-04-27 08:07:08 PST --- Hi, is anyone still looking into this? I have the same problem, and while xrandr does the job, it should be working from the start... I was looking at how the radeon module initializes, and i wonder if perhaps RADEONCrtcFindClosestMode() doesn't honour the interlace flag. All the commits between the working and non-working version seem pretty harmless, but something must have been changed :( -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #55 from Andy Burns [EMAIL PROTECTED] 2008-04-27 08:31:29 PST --- (In reply to comment #54) Hi, is anyone still looking into this? Not had chance to look for a while, my hacky patch works for me, but is clearly not an acceptable solution. I have the same problem, and while xrandr does the job, it should be working from the start... I never got an interlaced mode running with xrandr, can you give me the exact steps you used to do that? what mode did you start X in? did you just switch to an interlaced mode pre-defined in your xorg.conf? or did you define a new mode with xrandr and then switch to it? All the commits between the working and non-working version seem pretty harmless, but something must have been changed :( Yep, but I rapidly got lost in them, doesn't help that my TV is the only monitor on this machine, hardly makes it convenient for editing/viewing large chunks of source code ... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #52 from Steve Newbury [EMAIL PROTECTED] 2008-03-27 08:17:37 PST --- So I guess the question is how does the code path differ between randr and startup. Perhaps the bug is related to where initial mode stucts get filled in, particularly where the xorg.conf modelines get added rather than mode programming itself? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #50 from Steve Newbury [EMAIL PROTECTED] 2008-03-25 07:43:00 PST --- Perhaps it's only not working if the initial start-up mode is interlace? I'm unable to test at the moment since I'm having trouble building the xserver... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #51 from Alex Deucher [EMAIL PROTECTED] 2008-03-25 08:24:45 PST --- (In reply to comment #50) Perhaps it's only not working if the initial start-up mode is interlace? I'm unable to test at the moment since I'm having trouble building the xserver... I'm able to add modes and switch between interlaced/non-interlaced on the fly via xrandr. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #47 from Steve Newbury [EMAIL PROTECTED] 2008-03-24 11:04:38 PST --- Andy, since the new randr code went in the current driver uses completely different code paths for modesetting, a bisect is only of limited usefulness due to this. I don't believe the new code was properly tested for the interlaced (initial mode) case we need. You need to look at what the old (working) code did when initialising interlaced modes and ensure the current code does the same. I did have a look myself previously but couldn't see what was missing. I'll have another look, as you say it's probably in the timings calcs... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #48 from Steve Newbury [EMAIL PROTECTED] 2008-03-24 11:56:27 PST --- OK. It's obviously: xf86SetModeCrtc(adjusted_mode, INTERLACE_HALVE_V) not getting called in every case it should. It seems to get called unconditionally in the i810 driver... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #49 from Andy Burns [EMAIL PROTECTED] 2008-03-24 14:00:07 PST --- (In reply to comment #48) OK. It's obviously: xf86SetModeCrtc(adjusted_mode, INTERLACE_HALVE_V) not getting called in every case it should. Sounds likely, but rather it's being called when it shouldn't be, I'll have to pull down some old git trees for comparison. Still doesn't explain why Alex sees interlace modes with a standard monitor work and I don't (without re-doubling the verticals). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #46 from Andy Burns [EMAIL PROTECTED] 2008-03-23 10:24:54 PST --- I realised I hadn't done any non-interlaced tests, in the case of my TV it doesn't support non-interlaced modes, but I have the CRT monitor available, so I tried 640x480 mode with it, this works fine (with and without my patch, and as expected fails to produce a valid display if I make my patch *NOT* unconditional instead of checking for V_INTERLACE) It seems to me from looking at the register dumps by Michael Haas and from debug prints I put into the driver that *something* has halved the values of vertical registers for interlaced modes, presumably this is happening when the mode values are calculated (or adjusted) rather than (at the stage I inserted my hack) when they are poked into CRTC registers. I tried a git bisect, but rapidly ran back to versions of the driver that the X server refused to load (version compatibility with my server or drm module?) Also I've looked by eye at the diffs between 0abce69f0d826a7ca1a41d963cd4730b6e01c145 and 2618cf2aa8ed76411b943eb90c95869814c2f151 but the merge and fix conflicts in 76670f665ebec7cdf40a04bf9379cb3ad4417507 are a bit too much for me to follow manually, so much other development has happened since that change, makes it difficult to follow code that has been split into other files. Perhaps this problem only affects certain cards, any clue how I can proceed further? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #38 from Andy Burns [EMAIL PROTECTED] 2008-03-19 07:39:02 PST --- (In reply to comment #35) I've just tested interlaced modes with the ati driver currently in git on several cards (RV280, RV350, RS690) and it works perfectly as is. Can you verify that you are still having a problem with the ati driver currently in git? Just checked out the ATI driver sources with git-clone from git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati Ran autogen and make, killed X server, copied over the newly built driver and re-started X server. I can confirm the same issue exists that I originally had. Will attach config and log files. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #40 from Andy Burns [EMAIL PROTECTED] 2008-03-19 07:42:11 PST --- Created an attachment (id=15296) -- (http://bugs.freedesktop.org/attachment.cgi?id=15296) Log file from git 19-MAR-2008 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #42 from Andy Burns [EMAIL PROTECTED] 2008-03-19 08:27:22 PST --- (In reply to comment #41) you can try an interlaced mode (like 1024x768i) on a monitor? Connected a CRT and used the industry standard modeline ModeLine 1024x768 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace Unfortunately, the output is not correct. Only the top half of the screen is displayed, stretched to fill the whole screen, the individual scanlines are quite widely separated, the monitor seems able to lock on to the double frequency sync pulse better than the TV, as you'd expect from a multisync device I suppose, so there isn't a black sync bar visible on screen. Monitor OSD reports frequencies as horizontal 35kHz, vertical 174Hz I don't have a TV to test you PAL modes on. Perhaps forcing a lower min clock would help? The 13MHz clock has worked with all previous drivers for more than 2 years, but I will certainly try forcing it even lower. Config/Log files required for the 1024x768i test? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #45 from Andy Burns [EMAIL PROTECTED] 2008-03-19 10:43:01 PST --- (In reply to comment #41) Perhaps it's just an issue with PAL modes you are using. I think all the people reporting this issue are using PAL modelines. Perhaps forcing a lower min clock would help? Tried using 12.0MHz (which I beleive is the lowest the drive will allow) unfortunately no difference. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #35 from Alex Deucher [EMAIL PROTECTED] 2008-03-17 08:55:54 PST --- (In reply to comment #34) Created an attachment (id=15187) -- (http://bugs.freedesktop.org/attachment.cgi?id=15187) [details] Fix for radeon interlace modes You'll be interested to know I've written a patch to fix this, by doubling the values of the vtotal/vdisplay/vsyncstart CRTC registers when in interlaced modes, the same should probably be done for CRTC2 registers. I've just tested interlaced modes with the ati driver currently in git on several cards (RV280, RV350, RS690) and it works perfectly as is. Can you verify that you are still having a problem with the ati driver currently in git? Note that there are still issues with tiling when using multiple crtcs, but that is being sorted out now. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 12626] Interlaced modes broken in latest git
http://bugs.freedesktop.org/show_bug.cgi?id=12626 --- Comment #36 from Andy Burns [EMAIL PROTECTED] 2008-03-17 10:08:09 PST --- (In reply to comment #35) I've just tested interlaced modes with the ati driver currently in git on several cards (RV280, RV350, RS690) and it works perfectly as is. Can you verify that you are still having a problem with the ati driver currently in git? I'll see if I can figure out git, and try to build from there, have to confess my main interest is in distro released versions. Note that there are still issues with tiling when using multiple crtcs, but that is being sorted out now. Multi-crtc problems wouldn't show up on this machine, the only output is a TV. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
