Am Donnerstag, den 01.10.2009, 22:11 +0200 schrieb Rafał Miłecki: > OK, I've compared radeonhd and KMS with that registers. Logs attached > (radeonhd.playing.dump.log, kms.playing.broken.dump.log). > > I've diffed them and used wrote radeonhd's values (potential.fix.sh). > > After executing potential.fix.sh nothing changed: no sound, no > corruptions, playback speed correct. > > Then I dumped registers once more (kms.hacked.log). > > Comparing radeonhd.playing.dump.log with kms.hacked.log showed > registers that didn't /accept/ new values. > > Tried overwriting again but didn't success on that (failed.changes.log). That's ok, the register values you could overwrite are read only status registers, with the exception of the 0x7408 register, but this really doesn't matter much.
But there is something else which is very interesting: 0x74C4: 0x00000000 That's the last transmitted CTS value which is used for clock recovery in your AV receiver. The setup which values should be transmitted for the different sampling rates is correct (register 0x74AC, 0x74B4, 0x74BC), but this register is still 0 could only mean one thing: we never transmitted a single value. Check the registers 0x75A0 and 0x79A0 (RV620_DIG[12]_CNTL), i suspect that the transmitter isn't running in HDMI mode, maybe because of failed auto detection, but i am not 100% sure. Bye, Christian. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
