On Thursday 27 May 2004 22:45, Kenneth Aafl�y wrote: > On Thursday 27 May 2004 23:13, Andrew de Quincey wrote: > > On Thursday 27 May 2004 21:09, Kenneth Aafl�y wrote: > > I believe that card is supposed to have a similar idea - a cheapy CI > > interface, but that the implementation is different. > > > > As to how to proceed, you'll have to investigate what the windows driver > > is doing to communicate with the hardware on the CI interface, combined > > with working out the CI interface circuitry. > > > > The TT budget-ci is basically mostly done by the DEBI bus itself, but > > there is a custom GAL on there for handling the CAM detect and a few > > other things. > > Yeah, kinda thought they would be similar enough to get working fairly > easy. > > Anyways, found that the IRQ mask generated from the CAM/CI is MASK_06, not > MASK_03 (budget_ci_irq) which a little printk in there verified; w/cam it > prints those dots without it does not. > > I had to make a msp430_present flag, or the module would hang in > tasklet_kill(msp430), presumably because the tasklet has exited. > > A little while later... > It appears it's almost working :)
Aha, that would probably mean its wired the IRQ line (assuming it has one - it _could_ be polling mode only) to a different GPIO. I think you're getting too many IRQs for it to be working quite right judging by that syslog. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
