linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CityK <cityk@rogers.com>
To: Bob Cunningham <FlyMyPG@gmail.com>, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick
Date: Tue, 25 Nov 2008 20:36:22 -0500	[thread overview]
Message-ID: <492CA816.7000400@rogers.com> (raw)
In-Reply-To: <492B9B98.5060603@gmail.com>

Bob Cunningham wrote:
> CityK wrote:
>> Bob Cunningham wrote:
>>> There are 3 chips, from the USB to the cable connector they are:
>>> AU0828A
>>> AU8522AA
>>> MT2131F
>>>
>>
>> What tuner is being listed in your dmesg output ?
>
> Here's everything from dmesg:
>
>    usb 1-2: new high speed USB device using ehci_hcd and address 22
>    usb 1-2: configuration #1 chosen from 1 choice
>    au0828: i2c bus registered
>    tveeprom 4-0050: Encountered bad packet header [ff]. Corrupt or not
> a Hauppauge eeprom.
>    hauppauge_eeprom: warning: unknown hauppauge model #0
>    hauppauge_eeprom: hauppauge eeprom: model=0
>    tda18271 4-0060: creating new instance
>    Unknown device detected @ 4-0060, device not supported.
>    Unknown device detected @ 4-0060, device not supported.
>    tda18271_attach: error -22 on line 1171
>    tda18271 4-0060: destroying instance
>    DVB: registering new adapter (au0828)
>    DVB: registering adapter 0 frontend 1 (Auvitek AU8522 QAM/8VSB
> Frontend)...
>    Registered device AU0828 [Hauppauge Woodbury]
>    usb 1-2: New USB device found, idVendor=05e1, idProduct=0400
>    usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>    usb 1-2: Product: USB 2.0 Video Capture Controller
>    usb 1-2: Manufacturer: Syntek Semiconductor
>

Please use 'reply all', so you don't drop the list -- I have cc'ed your
reply back in (snipping out the unnecessary stuff)

As can be seen, there is:
a) a problem with reading from the EEPROM
b) the device is initially setting up  with a NXP tda18271 tuner ...
which obviously is not the same as the  MT2131 in your device ...
understandably, the tuner driver craps out.

I suspect that when you were attempting to tune, all you were doing was
polling from the last state the tuner was left in (whatever the tda
driver's attempt to initialize it was before it crapped out)... and, as
there is no driver operating further, there is no fine control over the
tuner ... hence, the scan utility could instruct the frontend to check a
certain frequency, but all you're getting back is crap from the tuner  
....   sort of like an analog radio that's in between stations and
emitting static -- unless you directly manipulate/have control over the
tuning knob,  standing 10 feet away and verbally instructing the radio
to tune this or that frequency is going to produce the same thing being
emitted all along -- static.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2008-11-26  1:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 21:46 [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick Bob Cunningham
2008-11-23 16:35 ` Bob Cunningham
2008-11-23 19:21 ` Michael Krufky
2008-11-23 19:40   ` CityK
2008-11-23 19:48     ` CityK
2008-11-24  1:08     ` Bob Cunningham
2008-11-24  1:33       ` Bob Cunningham
2008-11-24  2:34         ` Bob Cunningham
2008-11-24  3:05           ` Bob Cunningham
2008-11-24  4:50       ` CityK
     [not found]         ` <492B9B98.5060603@gmail.com>
2008-11-26  1:36           ` CityK [this message]
2008-11-26  7:18             ` Bob Cunningham
2008-11-27 16:11               ` CityK
2008-11-27 19:28                 ` Michael Krufky
2008-12-19  6:43                   ` Bob Cunningham
2009-03-04 17:24                     ` Bob Cunningham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=492CA816.7000400@rogers.com \
    --to=cityk@rogers.com \
    --cc=FlyMyPG@gmail.com \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).