Am Sonntag, den 20.12.2009, 19:10 +0100 schrieb Luca Tettamanti:
> Typo, sorry: it's a M76 (the core is a RV630).
Interesting, I always thought that every R6xx based chipset has an audio
codec. Could you make sure that there is no audio codec on this chipset?
Take a look in the bios, its possible the codec is just disabled.

If there is really no audio codec could you make some register dumps?
Since we still have no documentation about the codec (and probably will
never really have, because it's an IP core and not original by ATI/AMD),
it would just be nice to see how some registers behave in the absence of
a codec.

> I see; still the driver could touch audio settings only when the audio
> device is actually open, no?
No, what we are really triggering on are buffer filled/depleted events, 
and those depends on the application sending or stopping audio, not the
alsa open/close events. And there are cases (the silence audio stream
option for example) where we send audio completely without alsa.

> > At the time of writing this patch the IRQ code wasn't available so I
> > just used the same workaround as the ddx, we should get rid of it as
> > soon as stable IRQ support is available.
> 
> Ok, cool :)
Alex Deucher has patches ready to clean this up, he is just waiting for
the IP review. If he isn't capable of releasing those before this code
went into mainline we should disable audio by default (by the way you
can do this by specifying audio=0 as an module option). 

Regards,
Christian.


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to