alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@iki.fi>
To: Olivier Langlois <olivier@trillion01.com>
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: Sat, 09 Nov 2013 00:13:14 +0200	[thread overview]
Message-ID: <527D61FA.7010903@iki.fi> (raw)
In-Reply-To: <1383929090.6455.44.camel@Wailaba2>

08.11.2013 18:44, Olivier Langlois kirjoitti:
> 
>>>> 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?
>>
>> With direct VBE BIOS calls, e.g. with this:
>> http://gitweb.mageia.org/software/monitor-edid/
>>
>> monitor-get-edid -v --try-in-console --max-vbe-port 6 > edid.bin
>> (or --vbe-port X if multiple monitors)
>>
>> or directly with the C tool (X=0..6):
>> monitor-get-edid-using-vbe -v --try-in-console --port X > edid.bin
>>
>> However, I don't know if fglrx interferes with it (I know nvidia
>> proprietary driver doesn't/didn't).
>>
> No luck. This gives me the same info:
> 
> lano1106@whippet2 ~/dev/monitor-edid :( $
> sudo ./monitor-get-edid-using-vbe -v --try-in-console > edid.bin
> [sudo] password for lano1106: 
> VBE version: 3.0, oem version = 15.25
> Memory: 16384k
> OEM name: 
> Vendor name: 
> Product name: 
> Product revision: 
> Port 0:
>   DDC1 not supported
>   DDC2 supported
>   Screen not blanked during data transfer
>   Time to transfer one EDID block: 1 sec (rounded up)
> EDID: Extension block 1 is identical to main EDID block, stopping
> retrieval
> lano1106@whippet2 ~/dev/monitor-edid $ hexdump edid.bin 
> 0000000 ff00 ffff ffff 00ff 2f41 0000 0101 0101
> 0000010 1100 0301 6e80 783e d72a aeb3 5051 2394
> 0000020 4a0c 2147 0008 8081 0101 0101 0101 0101
> 0000030 0101 0101 0101 3a02 1880 3871 402d 2c58
> 0000040 0045 6c4e 0042 1e00 1d01 1880 1c71 2016
> 0000050 2c58 0025 6c4e 0042 9e00 0000 fd00 1700
> 0000060 0f3d 0f45 0a00 2020 2020 2020 0000 fc00
> 0000070 5300 2d43 3930 5854 200a 2020 2020 c401
> 0000080
> 
> My receiver is maybe too old for CEA ext v3 with SADs. I bought it in
> 2008 and maybe it has been manufactured in 2007. It is a Pioneer.

It clearly does have them, since the eld#x contents you provided earlier
contained information from SADs.

Anyway, the information looked correct, so I think we can leave this be :)

-- 
Anssi Hannula

      reply	other threads:[~2013-11-08 22:13 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
2013-11-08 10:18               ` Anssi Hannula
2013-11-08 16:44                 ` Olivier Langlois
2013-11-08 22:13                   ` Anssi Hannula [this message]

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=527D61FA.7010903@iki.fi \
    --to=anssi.hannula@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=olivier@trillion01.com \
    --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).