Terve Hans, On 03/14/2012 05:53 PM, Hans van den Bogert wrote:
The anysee driver works correctly from cold boot and reinsertion of the device, however, after a suspend resume cycle (S3), the device suddenly is initated as dvb-t as where it was dvb-c before. Yes this is a combo device, so dvb T and C, but why does the profiling in anysee.c not handle this case? Obviously the following snippet produces a false positive on warm boot and resume:
This is known problem. Actually it is coming from wrong GPIOs / demodulator selection logic. I just guessed those in the time driver was made. Now I have also correct info. Unfortunately I don't even have this device currently... IIRC you can blacklist zl10353 driver as workaround.
regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
