[linux-dvb] [PATCH] Add syntek corp device to au0828

[linux-dvb] [PATCH] Add syntek corp device to au0828

[Mark Kimsal]

The woodbury is the first model I chose, and it seems to work.  I tried two 
others and they do not tune any channels, although the module au0828 does 
load.  Watching ATSC works fine, haven't tried NTSC or QAM.

diff -r 9273407ca6e1 linux/drivers/media/video/au0828/au0828-cards.c
--- a/linux/drivers/media/video/au0828/au0828-cards.c   Wed Oct 15 02:50:03 
2008 +0400
+++ b/linux/drivers/media/video/au0828/au0828-cards.c   Thu Oct 16 09:23:50 
2008 -0400
@@ -212,6 +212,8 @@ struct usb_device_id au0828_usb_id_table
                .driver_info = AU0828_BOARD_HAUPPAUGE_HVR950Q_MXL },
        { USB_DEVICE(0x2040, 0x8200),
                .driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },
+       { USB_DEVICE(0x05e1, 0x0400),
+               .driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },
        { },
 };


-- 
Mark Kimsal
http://biz.metrofindings.com/
Fax: 866-375-1590

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

Re: [linux-dvb] [PATCH] Add syntek corp device to au0828

[Michael Krufky]

On Thu, Oct 16, 2008 at 9:25 AM, Mark Kimsal <mark@metrofindings.com> wrote:
> The woodbury is the first model I chose, and it seems to work.  I tried two
> others and they do not tune any channels, although the module au0828 does
> load.  Watching ATSC works fine, haven't tried NTSC or QAM.
>
> diff -r 9273407ca6e1 linux/drivers/media/video/au0828/au0828-cards.c
> --- a/linux/drivers/media/video/au0828/au0828-cards.c   Wed Oct 15 02:50:03
> 2008 +0400
> +++ b/linux/drivers/media/video/au0828/au0828-cards.c   Thu Oct 16 09:23:50
> 2008 -0400
> @@ -212,6 +212,8 @@ struct usb_device_id au0828_usb_id_table
>                .driver_info = AU0828_BOARD_HAUPPAUGE_HVR950Q_MXL },
>        { USB_DEVICE(0x2040, 0x8200),
>                .driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },
> +       { USB_DEVICE(0x05e1, 0x0400),
> +               .driver_info = AU0828_BOARD_HAUPPAUGE_WOODBURY },
>        { },
>  };

Mark,

I thought this stick had an MT2130 inside -- looks like you've got
another revision with a TDA18271... very interesting :-)

You say that ATSC works -- does it work on more than just one channel?
 If ATSC works, then QAM should work as well.  NTSC is not yet
supported in the Linux driver.

Can you show me the dmesg output when the driver loads?  Also, can you
give me the exact name of the device (from the retail package) ?

Regards,

Mike

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

Re: [linux-dvb] [PATCH] Add syntek corp device to au0828

[Mark Kimsal]

On Thursday 16 October 2008 11:11:39 am you wrote:
> On Thu, Oct 16, 2008 at 9:25 AM, Mark Kimsal <mark@metrofindings.com> wrote:
[snip]
>
> Mark,
>
> I thought this stick had an MT2130 inside -- looks like you've got
> another revision with a TDA18271... very interesting :-)
>
> You say that ATSC works -- does it work on more than just one channel?
>  If ATSC works, then QAM should work as well.  NTSC is not yet
> supported in the Linux driver.
>
> Can you show me the dmesg output when the driver loads?  Also, can you
> give me the exact name of the device (from the retail package) ?
>
> Regards,
>
> Mike


Yes, more than one channel works.  I do see the module TDA18721 loaded along 
with a couple other.  Again, I'm not 100% sure that this is the woodbury, but 
it works.  I can scan channels, I've watched 4-5 stations.  It seems to 
kernel oops every once in a while on very static-y stations.

I just upgraded to 2.6.27 and it doesn't work anymore.  Modprobing au0828 does 
not load up any other modules like the tda18721 and does not create 
a /dev/dvb folder.  This is a problem with the latest hg tip of v4l-dvb.


dmesg from 2.6.27 (not working):
usb 1-2: new high speed USB device using ehci_hcd and address 2
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
usbcore: registered new interface driver au0828
usbcore: registered new interface driver snd-usb-audio

dmesg from 2.6.24 (working):
usb 1-2: new high speed USB device using ehci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
au0828: i2c bus registered
tveeprom 1-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 1-0060: creating new instance
TDA18271HD/C2 detected @ 1-0060
DVB: registering new adapter (au0828)
DVB: registering frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
Registered device AU0828 [Hauppauge Woodbury]


As per my other email (sabrent/auvitek unknown usb device) I'm not entirely 
sure of the brand name.  The Web store lists it as "sabrent".  lsusb says 
it's "syntek", but Windows and the device manager says it's an "auvitek".  
The box has literally no brand name.  The only "brand" looking things are 
just acronyms like NTSC and ATSC.  The windows .inf file for the driver is 
littered with the words "auvitek international", "copyright auvitek" and the 
like....

