On Mon, Jun 29, 2009 at 9:43 AM, Steven Toth<stoth@xxxxxxxxxxxxxx> wrote: >>> cx23885_dev_checkrevision() New hardware revision found 0x0 >>> cx23885_dev_checkrevision() Hardware revision unknown 0x0 >>> cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 17, latency: 0, >>> mmio: 0xfd800000 >>> cx23885 0000:02:00.0: setting latency timer to 64 >>> >>> I'm pretty sure that is the problem but I don't know how to fix it. I > > The new revision isn't the problem, the above code is for information > purposes so we can track new revs of the silicon in this mailing list. Most > likely the demodulators / tuners are not configured correctly. DViCO > probably changed something. > > Double check that the silicon and gpios / settings inside the cx23885 driver > for the existing card definition match the silicon and configuration for > this new card you have. > It's not a new revision. Something else is wrong. I have both revisions of this board, and they display the same revision information as Hauppauge cx23885-based products: mk@codes:~$ dmesg | grep checkrevision [ 136.689267] cx23885_dev_checkrevision() Hardware revision = 0xb0 [ 136.914968] cx23885_dev_checkrevision() Hardware revision = 0xb0 [ 137.086548] cx23885_dev_checkrevision() Hardware revision = 0xb0 If it was a PCI card I would suggest moving it to another PCI slot, but I'm not sure that would help at all in the case of PCIe. DViCO has not updated their Windows driver since April of last year. I think that Michael Kutyna should confirm that the device works in windows before anybody proceeds to troubleshoot this any further -- it might just be a bad board / platform. -Mike Krufky -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
