dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Marius Gröger" <marius.groeger@googlemail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Interlace modes with r600 KMS
Date: Tue, 07 Sep 2010 17:42:04 +0200	[thread overview]
Message-ID: <4C865D4C.30703@googlemail.com> (raw)
In-Reply-To: <AANLkTinr=HV5T5qah3sn4MsHxMbN74HZFbkrdDSFVrri@mail.gmail.com>

Am 07.09.2010 16:52, wrote Alex Deucher:
> 2010/9/7 Marius Gröger<marius.groeger@googlemail.com>:
>> Hi All,
>>
>> I'm not able to use interlace modes (r600 KMS from d-r-t, HDMI output, Xorg
>> stack on xorg-edgers, Ubuntu lucid). All interlace modes which are defined
>> 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 shows
>> 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 tests
>> 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=29591

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

  reply	other threads:[~2010-09-07 15:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  7:39 Interlace modes with r600 KMS Marius Gröger
2010-09-07 14:52 ` Alex Deucher
2010-09-07 15:42   ` Marius Gröger [this message]
2010-09-07 15:53     ` Alex Deucher
2010-09-07 15:56       ` Marius Gröger
2010-09-07 18:06       ` Marius Gröger
2010-09-07 19:00         ` Alex Deucher
2010-09-07 20:07           ` Marius Gröger
2010-09-07 22:00             ` Alex Deucher
2010-09-08  6:12               ` Marius Gröger
2010-09-09 15:03                 ` Alex Deucher
2010-09-09 19:28                   ` Marius Gröger
2010-09-09 19:51                     ` Alex Deucher
2010-09-10  7:14                   ` Marius Gröger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C865D4C.30703@googlemail.com \
    --to=marius.groeger@googlemail.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox