From: Olivier Langlois <olivier@trillion01.com>
To: Anssi Hannula <anssi.hannula@iki.fi>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [RFC/RFT v2 0/4] ALSA: hda - hdmi: ATI/AMD multi-channel and HBR support
Date: Thu, 07 Nov 2013 16:20:22 -0500 [thread overview]
Message-ID: <1383859222.6455.28.camel@Wailaba2> (raw)
In-Reply-To: <52696FB4.1090704@iki.fi>
> >> o Contents of /proc/asound/cardX/eld#0.0
> >>
> >> Thanks a lot :)
> >>
> > monitor_present 1
> > eld_valid 1
> > monitor_name SC-09TX
> > connection_type HDMI
> [...]
>
> Looks OK, thanks for testing. Do you happen to have an EDID handy for
> the receiver, just to double-check the data matches? Not sure how it is
> available with fglrx driver, maybe in /var/log/Xorg.0.log...
> No need to go to extraordinary lengths to get it, though :)
>
Anssi,
Here is the EDID from Xorg.0.log:
[511268.796] (II) fglrx(0): EDID (in hex):
[511268.797] (II) fglrx(0): 00ffffffffffff00412f000001010101
[511268.797] (II) fglrx(0): 00110103806e3e782ad7b3ae51509423
[511268.797] (II) fglrx(0): 0c4a4721080081800101010101010101
[511268.797] (II) fglrx(0): 010101010101023a801871382d40582c
[511268.797] (II) fglrx(0): 45004e6c4200001e011d8018711c1620
[511268.797] (II) fglrx(0): 582c25004e6c4200009e000000fd0017
[511268.797] (II) fglrx(0): 3d0f450f000a202020202020000000fc
[511268.797] (II) fglrx(0): 0053432d303954580a202020202001c4
I'm seeing the monitor_name ok. Unfortunately, it doesn't dump the
extension that byte 126 indicates to be present. (the CEA EDID Timing
Extension with the SADs ?) to validate the rest of the content
of /proc/asound/cardX/eld#0.0.
Is there any other way to get the EDID data?
next prev parent reply other threads:[~2013-11-07 21:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:30 [RFC/RFT v2 0/4] ALSA: hda - hdmi: ATI/AMD multi-channel and HBR support Anssi Hannula
2013-10-01 20:30 ` [PATCH 1/4] ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support Anssi Hannula
2013-10-30 15:35 ` Rafał Miłecki
2013-10-30 15:59 ` Anssi Hannula
2013-10-31 16:22 ` Rafał Miłecki
2013-10-31 20:26 ` Anssi Hannula
2013-10-31 23:25 ` Rafał Miłecki
2013-10-31 23:34 ` Anssi Hannula
2013-10-31 23:51 ` Rafał Miłecki
2013-10-31 23:58 ` Anssi Hannula
2013-11-01 11:29 ` Rafał Miłecki
2013-11-01 12:15 ` Anssi Hannula
2013-11-01 13:22 ` Rafał Miłecki
2013-11-01 13:43 ` Rafał Miłecki
2013-10-01 20:30 ` [PATCH 2/4] ALSA: hda - hdmi: Add ELD emulation for ATI/AMD codecs Anssi Hannula
2013-10-01 20:30 ` [PATCH 3/4] ALSA: hda - hdmi: Add HBR bitstreaming support for ATI/AMD HDMI codecs Anssi Hannula
2013-10-01 20:30 ` [PATCH 4/4] ALSA: hda - hdmi: Disable ramp-up/down for non-PCM on AMD codecs Anssi Hannula
2013-10-02 14:34 ` [RFC/RFT v2 0/4] ALSA: hda - hdmi: ATI/AMD multi-channel and HBR support Takashi Iwai
2013-10-02 16:42 ` Anssi Hannula
2013-10-07 7:33 ` Takashi Iwai
2013-10-04 7:06 ` Olivier Langlois
2013-10-04 23:39 ` Anssi Hannula
2013-10-06 3:48 ` Olivier Langlois
2013-10-06 12:07 ` [alsa-devel] " Anssi Hannula
2013-10-09 4:32 ` Olivier Langlois
2013-10-24 19:06 ` Anssi Hannula
2013-11-07 21:20 ` Olivier Langlois [this message]
2013-11-08 10:18 ` Anssi Hannula
2013-11-08 16:44 ` Olivier Langlois
2013-11-08 22:13 ` Anssi Hannula
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=1383859222.6455.28.camel@Wailaba2 \
--to=olivier@trillion01.com \
--cc=alsa-devel@alsa-project.org \
--cc=anssi.hannula@iki.fi \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).