[alsa-devel] [RFC/RFT v2 0/4] ALSA: hda - hdmi: ATI/AMD multi-channel and HBR support

Anssi Hannula anssi.hannula at iki.fi
Fri Nov 8 23:13:14 CET 2013


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 at 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 at 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



More information about the Alsa-devel mailing list