I have read documents that say it uses a NXT2002, NXT2003, and
NXT2004. Most of the notable sources say it uses a NXT2004
(<a href="http://www.ati.com/companyinfo/press/2004/4732.html">http://www.ati.com/companyinfo/press/2004/4732.html</a>).<br>
<br>
I have the driver I have been working on sending the exact same i2c
data as the Windows driver. Everything is identical until it
check for a signal lock. The Windows driver returns a 0x20 on the
i2c bus indicating a signal lock, but all I get is 0x00 under
Linux. There must be something else I am missing.<br>
<br>
Kirk<br>
<br><br><div><span class="gmail_quote">On 10/13/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>> This is true, but on the HDTV Wonder the NXT2004 and Philips tuner are<br>> integrated into one package. The NXT2004 is actually in the tuner metal<br>> box. This module is called the Philips TUV1236D. It also uses the CX88
<br>> interface chip. So, besides the NXT2004 there is nothing similar<br>> between the cards. I still have not been able to get the NXT2004<br>> working correctly on the HDTV Wonder. I started off using the NXT2004
<br>> DVB driver that was posted to the DVB mailing list a few months back<br>> written for the AverTVHD, but the HDTV Wonder is a completely different<br>> setup. I have been able to write a driver that from what I can tell
<br>> completely mimics the Windows driver and I have gotten the firmware<br>> loaded and the tuner changes channels, but for some reason the NXT2004<br>> never reports a signal lock. There must just be something I am
<br>> missing. Once I figure out what I am doing wrong it shouldn't take much<br>> to get it to work on other NXT2004 based cards as long as the tuner and<br>> interface chips are supported.<br><br>Kirk-<br><br>
I didnt see that "[linux-dvb] AverTVHD/NXT2004 patches" thread when it<br>was first posted. Thank you for pointing it out. I cc'd this email to<br>the list, maybe Patrick or Jean-Francois can say something about the
<br>status of the nxt200x module?<br><br>I haven't yet tried Jean-Francois 's patch.... I think I'll give it a<br>whirl later on.<br><br>About the Philips TUV1236D, Google found this excel sheet that shows<br>that it uses NXT2003. Is the sheet wrong? ...or maybe some registers
<br>might be different? (just a guess)<br><br><a href="http://hdtv.forsandiego.com/messages/1/ATSC_NTSC_Tuner_Specs-3646.xls">http://hdtv.forsandiego.com/messages/1/ATSC_NTSC_Tuner_Specs-3646.xls</a><br><br>AVerTVHD also has the NXT2004 inside the the same package with the
<br>tuner. It is a TDHU2-008A. I found some specs for this at:<br><br><a href="http://www3.alps.co.jp/alpscom/pdf/index_broadcasting-e.html">http://www3.alps.co.jp/alpscom/pdf/index_broadcasting-e.html</a><br><br>Regards,
<br><br>Michael Krufky<br></blockquote></div><br>