Although I didn't buy the device, the first brand name that I identified would 
be "auvitek".  Sabrent was only found after back tracking to the the retailer 
and seeing the product page.  I don't think that "Syntek" is the proper 
coporation for the usb vendor ID of 05e1.

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

[linux-dvb] [PATCH] Add syntek corp device to au0828

[CityK]

Mark Kimsal wrote:

> mkrufky wrote:
> > can you give me the exact name of the device (from the retail package) ?
> As per my other email (sabrent/auvitek unknown usb device) I'm not
> entirely
> sure of the brand name.  The Web store lists it as "sabrent".  lsusb says 
> it's "syntek", but Windows and the device manager says it's an "auvitek".  
> The box has literally no brand name.  The only "brand" looking things are 
> just acronyms like NTSC and ATSC.  The windows .inf file for the driver is 
> littered with the words "auvitek international", "copyright auvitek" and the 
> like....
>
> Although I didn't buy the device, the first brand name that I identified would 
> be "auvitek".  Sabrent was only found after back tracking to the the retailer 
> and seeing the product page.  I don't think that "Syntek" is the proper 
> coporation for the usb vendor ID of 05e1.

http://www.linuxtv.org/wiki/index.php/Sabrent_TV-USBHD



mkrufky wrote:

> I thought this stick had an MT2130 inside -- looks like you've got
> another revision with a TDA18271... very interesting :-)


I believe that the AnyTV sticks, from Shenzhen Forward Video, are configured with the MT213x part too. 


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

Re: [linux-dvb] [PATCH] Add syntek corp device to au0828

[Michael Krufky]

On Fri, Oct 17, 2008 at 8:57 AM, Mark Kimsal <mark@metrofindings.com> wrote:
> On Thursday 16 October 2008 11:11:39 am you wrote:
>> I thought this stick had an MT2130 inside -- looks like you've got
>> another revision with a TDA18271... very interesting :-)
>>
>> You say that ATSC works -- does it work on more than just one channel?
>>  If ATSC works, then QAM should work as well.  NTSC is not yet
>> supported in the Linux driver.
>>
>> Can you show me the dmesg output when the driver loads?  Also, can you
>> give me the exact name of the device (from the retail package) ?
>
> Yes, more than one channel works.  I do see the module TDA18721 loaded along
> with a couple other.  Again, I'm not 100% sure that this is the woodbury, but
> it works.  I can scan channels, I've watched 4-5 stations.  It seems to
> kernel oops every once in a while on very static-y stations.

It's definitely not a "woodbury", but if the woodbury configuration is
working for you, then it could be similar.

The really strange thing is that I have a device in my hand with usb
ID 05e1:0400 .  I opened it up, and there is an mt2130 and an au8502.

This is _not_ a tda18271c2 and an au8522.  So, the fact that the
tda18271c2 + au8522 driver combination is working for you tells us
that multiple configurations are out there that all have the same usb
ID.

or, by some strange chance, the my2130 in your stick might be tuned to
some default frequency that just happens to have channels.

I asked you if you were able to receive multiple channels -- are they
all on the same frequency, or are they on different frequencies?

Would it be possible for you to open up the device and take some
hi-res digital photos?

> I just upgraded to 2.6.27 and it doesn't work anymore.  Modprobing au0828 does
> not load up any other modules like the tda18721 and does not create
> a /dev/dvb folder.  This is a problem with the latest hg tip of v4l-dvb.


I will have to take a look into this -- I haven't tested 2.6.27
enough, myself.  If there is a problem, then we'll have to fix it for
the 2.6.27.y stable series.

> dmesg from 2.6.27 (not working):
> usb 1-2: new high speed USB device using ehci_hcd and address 2
> 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
> usbcore: registered new interface driver au0828
> usbcore: registered new interface driver snd-usb-audio
>
> dmesg from 2.6.24 (working):
> usb 1-2: new high speed USB device using ehci_hcd and address 3
> usb 1-2: configuration #1 chosen from 1 choice
> au0828: i2c bus registered
> tveeprom 1-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 1-0060: creating new instance
> TDA18271HD/C2 detected @ 1-0060
> DVB: registering new adapter (au0828)
> DVB: registering frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
> Registered device AU0828 [Hauppauge Woodbury]
>
>
> As per my other email (sabrent/auvitek unknown usb device) I'm not entirely
> sure of the brand name.  The Web store lists it as "sabrent".  lsusb says
> it's "syntek", but Windows and the device manager says it's an "auvitek".
> The box has literally no brand name.  The only "brand" looking things are
> just acronyms like NTSC and ATSC.  The windows .inf file for the driver is
> littered with the words "auvitek international", "copyright auvitek" and the
> like....
>
> Although I didn't buy the device, the first brand name that I identified would
> be "auvitek".  Sabrent was only found after back tracking to the the retailer
> and seeing the product page.  I don't think that "Syntek" is the proper
> coporation for the usb vendor ID of 05e1.

Auvitek is the chip manufacturer.  Lets go with the name "Syntek" for
now.  I've seen this in retail packaging using the name, "Syntek
Teledongle" ...

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

