Progess has slowed down a bit. I happen to have a 2.4.7-10 machine which the Twinhan driver wants, and can run their app. Unfortunately I can't lock the signal.
Can anyone confirm that the cidst from twinhan software actually works for them? The I2C comms is just too unreliable. I can't workout where the problem might be. Too slow? some bit timing problem? One way around it is to implement the i2c transfer the same as saa7146_i2c.c does, rather than bit-banging using algo-bit. The fusion has quite good i2c xfer so this is worthwhile anyway. For audio dma, this card is using 8 bit parallel 'async data parallel port'. I'm not sure why the FDSR errors have to be masked out on sync instructions. Also I get lots of FBUS and other errors ... Maybe they're a feature of this type of transfer. Anyway, there's newer code up on http://members/optushome.com.au/jhonan/dst together with more uptodate information. Of course it doesn't work and won't for a while yet. This card is annoying. I can't see a way to get BER, SNR etc, only lock/no lock. Does the windows version provide this info? Jamie -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
