From: Jasper Smet <josbeir@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Alsa-user] intel-hda: sound via HDMI only when using interlaced modes
Date: Wed, 9 Oct 2013 13:28:05 +0200 [thread overview]
Message-ID: <CAGpEb3Gi4-0Jper3Xs8VZ+ZbmabrjJDxoBwcqGNqA5PevPWDpw@mail.gmail.com> (raw)
In-Reply-To: <20131009110108.GP8303@phenom.ffwll.local>
Ok will pass the info when i get home later this day.
On Wed, Oct 9, 2013 at 1:01 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Oct 09, 2013 at 12:44:10PM +0200, Jasper Smet wrote:
>> Sorry,
>>
>> Intel NUC NUC Kit DC3217BY (Ivy bridge HD4000) Connected via HDMI to
>> my Pioneer VSX-928 which is then connected to my Panasonic tv
>>
>> Running latest stable Openelec build (3.2.2). (tried different builds
>> using stable/unstable drivers)
>
> That's really old ... Can you please test on something more modern? We
> made tons of fixes to the hdmi infoframe code.
>>
>> Here are some logs i pulled while i was debugging the issue with one
>> of the OpenElec developers.
>>
>> xbmc log (shows ALSA enumeration): http://sprunge.us/YJHc
>> alsa playback devices: http://sprunge.us/KZKX
>> xrandr modes: http://sprunge.us/DhFK
>> dmesg: http://sprunge.us/XRGP
>
> When you have a new kernel please boot with drm.debug=0xe added to your
> kernel cmdline and then grab the dmesg. Otherwise all the useful gfx debug
> noise isn't in there.
> -Daniel
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Met Vriendelijke Groeten
Jasper Smet
Developer
Twitter: josbeir
E-mail: josbeir@gmail.com
Mobile: 0486/41.75.45
next prev parent reply other threads:[~2013-10-09 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 9:09 [Alsa-user] intel-hda: sound via HDMI only when using interlaced modes Jasper Smet
2013-10-09 10:34 ` Daniel Vetter
2013-10-09 10:44 ` Jasper Smet
2013-10-09 11:01 ` Daniel Vetter
2013-10-09 11:28 ` Jasper Smet [this message]
2013-10-09 18:27 ` Jasper Smet
2013-10-10 5:57 ` Jani Nikula
2013-10-10 6:59 ` Jasper Smet
2013-10-10 8:08 ` Jani Nikula
2013-10-10 8:27 ` Jani Nikula
2013-10-10 8:36 ` Jasper Smet
2013-10-10 8:38 ` Jani Nikula
2013-10-10 8:53 ` Jasper Smet
2013-10-11 6:25 ` Jasper Smet
2013-10-11 7:06 ` Jani Nikula
2013-10-12 11:51 ` Jasper Smet
[not found] <20130129221826.GA11723@hardeman.nu>
2013-02-06 21:35 ` David Härdeman
2013-02-07 10:00 ` [Alsa-user] " Daniel Vetter
2013-02-10 1:16 ` David Härdeman
2013-02-11 11:09 ` Takashi Iwai
2013-02-18 23:44 ` David Härdeman
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=CAGpEb3Gi4-0Jper3Xs8VZ+ZbmabrjJDxoBwcqGNqA5PevPWDpw@mail.gmail.com \
--to=josbeir@gmail.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@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 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.