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
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 c