Re: [linux-dvb] [PATCH] Add syntek corp device to au0828

[Mark Kimsal]

On Saturday 08 November 08, Michael Krufky wrote:
> On Fri, Oct 17, 2008 at 8:57 AM, Mark Kimsal <mark@metrofindings.com> wrote:
> > On Thursday 16 October 2008 11:11:39 am you wrote:
> >> I thought this stick had an MT2130 inside -- looks like you've got
> >> another revision with a TDA18271... very interesting :-)
> >>
> >> You say that ATSC works -- does it work on more than just one channel?
> >>  If ATSC works, then QAM should work as well.  NTSC is not yet
> >> supported in the Linux driver.
> >>
> >> Can you show me the dmesg output when the driver loads?  Also, can you
> >> give me the exact name of the device (from the retail package) ?
> >
> > Yes, more than one channel works.  I do see the module TDA18721 loaded
> > along with a couple other.  Again, I'm not 100% sure that this is the
> > woodbury, but it works.  I can scan channels, I've watched 4-5 stations. 
> > It seems to kernel oops every once in a while on very static-y stations.
>
> It's definitely not a "woodbury", but if the woodbury configuration is
> working for you, then it could be similar.
>
> The really strange thing is that I have a device in my hand with usb
> ID 05e1:0400 .  I opened it up, and there is an mt2130 and an au8502.
>
> This is _not_ a tda18271c2 and an au8522.  So, the fact that the
> tda18271c2 + au8522 driver combination is working for you tells us
> that multiple configurations are out there that all have the same usb
> ID.
>
> or, by some strange chance, the my2130 in your stick might be tuned to
> some default frequency that just happens to have channels.
>
> I asked you if you were able to receive multiple channels -- are they
> all on the same frequency, or are they on different frequencies?

I don't think they're all on the same frequency.  I'm not 100% sure of the 
terminology, but I ran scandvb and it locked on to about 6 local broadcast 
channels.  I'm fairly certain that they are different frequencies, but I 
don't have the channels conf file in front of my to say for certain.  How 
likely is it that 6 channels from 3 different broadcast corps would be on the 
same "frequency"?

> Would it be possible for you to open up the device and take some
> hi-res digital photos?

I've tried and tried.  I'm afraid it's going to break if I tear at the case 
anymore.  It's not mine and the vendor's Website doesn't list it for sale 
anymore :(

UPDATE: Okay, one bloody fingernail later... it's open.  I'll send pics when I 
can get them.  But right away I see:

 1 NXP Chip: TDA 18271HDC2
 1 Auvitek Chip: AU8522AA
 1 Auvitek Chip: AU0828A


> > I just upgraded to 2.6.27 and it doesn't work anymore.  Modprobing au0828
> > does not load up any other modules like the tda18721 and does not create
> > a /dev/dvb folder.  This is a problem with the latest hg tip of v4l-dvb.
>
> I will have to take a look into this -- I haven't tested 2.6.27
> enough, myself.  If there is a problem, then we'll have to fix it for
> the 2.6.27.y stable series.

This is a problem with the install scripts, not with 2.6.27.
My distro has gzipped modules so the 'make install' command did not overwrite 
the default mod.ko.gz.  'make rmmod' or whatever the specific make target is 
in this project removes both the mod.ko files and the mod.ko.gz files.  So, 
uninstalling then installing works.  Nothing to do with 2.6.27.


> Auvitek is the chip manufacturer.  Lets go with the name "Syntek" for
> now.  I've seen this in retail packaging using the name, "Syntek
> Teledongle" ...



-- 
***************************************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues.

Mark Kimsal
http://biz.metrofindings.com/
fax: 866-375-1590

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

Re: [linux-dvb] [PATCH] Add syntek corp device to au0828

[Mark Kimsal]

On Saturday 08 November 08, Michael Krufky wrote:
> On Fri, Oct 17, 2008 at 8:57 AM, Mark Kimsal <mark@metrofindings.com> wrote:
> > On Thursday 16 October 2008 11:11:39 am you wrote:
> >> I thought this stick had an MT2130 inside -- looks like you've got
> >> another revision with a TDA18271... very interesting :-)
> >>
> It's definitely not a "woodbury", but if the woodbury configuration is
> working for you, then it could be similar.
>
> The really strange thing is that I have a device in my hand with usb
> ID 05e1:0400 .  I opened it up, and there is an mt2130 and an au8502.
>
> This is _not_ a tda18271c2 and an au8522.  So, the fact that the
> tda18271c2 + au8522 driver combination is working for you tells us
> that multiple configurations are out there that all have the same usb
> ID.
> Would it be possible for you to open up the device and take some
> hi-res digital photos?

I have updated the wiki with a hi-res photo.  I can e-mail an even higher 
resolution image off-list if it is required.  Contact my directly for shots 
of the back of the device (nothing interesting), my stock photos are twice as 
large as what's on the wiki.

http://linuxtv.org/wiki/index.php/Sabrent_TV-USBHD

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