Reply to thread

Message: <blockquote data-quote="RaStr" data-source="post: 11059">AVER T771 & DVICO drivers - probbably real final resultsHi all, I have finally patched the DVICO's drivers to fully match the programming of mt352 done by original drivers from Aver. While driver from DVICO seems to be pretty straight-forward and it's behavior reflects the suggested mt352 datasheets's steps, the work done by an original driver from Aver is a big mess with a lot of redundant I2C commands and operations, so analyzing it is a bit complicated. I have made my patched zulutune to send all most important config values to mt352, but it was unable to lock to a channel either. There are some commands missing compared to a steps performed by an Aver driver and originally I thought there are not critical. While my sniffing hardware currently doesn't  support sending I2C commands from the monitoring application I can't check my sequence step by step and I am not sure where is the problem, one possible reason could be some kind of missetup of general purpose pins of BT878A PCI chip on the card (there could be something like enable pin for a tin box, etc.), but I don't expect much this would be the case, another option is that the tuner is much slower then the tuner on DVICO's card, so the driver check it's status before it actually locks on the channel, I can't test this before I will get my sniffer fully operational, so I could send the read-status command manually and the last possibility is that some more config data must be sent to a mt352 before it can lock on the channel, I can check this with my saved Aver's driver session, but it would be extremely difficult to patch the DVICO driver further, so without the source code is almost impossible to make necessary changes in it anyhow. So as I have already stated, until we will get the driver sources, we can't do much about it. Maybe we can ask for a current Aver's driver sources, as this could be very helpful to me too !</blockquote>

Verification