All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Dieter Nützel" <dieter@nuetzel-hh.de>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [TIP] Catalyst / fglrx and DVI to HDMI adapters (audio)
Date: Tue, 08 Oct 2013 10:29:54 +0200	[thread overview]
Message-ID: <5253C282.4020106@vodafone.de> (raw)
In-Reply-To: <66d90e371b079636a95d78132a5a6740@mail.ud03.udmedia.de>

Am 08.10.2013 00:14, schrieb Dieter Nützel:
> Am 07.10.2013 11:22, schrieb Christian König:
>> Am 07.10.2013 10:58, schrieb Rafał Miłecki:
>>> 2013/10/7 Christian König <deathsimple@vodafone.de>:
>>>> Why didn't you just asked me?
>>> I was told on #radeon you're on holidays ;) I was trying to catch you.
>>
>> I'm on vacation right now, but got back yesterday and now greping
>> though my accumulated mails ;)
>>
>>>
>>>> I've figured this out over five years ago by applying brute force 
>>>> to one of
>>>> the "magic" DVI->HDMI adapters that came with my original RV635. 
>>>> And it
>>>> indeed contains an extra EEPROM on the I2C bus ;)
>>> Did you find any way to workaround this? So I can use my generic
>>> adapter with fglrx for audio?
>>
>> Not that I know of any, well those adapters where only used on the
>> early RV6xx HDMI days. IIRC my later RV7xx worked well with the
>> 10meters DVI->HDMI cable fglrx on RV6xx failed.
>
> Hello to both of you!
>
> Christian, is there any change to get HDMI audio out of my 2 x 
> Dual-Link DVI RV730 AGP ports with one of those adapters (were can I 
> get one) or is the poor little one which came with the gfx card 
> (SAPPHIRE HD 4650 1GB DDR2 AGP) enough?
>

Hi Dieter,

for the open source driver you don't need any of those adapters. They 
are only used by fglrx to identify the "original" adapters that came 
with the board.

So the poor little one which came with the gfx card should be 
sufficient, but if you want to use fglrx + some other adapter you might 
run into problems.

Christian.

> Thanks,
>    Dieter
>
> PS Rafał, with the right solution I can maybe help you with your 
> investigation ;-)

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2013-10-08  9:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07  8:06 [TIP] Catalyst / fglrx and DVI to HDMI adapters (audio) Rafał Miłecki
2013-10-07  8:51 ` Christian König
2013-10-07  8:58   ` Rafał Miłecki
2013-10-07  9:22     ` Christian König
2013-10-07 22:14       ` Dieter Nützel
2013-10-08  8:29         ` Christian König [this message]
2013-10-09 22:40           ` Matt Sealey
2013-10-10  9:30             ` Christian König
2013-10-10 14:47               ` Matt Sealey

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=5253C282.4020106@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dieter@nuetzel-hh.de \
    --cc=dri-devel@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.