<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jo Heremans wrote:
<blockquote cite="mid:1219576046.11317.2.camel@pvr" type="cite">
<pre wrap="">On Sat, 2008-08-23 at 21:15 +0100, Roger James wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I asked a similar question this a little whiile ago and got no answer.
So I am trying again with a bit more detail and hoping someone somewhere
can tell me whether I am wasting my time. I need to find out whether the
CI daughter board is broken or this combination has never worked in the
budget-ci driver.

The TT-3200 works fine for DVB scan and capture, but I cannot get the CI
to initialise fully. It always times out on the initial reset and gives
a "PC card did not respond" message in the kernel log.

I peppered the driver with extra diagnostics and as far as I can see the
initial CI reset process is started. The firmware version is reported as
0xa0 (is this correct?) so an interrupt is expected from the card. This
interrupt never occurs. If I poll the card status
(ciintf_poll_slot_status) when the reset times out then flags come back
as 9 (CAMDETECT|RESET) but it looks like the read_attribute_mem does not
give the correct value and returns 0x00 which I assume means that the
CAM has not initialised. I have appended the dmesg output to the end of
this message.

If anyone has got this working can you please let me know, so I can swap
the CI daughter board for a working one and stop wasting my time debugging.

</pre>
</blockquote>
Jo,<br>
<br>
It looks like the driver is OK but I have an issue either with the
T.Rex/Dragon CAM when it used in this CI, or the CI interface on my
TT-3200, or the CI daughter board. What kind of CAM are you using? Has
anyone got a T.Rex/Dragon CAM working with the budget PCI driver.<br>
<br>
Thanks,<br>
<br>
Roger<br>
</body>
</html>