From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Marius_Gr=F6ger?= Subject: Re: Interlace modes with r600 KMS Date: Tue, 07 Sep 2010 17:42:04 +0200 Message-ID: <4C865D4C.30703@googlemail.com> References: <4C85EC2B.6050100@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mail-fx0-f49.google.com (mail-fx0-f49.google.com [209.85.161.49]) by gabe.freedesktop.org (Postfix) with ESMTP id 6ECA79E9D4 for ; Tue, 7 Sep 2010 08:42:23 -0700 (PDT) Received: by fxm12 with SMTP id 12so3951715fxm.36 for ; Tue, 07 Sep 2010 08:42:22 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Alex Deucher Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Am 07.09.2010 16:52, wrote Alex Deucher: > 2010/9/7 Marius Gr=F6ger: >> Hi All, >> >> I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output, X= org >> stack on xorg-edgers, Ubuntu lucid). All interlace modes which are defin= ed >> in EDID seem to be pruned and don't appear in xrandr. Manually adding a = mode >> using xrandr does work, and the TV set detects the mode, but the image s= hows >> horizontal lines. No crash though. >> >> Interlace modes did use to work fine in the past, but I don't know when = they >> ceased to function. >> >> What is the status of interlace modes on this kind of setup? What more t= ests >> or logs would be helpful to analyze the problem? What are other people's >> experiences with this? > > This isn't a driver bug as far as I can tell. At some point the > Xserver started purging interlaced modes. See this bug: > https://bugs.freedesktop.org/show_bug.cgi?id=3D29591 Thanks for the pointer. I did look into the xserver sources a bit and = while I'm far from understanding exactly what's going on, it seems like = the server is relying on output->interlaceAllowed and = output->doubleScanAllowed. Aren't these bools in the domain of the = display driver (granted, this wouldn't be the radeon module but the = xf86-video-ati driver)? Also, as I wrote, the purging seems to be half-done, since I am able to = manually add an interlaced mode. But since that mode doesn't work = properly - does the radeon module support interlaced modes? Is there a = non-X way to verify this? Regards Marius