Talk:NMT:DTS: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
I've tried comparing the firmware between 100 and 110 to see if I can find where it would enable me to select analog for DTS, but no luck thus far. | I've tried comparing the firmware between 100 and 110 to see if I can find where it would enable me to select analog for DTS, but no luck thus far. | ||
-- | |||
Line 13: | Line 13: | ||
I'm more interested in if the CSS_ucode could be loaded. | I'm more interested in if the CSS_ucode could be loaded. | ||
-- lundman |
Revision as of 00:03, 5 February 2009
I'm basically at the same spot you are. I've been able to get the 110 fw on the 100, but cannot use HDMI. I've switched to component, so everything basically works like normal.
I've tried comparing the firmware between 100 and 110 to see if I can find where it would enable me to select analog for DTS, but no luck thus far.
--
Yeah.. I'm reasonably sure it isn't anything in the binaries mono and gaya, they differ only by 4 bytes or something equally small. It is by far likely to be in libsample, or other libraries in /usr/lib/. However I did notice the kernel module em86xx.so is tried to the ucode and needs to match. More importantly, I've not been able to successfully unload it and load again. So most likely the ucodes and kernel modules need to be moved, then figure out what part of gaya detects if the option should be enabled.
But really we should ignore gaya, get the "mono" arguments it uses to play DTS->2ch, and work with that until it works. But there is a high chance those ucodes will just not work right with HDMI-1.1. I also doubt there will be a model with HDMI1.1 *and* DTS decoding.
Perhaps just buy a B-110, put it in the A-100 case :)
I'm more interested in if the CSS_ucode could be loaded.
-- lundman