Reply to thread

Message

<blockquote data-quote="RaStr" data-source="post: 10914">Aver with DVICOSo, here is the conclusion, I have compared the data from Aver driver and modded DVICO: the main reason, why it still cannot tune and find anything seems to be in different PCB setup of DVICO's card, i.e. some interfacing of PLL chip used is different. Actually the config word for a PLL has to be modified in DVICO's driver too, one change in a first byte of this word is probbably a constant, which can be&nbsp; probbably tracked in the code, but the second part of this word could be a variable (the exact value depends on the frequency band of a channel selected) a could be calculated somewhere in the code. This one will be extremely hard to find and modify in the binary code ! So I give-up, because without a source code of a driver it is pretty hard to modify the driver for actuall hw setup and Aver is using for A771 such a crap hw, which noone else uses, so modifying some other driver is impossible too!</blockquote>

[QUOTE="RaStr, post: 10914"] [b]Aver with DVICO[/b] So, here is the conclusion, I have compared the data from Aver driver and modded DVICO: the main reason, why it still cannot tune and find anything seems to be in different PCB setup of DVICO's card, i.e. some interfacing of PLL chip used is different. Actually the config word for a PLL has to be modified in DVICO's driver too, one change in a first byte of this word is probbably a constant, which can be probbably tracked in the code, but the second part of this word could be a variable (the exact value depends on the frequency band of a channel selected) a could be calculated somewhere in the code. This one will be extremely hard to find and modify in the binary code ! So I give-up, because without a source code of a driver it is pretty hard to modify the driver for actuall hw setup and Aver is using for A771 such a crap hw, which noone else uses, so modifying some other driver is impossible too! [/QUOTE]

Verification