That's what I am thinking. It looks like those registers are
trying to be read before the card has locked onto the signal. I
only get these errors if I tune to channel that doesn't have a digital
signal. I wonder if the tuner in the HDTV Wonder is able to lock
on faster than the one in the A180. Since you get these errors
when there is not a signal, and it doesn't mean anything is wrong, we
should probably ignore it.<br>
<br>
After looking over the nxt2002_readreg_multibyte code again it looks
like it never even checks for errors. We might just want to do
the same and remove<br>
<br>
In nxt200x_readreg_multibyte change it from:<br>
<br>
case NXT2004:<br>
/* probably not right, but gives correct values */<br>
attr = 0x02;<br>
if (reg & 0x80) {<br>
attr = attr << 1;<br>
if (reg & 0x04)<br>
attr = attr >> 1;<br>
}<br>
<br>
/* set multi register length */<br>
len2 = (attr << 4) | len;<br>
nxt200x_writebytes(state, 0x34, &len2, 1);<br>
<br>
/* toggle the multireg bit*/<br>
buf = 0x80;<br>
nxt200x_writebytes(state, 0x21, &buf, 1);<br>
<br>
/* read status */<br>
nxt200x_readbytes(state, 0x21, &buf, 1);<br>
<br>
if (buf == 0)<br>
{<br>
/* read the actual data */<br>
for(i = 0; i < len; i++) {<br>
nxt200x_readbytes(state, 0x36 + i, &data[i], 1);<br>
}<br>
return 0;<br>
}<br>
break;<br>
default:<br>
return -EINVAL;<br>
break;<br>
}<br>
<br>
printk(KERN_WARNING "nxt200x: Error reading multireg register 0x%02X BUFFER=0x%02X\n",reg,buf);<br>
<br>
return 0;<br>
<br>
To:<br>
<br>
case NXT2004:<br>
/* probably not right, but gives correct values */<br>
attr = 0x02;<br>
if (reg & 0x80) {<br>
attr = attr << 1;<br>
if (reg & 0x04)<br>
attr = attr >> 1;<br>
}<br>
<br>
/* set multi register length */<br>
len2 = (attr << 4) | len;<br>
nxt200x_writebytes(state, 0x34, &len2, 1);<br>
<br>
/* toggle the multireg bit*/<br>
buf = 0x80;<br>
nxt200x_writebytes(state, 0x21, &buf, 1);<br>
<br>
/* read the actual data */<br>
for(i = 0; i < len; i++) {<br>
nxt200x_readbytes(state, 0x36 + i, &data[i], 1);<br>
}<br>
return 0;<br>
break;<br>
default:<br>
return -EINVAL;<br>
break;<br>
}<br>
<br>
<br>
Kirk<br><br><div><span class="gmail_quote">On 10/27/05, <b class="gmail_sendername">Michael Krufky</b> <<a href="mailto:mkrufky@m1k.net">mkrufky@m1k.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Kirk Lapray wrote:<br><br>> On 10/27/05, *Michael Krufky* <<a href="mailto:mkrufky@m1k.net">mkrufky@m1k.net</a><br>> <mailto:<a href="mailto:mkrufky@m1k.net">mkrufky@m1k.net</a>>> wrote:<br>><br>> Although everything is working well, I am still getting these errors
<br>> when I first run azap:<br>><br>> nxt200x: NXT2004 Detected<br>> DVB: registering new adapter (saa7133[0]).<br>> DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM frontend)...<br>> nxt2004: Waiting for firmware upload (
dvb-fe-nxt2004.fw)...<br>> nxt2004: Waiting for firmware upload(2)...<br>> nxt2004: Firmware upload complete<br>> nxt200x: Error reading multireg register 0xA6<br>> nxt200x: Error reading multireg register 0xE6
<br>> nxt200x: Error reading multireg register 0xE6<br>><br>> Never more than 3 lines in the log... It is tuning and delivering<br>> my ts<br>> stream just fine.<br>><br>> I know the nxt2002 driver used dprintk instead of printk in the
<br>> multireg read and write commands. We could switch it to dprintk and<br>> then you would only see these errors if you loaded the driver with<br>> debug set.<br><br>Kirk -<br><br>So... I guess that translates to "those errors don't matter." Would
<br>that be the correct assessment?<br><br>I'm not worried about whether I am *seeing* them or not... I was only<br>concerned about whether it was indicating something worth paying<br>attention to.<br><br>-Mike<br><br></blockquote>
</div><br>