All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Eriksson <aeriksson@fastmail.fm>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, xorg-driver-ati@lists.x.org
Subject: Re: Radeon jittery post 2.6.35
Date: Wed, 16 Mar 2011 21:09:15 +0100	[thread overview]
Message-ID: <4D8118EB.2070209@fastmail.fm> (raw)
In-Reply-To: <AANLkTimboMAFkqTUOwP9m2z361TM_EgthQO07T5Y_az1@mail.gmail.com>

 On 03/15/11 22:46, Alex Deucher wrote:
>  Try booting with radeon.audio=0 on 2.6.38rc, some TVs have problems
> with the hdmi packets we send by default.  disabling audio will treat
> the hdmi like dvi.
>
> Alex
You seem to be on to something there. radeon.audio=0 removes
what appears to be all of the jitter. I say "appear", because during
my many test runs today, I've come across moments where my brain
goes "wasn't what I just noticed on the TV something abnormal?" Both
in fb mode (post KMS), and in X11. It's definetly improved from useless
for family use, to perfectly ok though.

Back when the radeonhd and radeon X drivers where on par, HDMIAudio
where first introduced in the radeonhd driver. I recall testing HDMIAudio
sucessfully then, but haven't used HDMUAudio since, and have switched to
the radeon driver. Now when I check for HDMIAudio (with and without that
command line option), I come up blank (all I see is an S/PDIF output). Isn't
HDMIAudio supported on this card? I googled up a post suggesting that it
was ported to R600+ cards in the radeon driver which would suggest that
the RS690 driver doesn't support it(?).

If at all possible, I'd like to have HDMIAudio operational as the HW
supports it.

A couple of data points:
* Disabling HDMIAudio in the BIOS does not change anything (GRUB bad,
KMS fixes it, etc..)
* A pm-suspend cycle with the TV powered on is enough to turn a
jitter-free session jittery (if I don't use radeon.audio=0)

Any patches I can try (either to add support, or fixup what's currently
broken w/ HDMIAudio?)

-Anders


  reply	other threads:[~2011-03-16 20:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 14:08 Radeon jittery post 2.6.35 Anders Eriksson
2011-03-13 17:15 ` Arthur Titeica
2011-03-13 17:15   ` Arthur Titeica
2011-03-14 20:35   ` Anders Eriksson
2011-03-14 20:35     ` Anders Eriksson
2011-03-14 22:20 ` Alex Deucher
2011-03-14 22:20   ` Alex Deucher
2011-03-14 22:22   ` Alex Deucher
2011-03-14 22:22     ` Alex Deucher
2011-03-15  8:35     ` Anders Eriksson
2011-03-15 20:58     ` Anders Eriksson
2011-03-15 20:58       ` Anders Eriksson
2011-03-15 21:08       ` Jerome Glisse
2011-03-15 21:08         ` Jerome Glisse
2011-03-16 21:40         ` Anders Eriksson
2011-03-15 21:46       ` Alex Deucher
2011-03-16 20:09         ` Anders Eriksson [this message]
2011-03-18  8:55           ` Anders Eriksson
2011-04-24  9:24             ` Anders Eriksson
2011-04-25 14:53               ` Jerome Glisse
2011-04-27 12:16                 ` Anders Eriksson
2011-03-15  8:18   ` Anders Eriksson
2011-03-15  8:18     ` Anders Eriksson

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=4D8118EB.2070209@fastmail.fm \
    --to=aeriksson@fastmail.fm \
    --cc=airlied@redhat.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg-driver-ati@lists.x.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.