* [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick
@ 2008-11-22 21:46 Bob Cunningham
2008-11-23 16:35 ` Bob Cunningham
2008-11-23 19:21 ` Michael Krufky
0 siblings, 2 replies; 16+ messages in thread
From: Bob Cunningham @ 2008-11-22 21:46 UTC (permalink / raw)
To: linux-dvb
Hi,
I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following:
Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd
A quick search revealed that the au0828 driver had recently been updated (10 Nov) to support this USB ID.
Following instructions on the wiki, I obtained the latest v4l-dvb source via Mercurial, and built/installed it without error. Next I did "modprobe au0828", and dmesg provided the following:
au0828 driver loaded
usbcore: registered new interface driver au0828
Next I did "lsmod | grep au0828", which provides the following:
au0828 20384 0
dvb_core 68673 1 au0828
tveeprom 14917 1 au0828
i2c_core 20949 4 au0828,tveeprom,nvidia,i2c_i801
dmesg provides the following when the device is plugged in:
usb 1-2: new high speed USB device using ehci_hcd and address 10
usb 1-2: configuration #1 chosen from 1 choice
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
However, I have no /dev/dvb. I unplugged/replugged several times, with no change.
I rebooted and repeated the modprobe and the unplug/replug, with no different results.
My guess is that udev isn't making the connection from the USB ID, but I'm not sure what to do about it.
I'm running a fully updated FC8 on a Dell dual Xeon-HT server with kernel 2.6.26.6-49.fc8 #1 SMP.
Did I miss something basic?
Thanks,
-BobC
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 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 1 sibling, 0 replies; 16+ messages in thread From: Bob Cunningham @ 2008-11-23 16:35 UTC (permalink / raw) To: linux-dvb I previously wrote: > Hi, > > I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: > > Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd > > A quick search revealed that the au0828 driver had recently been updated (10 Nov) to support this USB ID. > > Following instructions on the wiki, I obtained the latest v4l-dvb source via Mercurial, and built/installed it without error. Next I did "modprobe au0828", and dmesg provided the following: > > au0828 driver loaded > usbcore: registered new interface driver au0828 > > Next I did "lsmod | grep au0828", which provides the following: > > au0828 20384 0 > dvb_core 68673 1 au0828 > tveeprom 14917 1 au0828 > i2c_core 20949 4 au0828,tveeprom,nvidia,i2c_i801 > > dmesg provides the following when the device is plugged in: > > usb 1-2: new high speed USB device using ehci_hcd and address 10 > usb 1-2: configuration #1 chosen from 1 choice > 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 > > However, I have no /dev/dvb. I unplugged/replugged several times, with no change. > > I rebooted and repeated the modprobe and the unplug/replug, with no different results. > > My guess is that udev isn't making the connection from the USB ID, but I'm not sure what to do about it. > > I'm running a fully updated FC8 on a Dell dual Xeon-HT server with kernel 2.6.26.6-49.fc8 #1 SMP. > > Did I miss something basic? > > > Thanks, > > -BobC Hi again, To see what's happening in the udev domain, I added the following rule to hopefully let the system know that I'm trying to plug in a v4l device: /etc/udev/rules.d/25-name-video-devices.rules: SUBSYSTEM=="video4linux", BUS=="usb", SYSFS{idVendor}=="05e1", SYSFS{idProduct}=="0400", NAME="video0" At the end of this note is the output of "udevmonitor --environment" that is generated when the tuner stick is plugged in. Sorry for the length, but I'm not sure what's important. Though I don't know what should be happening for this device, it seems I'm adding lots of endpoints, but the only devices identified are for sound. No video. How do I get the au0828 driver to accept this device? Thanks, -BobC Output of "udevmonitor --environment": udevmonitor will print the received events for: UDEV the event which udev sends out after rule processing UEVENT the kernel uevent UEVENT[1227456137.360734] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2 (usb) ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2 SUBSYSTEM=usb MAJOR=189 MINOR=11 DEVTYPE=usb_device PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 BUSNUM=001 DEVNUM=012 SEQNUM=1605 UEVENT[1227456137.361600] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 (usb) ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=255/255/255 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00icFFiscFFipFF SEQNUM=1606 UEVENT[1227456137.361624] add /class/usb_endpoint/usbdev1.12_ep81 (usb_endpoint) ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep81 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=8 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 PHYSDEVBUS=usb SEQNUM=1607 UEVENT[1227456137.362218] add /class/usb_endpoint/usbdev1.12_ep82 (usb_endpoint) ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep82 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=9 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 PHYSDEVBUS=usb SEQNUM=1608 UEVENT[1227456137.362238] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 (usb) ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=1/1/0 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00ic01isc01ip00 SEQNUM=1609 UEVENT[1227456137.363306] add /class/sound/pcmC1D0c (sound) ACTION=add DEVPATH=/class/sound/pcmC1D0c SUBSYSTEM=sound MAJOR=116 MINOR=10 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1610 UEVENT[1227456137.363324] add /class/sound/dsp1 (sound) ACTION=add DEVPATH=/class/sound/dsp1 SUBSYSTEM=sound MAJOR=14 MINOR=19 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1611 UEVENT[1227456137.363878] add /class/sound/audio1 (sound) ACTION=add DEVPATH=/class/sound/audio1 SUBSYSTEM=sound MAJOR=14 MINOR=20 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1612 UEVENT[1227456137.363898] add /class/sound/controlC1 (sound) ACTION=add DEVPATH=/class/sound/controlC1 SUBSYSTEM=sound MAJOR=116 MINOR=11 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1613 UEVENT[1227456137.364445] add /class/sound/mixer1 (sound) ACTION=add DEVPATH=/class/sound/mixer1 SUBSYSTEM=sound MAJOR=14 MINOR=16 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1614 UEVENT[1227456137.364864] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 (usb) ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 SUBSYSTEM=usb DEVTYPE=usb_interface DRIVER=snd-usb-audio PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=1/2/0 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00ic01isc02ip00 SEQNUM=1615 UEVENT[1227456137.365333] add /class/usb_endpoint/usbdev1.12_ep84 (usb_endpoint) ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep84 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=10 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1616 UEVENT[1227456137.365632] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 (usb) ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=255/255/255 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00icFFiscFFipFF SEQNUM=1617 UEVENT[1227456137.365916] add /class/usb_endpoint/usbdev1.12_ep83 (usb_endpoint) ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep83 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=11 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 PHYSDEVBUS=usb SEQNUM=1618 UEVENT[1227456137.366631] add /class/usb_endpoint/usbdev1.12_ep00 (usb_endpoint) ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep00 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=12 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2 PHYSDEVBUS=usb PHYSDEVDRIVER=usb SEQNUM=1619 UDEV [1227456137.378540] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2 (usb) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2 SUBSYSTEM=usb MAJOR=189 MINOR=11 DEVTYPE=usb_device PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 BUSNUM=001 DEVNUM=012 SEQNUM=1605 UDEVD_EVENT=1 DEVNAME=/dev/bus/usb/001/012 UDEV [1227456137.423287] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 (usb) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 SUBSYSTEM=usb DEVTYPE=usb_interface DRIVER=snd-usb-audio PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=1/2/0 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00ic01isc02ip00 SEQNUM=1615 UDEVD_EVENT=1 UDEV [1227456137.442648] add /class/usb_endpoint/usbdev1.12_ep84 (usb_endpoint) UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep84 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=10 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.2 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1616 UDEVD_EVENT=1 DEVNAME=/dev/usbdev1.12_ep84 UDEV [1227456137.450632] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 (usb) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=1/1/0 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00ic01isc01ip00 SEQNUM=1609 UDEVD_EVENT=1 UDEV [1227456137.462968] add /class/sound/mixer1 (sound) UDEV_LOG=3 ACTION=add DEVPATH=/class/sound/mixer1 SUBSYSTEM=sound MAJOR=14 MINOR=16 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1614 UDEVD_EVENT=1 DEVNAME=/dev/mixer1 UDEV [1227456137.464124] add /class/sound/audio1 (sound) UDEV_LOG=3 ACTION=add DEVPATH=/class/sound/audio1 SUBSYSTEM=sound MAJOR=14 MINOR=20 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1612 UDEVD_EVENT=1 DEVNAME=/dev/audio1 UDEV [1227456137.480950] add /class/sound/pcmC1D0c (sound) UDEV_LOG=3 ACTION=add DEVPATH=/class/sound/pcmC1D0c SUBSYSTEM=sound MAJOR=116 MINOR=10 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1610 UDEVD_EVENT=1 DEVNAME=/dev/snd/pcmC1D0c UDEV [1227456137.484585] add /class/sound/controlC1 (sound) UDEV_LOG=3 ACTION=add DEVPATH=/class/sound/controlC1 SUBSYSTEM=sound MAJOR=116 MINOR=11 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1613 UDEVD_EVENT=1 DEVNAME=/dev/snd/controlC1 UDEV [1227456137.489291] add /class/sound/dsp1 (sound) UDEV_LOG=3 ACTION=add DEVPATH=/class/sound/dsp1 SUBSYSTEM=sound MAJOR=14 MINOR=19 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.1 PHYSDEVBUS=usb PHYSDEVDRIVER=snd-usb-audio SEQNUM=1611 UDEVD_EVENT=1 DEVNAME=/dev/dsp1 UDEV [1227456137.491488] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 (usb) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=255/255/255 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00icFFiscFFipFF SEQNUM=1606 UDEVD_EVENT=1 UDEV [1227456137.510251] add /class/usb_endpoint/usbdev1.12_ep82 (usb_endpoint) UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep82 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=9 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 PHYSDEVBUS=usb SEQNUM=1608 UDEVD_EVENT=1 DEVNAME=/dev/usbdev1.12_ep82 UDEV [1227456137.534106] add /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 (usb) UDEV_LOG=3 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 SUBSYSTEM=usb DEVTYPE=usb_interface PHYSDEVBUS=usb DEVICE=/proc/bus/usb/001/012 PRODUCT=5e1/400/5 TYPE=0/0/0 INTERFACE=255/255/255 MODALIAS=usb:v05E1p0400d0005dc00dsc00dp00icFFiscFFipFF SEQNUM=1617 UDEVD_EVENT=1 UDEV [1227456137.535262] add /class/usb_endpoint/usbdev1.12_ep81 (usb_endpoint) UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep81 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=8 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0 PHYSDEVBUS=usb SEQNUM=1607 UDEVD_EVENT=1 DEVNAME=/dev/usbdev1.12_ep81 UDEV [1227456137.542033] add /class/usb_endpoint/usbdev1.12_ep83 (usb_endpoint) UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep83 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=11 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.3 PHYSDEVBUS=usb SEQNUM=1618 UDEVD_EVENT=1 DEVNAME=/dev/usbdev1.12_ep83 UDEV [1227456137.545002] add /class/usb_endpoint/usbdev1.12_ep00 (usb_endpoint) UDEV_LOG=3 ACTION=add DEVPATH=/class/usb_endpoint/usbdev1.12_ep00 SUBSYSTEM=usb_endpoint MAJOR=250 MINOR=12 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-2 PHYSDEVBUS=usb PHYSDEVDRIVER=usb SEQNUM=1619 UDEVD_EVENT=1 DEVNAME=/dev/usbdev1.12_ep00 _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 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 1 sibling, 1 reply; 16+ messages in thread From: Michael Krufky @ 2008-11-23 19:21 UTC (permalink / raw) To: Bob Cunningham; +Cc: linux-dvb On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: > Hi, > > I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: > > Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd > > A quick search revealed that the au0828 driver had recently been updated (10 Nov) to support this USB ID. > > Following instructions on the wiki, I obtained the latest v4l-dvb source via Mercurial, and built/installed it without error. Next I did "modprobe au0828", and dmesg provided the following: > > au0828 driver loaded > usbcore: registered new interface driver au0828 > > Next I did "lsmod | grep au0828", which provides the following: > > au0828 20384 0 > dvb_core 68673 1 au0828 > tveeprom 14917 1 au0828 > i2c_core 20949 4 au0828,tveeprom,nvidia,i2c_i801 > > dmesg provides the following when the device is plugged in: > > usb 1-2: new high speed USB device using ehci_hcd and address 10 > usb 1-2: configuration #1 chosen from 1 choice > 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 > > However, I have no /dev/dvb. I unplugged/replugged several times, with no change. > > I rebooted and repeated the modprobe and the unplug/replug, with no different results. > > My guess is that udev isn't making the connection from the USB ID, but I'm not sure what to do about it. > > I'm running a fully updated FC8 on a Dell dual Xeon-HT server with kernel 2.6.26.6-49.fc8 #1 SMP. > > Did I miss something basic? Bob, A patch was submitted that adds support for a device with usb ID 05e1:0400, but it did not get merged yet. The reason why I didn't merge the patch yet, is that there are multiple devices out there using this USB id but they have different internal components and no way to differentiate between the two. If you can open up your stick and tell us what is printed on each chip, then I can help you get yours working. -Mike _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 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 0 siblings, 2 replies; 16+ messages in thread From: CityK @ 2008-11-23 19:40 UTC (permalink / raw) To: Michael Krufky; +Cc: Bob Cunningham, linux-dvb Michael Krufky wrote: > On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: > >> Hi, >> >> I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: >> >> Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd >> >> A quick search revealed that the au0828 driver .... >> > > Bob, > > A patch was submitted that adds support for a device with usb ID > 05e1:0400, but it did not get merged yet. > > The reason why I didn't merge the patch yet, is that there are > multiple devices out there using this USB id but they have different > internal components and no way to differentiate between the two. > > If you can open up your stick and tell us what is printed on each > chip, then I can help you get yours working. Likely (as mentioned in the related discussion/thread: http://marc.info/?l=linux-dvb&m=122472907625204&w=2): - Microtune MT213x (tuner) - Auvitek AU850x (demod) - Auvitek AU0828 (usb) _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-23 19:40 ` CityK @ 2008-11-23 19:48 ` CityK 2008-11-24 1:08 ` Bob Cunningham 1 sibling, 0 replies; 16+ messages in thread From: CityK @ 2008-11-23 19:48 UTC (permalink / raw) To: Michael Krufky; +Cc: Bob Cunningham, linux-dvb CityK wrote: > Likely (as mentioned in the related discussion/thread: > http://marc.info/?l=linux-dvb&m=122472907625204&w=2): > > - Microtune MT213x (tuner) > - Auvitek AU850x (demod) > - Auvitek AU0828 (usb) Here's a listing example: http://www.acesuppliers.com/Supplier_Company/USB-2-0-AnyTV-ATSC-Stick_Product_Showroom_37331.html Bob, if you open it up, can you take some high res images and upload them to the wiki: http://www.linuxtv.org/wiki/index.php?title=Shenzhen_Forward_Video_AnyTV-ATSC_Stick&action=edit I'm also curious if these are indeed LifeView OEM's (as I speculated on: http://www.linuxtv.org/wiki/index.php/ATSC_USB_Devices#Currently_Unsupported_ATSC_USB_Devices ) ... if so, the pcb would have a LRxxx model number silk screened on to it somewhere _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 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 4:50 ` CityK 1 sibling, 2 replies; 16+ messages in thread From: Bob Cunningham @ 2008-11-24 1:08 UTC (permalink / raw) To: CityK; +Cc: linux-dvb, Michael Krufky CityK wrote: > Michael Krufky wrote: >> On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: >> >>> Hi, >>> >>> I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: >>> >>> Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd >>> >>> A quick search revealed that the au0828 driver .... >>> >> Bob, >> >> A patch was submitted that adds support for a device with usb ID >> 05e1:0400, but it did not get merged yet. >> >> The reason why I didn't merge the patch yet, is that there are >> multiple devices out there using this USB id but they have different >> internal components and no way to differentiate between the two. >> >> If you can open up your stick and tell us what is printed on each >> chip, then I can help you get yours working. > > Likely (as mentioned in the related discussion/thread: > http://marc.info/?l=linux-dvb&m=122472907625204&w=2): > > - Microtune MT213x (tuner) > - Auvitek AU850x (demod) > - Auvitek AU0828 (usb) > There are 3 chips, from the USB to the cable connector they are: AU0828A AU8522AA MT2131F The silk screen text on the PC board reads "AUTV002_Ver1.0c" Pictures soon! -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-24 1:08 ` Bob Cunningham @ 2008-11-24 1:33 ` Bob Cunningham 2008-11-24 2:34 ` Bob Cunningham 2008-11-24 4:50 ` CityK 1 sibling, 1 reply; 16+ messages in thread From: Bob Cunningham @ 2008-11-24 1:33 UTC (permalink / raw) Cc: linux-dvb Bob Cunningham wrote: > CityK wrote: >> Michael Krufky wrote: >>> On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: >>>> >>>> Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd >>>> >>>> A quick search revealed that the au0828 driver .... >>>> >>> Bob, >>> >>> A patch was submitted that adds support for a device with usb ID >>> 05e1:0400, but it did not get merged yet. >>> >>> The reason why I didn't merge the patch yet, is that there are >>> multiple devices out there using this USB id but they have different >>> internal components and no way to differentiate between the two. >>> >>> If you can open up your stick and tell us what is printed on each >>> chip, then I can help you get yours working. >> Likely (as mentioned in the related discussion/thread: >> http://marc.info/?l=linux-dvb&m=122472907625204&w=2): >> >> - Microtune MT213x (tuner) >> - Auvitek AU850x (demod) >> - Auvitek AU0828 (usb) >> > > There are 3 chips, from the USB to the cable connector they are: > AU0828A > AU8522AA > MT2131F > > The silk screen text on the PC board reads "AUTV002_Ver1.0c" > > Pictures soon! > > -BobC Hi yet again, I checked the source, and it seems the patch I found (http://marc.info/?l=linux-dvb&m=122416362902362&w=2) had indeed not yet been committed to the tree. I applied it to my updated source and reinstalled v4l. The following devices now appear: /dev/audio1 /dev/dsp1 /dev/dvb/adapter0 /dev/mixer1 /dev/ptmx I have no idea if they are functional! I tried running xine, but I am unfamiliar with it, so I don't know if there is a problem in the driver, or if it is a PEBKAC. What is the preferred testing strategy? Thanks, -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-24 1:33 ` Bob Cunningham @ 2008-11-24 2:34 ` Bob Cunningham 2008-11-24 3:05 ` Bob Cunningham 0 siblings, 1 reply; 16+ messages in thread From: Bob Cunningham @ 2008-11-24 2:34 UTC (permalink / raw) To: linux-dvb Bob Cunningham wrote: > Bob Cunningham wrote: >> CityK wrote: >>> Michael Krufky wrote: >>>> On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: >>>>> >>>>> Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd >>>>> >>>>> A quick search revealed that the au0828 driver .... >>>>> >>>> Bob, >>>> >>>> A patch was submitted that adds support for a device with usb ID >>>> 05e1:0400, but it did not get merged yet. >>>> >>>> The reason why I didn't merge the patch yet, is that there are >>>> multiple devices out there using this USB id but they have different >>>> internal components and no way to differentiate between the two. >>>> >>>> If you can open up your stick and tell us what is printed on each >>>> chip, then I can help you get yours working. >>> Likely (as mentioned in the related discussion/thread: >>> http://marc.info/?l=linux-dvb&m=122472907625204&w=2): >>> >>> - Microtune MT213x (tuner) >>> - Auvitek AU850x (demod) >>> - Auvitek AU0828 (usb) >>> >> There are 3 chips, from the USB to the cable connector they are: >> AU0828A >> AU8522AA >> MT2131F >> >> The silk screen text on the PC board reads "AUTV002_Ver1.0c" >> >> Pictures soon! >> >> -BobC > > Hi yet again, > > I checked the source, and it seems the patch I found (http://marc.info/?l=linux-dvb&m=122416362902362&w=2) had indeed not yet been committed to the tree. I applied it to my updated source and reinstalled v4l. The following devices now appear: > > /dev/audio1 > /dev/dsp1 > /dev/dvb/adapter0 > /dev/mixer1 > /dev/ptmx > > I have no idea if they are functional! I tried running xine, but I am unfamiliar with it, so I don't know if there is a problem in the driver, or if it is a PEBKAC. > > What is the preferred testing strategy? > > > Thanks, > > -BobC As I stumbled through the maze, I was suddenly struck by a clue-by-4, and the following occurred: $ dvbscan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB Unable to query frontend status I take it this is not a good thing. -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-24 2:34 ` Bob Cunningham @ 2008-11-24 3:05 ` Bob Cunningham 0 siblings, 0 replies; 16+ messages in thread From: Bob Cunningham @ 2008-11-24 3:05 UTC (permalink / raw) To: linux-dvb Bob Cunningham wrote: > Bob Cunningham wrote: >> Bob Cunningham wrote: >>> CityK wrote: >>>> Michael Krufky wrote: >>>>> On Sat, Nov 22, 2008 at 4:46 PM, Bob Cunningham <FlyMyPG@gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I just bought an AnyTV AUTV002 USB Tuner Stick from DealExtreme. When plugged in, lsusb provides the following: >>>>>> >>>>>> Bus 001 Device 011: ID 05e1:0400 Syntek Semiconductor Co., Ltd >>>>>> >>>>>> A quick search revealed that the au0828 driver .... >>>>>> >>>>> Bob, >>>>> >>>>> A patch was submitted that adds support for a device with usb ID >>>>> 05e1:0400, but it did not get merged yet. >>>>> >>>>> The reason why I didn't merge the patch yet, is that there are >>>>> multiple devices out there using this USB id but they have different >>>>> internal components and no way to differentiate between the two. >>>>> >>>>> If you can open up your stick and tell us what is printed on each >>>>> chip, then I can help you get yours working. >>>> Likely (as mentioned in the related discussion/thread: >>>> http://marc.info/?l=linux-dvb&m=122472907625204&w=2): >>>> >>>> - Microtune MT213x (tuner) >>>> - Auvitek AU850x (demod) >>>> - Auvitek AU0828 (usb) >>>> >>> There are 3 chips, from the USB to the cable connector they are: >>> AU0828A >>> AU8522AA >>> MT2131F >>> >>> The silk screen text on the PC board reads "AUTV002_Ver1.0c" >>> >>> Pictures soon! >>> >>> -BobC >> Hi yet again, >> >> I checked the source, and it seems the patch I found (http://marc.info/?l=linux-dvb&m=122416362902362&w=2) had indeed not yet been committed to the tree. I applied it to my updated source and reinstalled v4l. The following devices now appear: >> >> /dev/audio1 >> /dev/dsp1 >> /dev/dvb/adapter0 >> /dev/mixer1 >> /dev/ptmx >> >> I have no idea if they are functional! I tried running xine, but I am unfamiliar with it, so I don't know if there is a problem in the driver, or if it is a PEBKAC. >> >> What is the preferred testing strategy? >> >> >> Thanks, >> >> -BobC > > > As I stumbled through the maze, I was suddenly struck by a clue-by-4, and the following occurred: > > $ dvbscan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB > Unable to query frontend status > > I take it this is not a good thing. > > > -BobC Tried this next: $ scan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB scanning /usr/share/dvb-apps/atsc/us-ATSC-center-frequencies-8VSB using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' >>> tune to: 57028615:8VSB WARNING: >>> tuning failed!!! >>> tune to: 57028615:8VSB (tuning failed) ... snip over 40 other attempts ... >>> tune to: 803028615:8VSB WARNING: >>> tuning failed!!! >>> tune to: 803028615:8VSB (tuning failed) WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. Still not success, but at least the devices were found and are accessible. -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-24 1:08 ` Bob Cunningham 2008-11-24 1:33 ` Bob Cunningham @ 2008-11-24 4:50 ` CityK [not found] ` <492B9B98.5060603@gmail.com> 1 sibling, 1 reply; 16+ messages in thread From: CityK @ 2008-11-24 4:50 UTC (permalink / raw) To: Bob Cunningham; +Cc: linux-dvb, Michael Krufky Bob Cunningham wrote: > There are 3 chips, from the USB to the cable connector they are: > AU0828A > AU8522AA > MT2131F > > The silk screen text on the PC board reads "AUTV002_Ver1.0c" > > Pictures soon! Okay, thanks > Hi yet again, > > > > I checked the source, and it seems the patch I found (http://marc.info/?l=linux-dvb&m=122416362902362&w=2) had indeed not yet been committed to the tree. I applied it to my updated source and reinstalled v4l. The following devices now appear: > > > > /dev/audio1 > > /dev/dsp1 > > /dev/dvb/adapter0 > > /dev/mixer1 > > /dev/ptmx > > > > I have no idea if they are functional! I tried running xine, but I am unfamiliar with it, so I don't know if there is a problem in the driver, or if it is a PEBKAC. > > > > What is the preferred testing strategy? > > > > > > Thanks, > > > > -BobC > > > > As I stumbled through the maze, I was suddenly struck by a clue-by-4, and the following occurred: > > $ dvbscan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB > Unable to query frontend status > > I take it this is not a good thing. > > ... > > Tried this next: > $ scan /usr/share/dvb/atsc/us-ATSC-center-frequencies-8VSB > scanning /usr/share/dvb-apps/atsc/us-ATSC-center-frequencies-8VSB > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > >>> tune to: 57028615:8VSB > WARNING: >>> tuning failed!!! > >>> tune to: 57028615:8VSB (tuning failed) > ... snip over 40 other attempts ... > >>> tune to: 803028615:8VSB > WARNING: >>> tuning failed!!! > >>> tune to: 803028615:8VSB (tuning failed) > WARNING: >>> tuning failed!!! > ERROR: initial tuning failed > dumping lists (0 services) > Done. > > Still not success, but at least the devices were found and are accessible. > What tuner is being listed in your dmesg output ? _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
[parent not found: <492B9B98.5060603@gmail.com>]
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick [not found] ` <492B9B98.5060603@gmail.com> @ 2008-11-26 1:36 ` CityK 2008-11-26 7:18 ` Bob Cunningham 0 siblings, 1 reply; 16+ messages in thread From: CityK @ 2008-11-26 1:36 UTC (permalink / raw) To: Bob Cunningham, linux-dvb 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 ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-26 1:36 ` CityK @ 2008-11-26 7:18 ` Bob Cunningham 2008-11-27 16:11 ` CityK 0 siblings, 1 reply; 16+ messages in thread From: Bob Cunningham @ 2008-11-26 7:18 UTC (permalink / raw) To: CityK; +Cc: linux-dvb CityK wrote: > 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. > What are the next steps? 1. How much effort will be needed to make this driver work? 2. Do all of the pieces already exist? (All the chips seem to be mentioned somewhere in the DVB tree.) 3. What new code is needed? 4. How much reverse-engineering needs to be done? Will a full schematic be needed? Most importantly: 5. How can I help? I'm a real-time embedded systems programmer with 25 years experience, though most of what I've written runs on "bare metal", often without an OS. I know nothing about Linux device drivers. However, I am very good at getting local hardware to "play nice", first by poking it with a debugger, then generally by scripting through /dev/port. I've never worked with hardware across the USB bus, though I have brought up USB interface hardware from the CPU side, and have had to snoop USB traffic to diagnose problems. Unfortunately, I don't have a Windows system available to use to snoop the USB traffic from the driver provided by the vendor, though I haven't yet tried to get anything to work via Wine. I'll be taking lots of time off in December, and should have some time to put toward this project. If anyone else is curious, or wants to help, the product is here: http://www.dealextreme.com/details.dx/sku.15569 I also found a brief description of a reference design here: http://www.auvitek.com/AU8522%20MT%20USB%20TV%20Stick%20Design%20Brief_R1.0.pdf -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-26 7:18 ` Bob Cunningham @ 2008-11-27 16:11 ` CityK 2008-11-27 19:28 ` Michael Krufky 0 siblings, 1 reply; 16+ messages in thread From: CityK @ 2008-11-27 16:11 UTC (permalink / raw) To: Bob Cunningham; +Cc: linux-dvb Bob Cunningham wrote: > What are the next steps? > 1. How much effort will be needed to make this driver work? > 2. Do all of the pieces already exist? (All the chips seem to be > mentioned somewhere in the DVB tree.) > 3. What new code is needed? > 4. How much reverse-engineering needs to be done? Will a full > schematic be needed? > > Most importantly: > 5. How can I help? > > I'm a real-time embedded systems programmer with 25 years experience, > though most of what I've written runs on "bare metal", often without > an OS. I know nothing about Linux device drivers. However, I am very > good at getting local hardware to "play nice", first by poking it with > a debugger, then generally by scripting through /dev/port. > I've never worked with hardware across the USB bus, though I have > brought up USB interface hardware from the CPU side, and have had to > snoop USB traffic to diagnose problems. Unfortunately, I don't have a > Windows system available to use to snoop the USB traffic from the > driver provided by the vendor, though I haven't yet tried to get > anything to work via Wine. > > I'll be taking lots of time off in December, and should have some time > to put toward this project. > > If anyone else is curious, or wants to help, the product is here: > http://www.dealextreme.com/details.dx/sku.15569 > > I also found a brief description of a reference design here: > http://www.auvitek.com/AU8522%20MT%20USB%20TV%20Stick%20Design%20Brief_R1.0.pdf 1 - probably not a lot 2 - sounds like it, but I do not know how far developed the MT2131 driver is 3 - probably just the "glue code" to tie all the pieces together 4 - likely none (there may be a chance the the components are wired up slightly differently, such as in the case with GPIO pins, in which case you'd have to try to discover the true configuration....schematics would obviously help, but probably 99.99% of cases are resolved without such aide ) 5 - you can add the support for the device ! :P Because of the advanced state (component drivers already exist) you won't need any in depth knowledge about the developing device drivers. At this point, all you will need to do is figure out where to insert the necessary glue code in the existing modules - have a look in the source code of the respective components (eg. /linux/drivers/media/video/au0828/ ; /linux/drivers/media/dvb/frontends/ ; .... ). Note that the AU0828 does not currently support analog (http://marc.info/?l=linux-video&m=122459807631633&w=2). I suspect that solving the EEPROM issue is just a matter of adjusting the code so that it is not specifically expecting a Hauppauge signature. Getting the device to attach the correct tuner should be, I imagine, fairly straight forward too . It would appear that this device is highly similar to the Woodbury (see: http://marc.info/?l=linux-dvb&m=122617795121243&w=2); I do not know whether there is significant difference between the respective MT parts -- might be trivial, then again it might not be _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-27 16:11 ` CityK @ 2008-11-27 19:28 ` Michael Krufky 2008-12-19 6:43 ` Bob Cunningham 0 siblings, 1 reply; 16+ messages in thread From: Michael Krufky @ 2008-11-27 19:28 UTC (permalink / raw) To: CityK; +Cc: Bob Cunningham, Mark Kimsal, linux-dvb On Thu, Nov 27, 2008 at 11:11 AM, CityK <cityk@rogers.com> wrote: > Bob Cunningham wrote: >> What are the next steps? >> 1. How much effort will be needed to make this driver work? >> 2. Do all of the pieces already exist? (All the chips seem to be >> mentioned somewhere in the DVB tree.) >> 3. What new code is needed? >> 4. How much reverse-engineering needs to be done? Will a full >> schematic be needed? >> >> Most importantly: >> 5. How can I help? >> >> I'm a real-time embedded systems programmer with 25 years experience, >> though most of what I've written runs on "bare metal", often without >> an OS. I know nothing about Linux device drivers. However, I am very >> good at getting local hardware to "play nice", first by poking it with >> a debugger, then generally by scripting through /dev/port. >> I've never worked with hardware across the USB bus, though I have >> brought up USB interface hardware from the CPU side, and have had to >> snoop USB traffic to diagnose problems. Unfortunately, I don't have a >> Windows system available to use to snoop the USB traffic from the >> driver provided by the vendor, though I haven't yet tried to get >> anything to work via Wine. >> >> I'll be taking lots of time off in December, and should have some time >> to put toward this project. >> >> If anyone else is curious, or wants to help, the product is here: >> http://www.dealextreme.com/details.dx/sku.15569 >> >> I also found a brief description of a reference design here: >> http://www.auvitek.com/AU8522%20MT%20USB%20TV%20Stick%20Design%20Brief_R1.0.pdf > > 1 - probably not a lot > 2 - sounds like it, but I do not know how far developed the MT2131 > driver is > 3 - probably just the "glue code" to tie all the pieces together > 4 - likely none (there may be a chance the the components are wired up > slightly differently, such as in the case with GPIO pins, in which case > you'd have to try to discover the true configuration....schematics would > obviously help, but probably 99.99% of cases are resolved without such > aide ) > 5 - you can add the support for the device ! :P Because of the > advanced state (component drivers already exist) you won't need any in > depth knowledge about the developing device drivers. At this point, all > you will need to do is figure out where to insert the necessary glue > code in the existing modules - have a look in the source code of the > respective components (eg. /linux/drivers/media/video/au0828/ ; > /linux/drivers/media/dvb/frontends/ ; .... ). Note that the AU0828 does > not currently support analog > (http://marc.info/?l=linux-video&m=122459807631633&w=2). > > I suspect that solving the EEPROM issue is just a matter of adjusting > the code so that it is not specifically expecting a Hauppauge > signature. Getting the device to attach the correct tuner should be, I > imagine, fairly straight forward too . It would appear that this device > is highly similar to the Woodbury (see: > http://marc.info/?l=linux-dvb&m=122617795121243&w=2); I do not know > whether there is significant difference between the respective MT parts > -- might be trivial, then again it might not be I am hosting experimental support for these devices in the following mercurial repository: http://linuxtv.org/hg/~mkrufky/teledongle Please generate any patches, if any, against the above tree. If you read the comments that I wrote in the changesets in that tree, it explains what I know about these devices. Ignore the "syntek teledongle" name for now -- there are so many of these different devices floating around with the same USB ID that the name really doesnt matter. If this works for you, please let me know. So far, the tda18271 version works, but the mt2131 version does not. -Mike _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [linux-dvb] AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-11-27 19:28 ` Michael Krufky @ 2008-12-19 6:43 ` Bob Cunningham 2009-03-04 17:24 ` Bob Cunningham 0 siblings, 1 reply; 16+ messages in thread From: Bob Cunningham @ 2008-12-19 6:43 UTC (permalink / raw) To: Michael Krufky; +Cc: Mark Kimsal, linux-dvb Michael Krufky wrote: > On Thu, Nov 27, 2008 at 11:11 AM, CityK <cityk@rogers.com> wrote: >> Bob Cunningham wrote: >>> What are the next steps? >>> 1. How much effort will be needed to make this driver work? >>> 2. Do all of the pieces already exist? (All the chips seem to be >>> mentioned somewhere in the DVB tree.) >>> 3. What new code is needed? >>> 4. How much reverse-engineering needs to be done? Will a full >>> schematic be needed? >>> >>> Most importantly: >>> 5. How can I help? >>> >>> I'm a real-time embedded systems programmer with 25 years experience, >>> though most of what I've written runs on "bare metal", often without >>> an OS. I know nothing about Linux device drivers. However, I am very >>> good at getting local hardware to "play nice", first by poking it with >>> a debugger, then generally by scripting through /dev/port. >>> I've never worked with hardware across the USB bus, though I have >>> brought up USB interface hardware from the CPU side, and have had to >>> snoop USB traffic to diagnose problems. Unfortunately, I don't have a >>> Windows system available to use to snoop the USB traffic from the >>> driver provided by the vendor, though I haven't yet tried to get >>> anything to work via Wine. >>> >>> I'll be taking lots of time off in December, and should have some time >>> to put toward this project. >>> >>> If anyone else is curious, or wants to help, the product is here: >>> http://www.dealextreme.com/details.dx/sku.15569 >>> >>> I also found a brief description of a reference design here: >>> http://www.auvitek.com/AU8522%20MT%20USB%20TV%20Stick%20Design%20Brief_R1.0.pdf >> 1 - probably not a lot >> 2 - sounds like it, but I do not know how far developed the MT2131 >> driver is >> 3 - probably just the "glue code" to tie all the pieces together >> 4 - likely none (there may be a chance the the components are wired up >> slightly differently, such as in the case with GPIO pins, in which case >> you'd have to try to discover the true configuration....schematics would >> obviously help, but probably 99.99% of cases are resolved without such >> aide ) >> 5 - you can add the support for the device ! :P Because of the >> advanced state (component drivers already exist) you won't need any in >> depth knowledge about the developing device drivers. At this point, all >> you will need to do is figure out where to insert the necessary glue >> code in the existing modules - have a look in the source code of the >> respective components (eg. /linux/drivers/media/video/au0828/ ; >> /linux/drivers/media/dvb/frontends/ ; .... ). Note that the AU0828 does >> not currently support analog >> (http://marc.info/?l=linux-video&m=122459807631633&w=2). >> >> I suspect that solving the EEPROM issue is just a matter of adjusting >> the code so that it is not specifically expecting a Hauppauge >> signature. Getting the device to attach the correct tuner should be, I >> imagine, fairly straight forward too . It would appear that this device >> is highly similar to the Woodbury (see: >> http://marc.info/?l=linux-dvb&m=122617795121243&w=2); I do not know >> whether there is significant difference between the respective MT parts >> -- might be trivial, then again it might not be > > I am hosting experimental support for these devices in the following > mercurial repository: > > http://linuxtv.org/hg/~mkrufky/teledongle > > Please generate any patches, if any, against the above tree. > > If you read the comments that I wrote in the changesets in that tree, > it explains what I know about these devices. > > Ignore the "syntek teledongle" name for now -- there are so many of > these different devices floating around with the same USB ID that the > name really doesnt matter. > > If this works for you, please let me know. So far, the tda18271 > version works, but the mt2131 version does not. > > -Mike > Sorry for the delay! I got, built and installed the teledongle tree, and dmesg provided the following output: usb 1-2: new high speed USB device using ehci_hcd and address 7 usb 1-2: configuration #1 chosen from 1 choice 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 au0828 driver loaded au0828: i2c bus registered 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 MT2131: successfully identified at address 0x60 DVB: registering new adapter (au0828) DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... Registered device AU0828 [Syntek Teledongle [EXPERIMENTAL]] usbcore: registered new interface driver au0828 And dvbscan was still "Unable to query frontend status". It will take me longer than expected to get into the code. If an experineced v4l developer would like to take on this device, I'll donate one to the cause. I'll stay in the loop for testing, and to learn how it is done. Thanks, -BobC _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: AnyTV AUTV002 USB ATSC/QAM Tuner Stick 2008-12-19 6:43 ` Bob Cunningham @ 2009-03-04 17:24 ` Bob Cunningham 0 siblings, 0 replies; 16+ messages in thread From: Bob Cunningham @ 2009-03-04 17:24 UTC (permalink / raw) To: Michael Krufky, linux-media Hi, I have not been able to put any serious time into this project, and I'd like to reiterate my offer to buy one of these devices (http://www.dealextreme.com/details.dx/sku.15569) for an experienced v4l developer who would like to give it a try. I will stay in the loop for testing (FC10 on Dell SC1420). Blame my new girlfriend: My evenings are no longer my own. And I don't mind it one bit! -BobC Bob Cunningham wrote: > Michael Krufky wrote: >> On Thu, Nov 27, 2008 at 11:11 AM, CityK <cityk@rogers.com> wrote: >>> Bob Cunningham wrote: >>>> What are the next steps? >>>> 1. How much effort will be needed to make this driver work? >>>> 2. Do all of the pieces already exist? (All the chips seem to be >>>> mentioned somewhere in the DVB tree.) >>>> 3. What new code is needed? >>>> 4. How much reverse-engineering needs to be done? Will a full >>>> schematic be needed? >>>> >>>> Most importantly: >>>> 5. How can I help? >>>> >>>> I'm a real-time embedded systems programmer with 25 years experience, >>>> though most of what I've written runs on "bare metal", often without >>>> an OS. I know nothing about Linux device drivers. However, I am very >>>> good at getting local hardware to "play nice", first by poking it with >>>> a debugger, then generally by scripting through /dev/port. >>>> I've never worked with hardware across the USB bus, though I have >>>> brought up USB interface hardware from the CPU side, and have had to >>>> snoop USB traffic to diagnose problems. Unfortunately, I don't have a >>>> Windows system available to use to snoop the USB traffic from the >>>> driver provided by the vendor, though I haven't yet tried to get >>>> anything to work via Wine. >>>> >>>> I'll be taking lots of time off in December, and should have some time >>>> to put toward this project. >>>> >>>> If anyone else is curious, or wants to help, the product is here: >>>> http://www.dealextreme.com/details.dx/sku.15569 >>>> >>>> I also found a brief description of a reference design here: >>>> http://www.auvitek.com/AU8522%20MT%20USB%20TV%20Stick%20Design%20Brief_R1.0.pdf >>> 1 - probably not a lot >>> 2 - sounds like it, but I do not know how far developed the MT2131 >>> driver is >>> 3 - probably just the "glue code" to tie all the pieces together >>> 4 - likely none (there may be a chance the the components are wired up >>> slightly differently, such as in the case with GPIO pins, in which case >>> you'd have to try to discover the true configuration....schematics would >>> obviously help, but probably 99.99% of cases are resolved without such >>> aide ) >>> 5 - you can add the support for the device ! :P Because of the >>> advanced state (component drivers already exist) you won't need any in >>> depth knowledge about the developing device drivers. At this point, all >>> you will need to do is figure out where to insert the necessary glue >>> code in the existing modules - have a look in the source code of the >>> respective components (eg. /linux/drivers/media/video/au0828/ ; >>> /linux/drivers/media/dvb/frontends/ ; .... ). Note that the AU0828 does >>> not currently support analog >>> (http://marc.info/?l=linux-video&m=122459807631633&w=2). >>> >>> I suspect that solving the EEPROM issue is just a matter of adjusting >>> the code so that it is not specifically expecting a Hauppauge >>> signature. Getting the device to attach the correct tuner should be, I >>> imagine, fairly straight forward too . It would appear that this device >>> is highly similar to the Woodbury (see: >>> http://marc.info/?l=linux-dvb&m=122617795121243&w=2); I do not know >>> whether there is significant difference between the respective MT parts >>> -- might be trivial, then again it might not be >> I am hosting experimental support for these devices in the following >> mercurial repository: >> >> http://linuxtv.org/hg/~mkrufky/teledongle >> >> Please generate any patches, if any, against the above tree. >> >> If you read the comments that I wrote in the changesets in that tree, >> it explains what I know about these devices. >> >> Ignore the "syntek teledongle" name for now -- there are so many of >> these different devices floating around with the same USB ID that the >> name really doesnt matter. >> >> If this works for you, please let me know. So far, the tda18271 >> version works, but the mt2131 version does not. >> >> -Mike >> > > Sorry for the delay! I got, built and installed the teledongle tree, and dmesg provided the following output: > > usb 1-2: new high speed USB device using ehci_hcd and address 7 > usb 1-2: configuration #1 chosen from 1 choice > 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 > au0828 driver loaded > au0828: i2c bus registered > 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 > MT2131: successfully identified at address 0x60 > DVB: registering new adapter (au0828) > DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... > Registered device AU0828 [Syntek Teledongle [EXPERIMENTAL]] > usbcore: registered new interface driver au0828 > > And dvbscan was still "Unable to query frontend status". > > It will take me longer than expected to get into the code. If an experineced v4l developer would like to take on this device, I'll donate one to the cause. I'll stay in the loop for testing, and to learn how it is done. > > > Thanks, > > -BobC > > _______________________________________________ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-03-04 22:23 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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).