* Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
@ 2012-03-25 20:09 Steffen Neumann
2012-03-26 14:46 ` Devin Heitmueller
0 siblings, 1 reply; 9+ messages in thread
From: Steffen Neumann @ 2012-03-25 20:09 UTC (permalink / raw)
To: linux-media
Hi,
I am trying to get a Hauppauge WinTV HVR 930C-HD
to work under Ubuntu 12.04 with the vanilla 3.3 kernel from [1].
After (manually) loading the em28xx module,
there are no additional messages in kern.log,
only "registered new interface driver em28xx".
What is odd is that lsusb shows for this card "ID 2040:b130 Hauppauge",
while from [2] I think it should be [2040:1605],
see below for the full lsusb -v output. The card
was purchased this week.
Do I have a new revision of the 930C ?
I tried "modprobe em28xx card=81", but no change.
Did I miss anything else ?
Yours,
Steffen
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/video4linux/CARDLIST.em28xx;h=d99262dda533042b3c99c8b8b1a339b48389af50;hb=HEAD
Bus 001 Device 004: ID 2040:b130 Hauppauge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0xb130
bcdDevice 40.01
iManufacturer 1 Hauppauge
iProduct 2 Hauppauge Device
iSerial 3 4035358241
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 344
bNumInterfaces 7
bConfigurationValue 1
iConfiguration 4 Hauppauge Device
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 340mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 32 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0e EP 14 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 4
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 1
bInterfaceCount 6
bFunctionClass 255 Vendor Specific Class
bFunctionSubClass 255 Vendor Specific Subclass
bFunctionProtocol 255 Vendor Specific Protocol
iFunction 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 7 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8f EP 15 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 7
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 8 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 9 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 10 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0080 1x 128 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 3
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 11 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x013c 1x 316 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 4
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 12 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x02c8 1x 712 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 5
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 13 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0ac8 2x 712 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 20 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 21 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 22 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0034 1x 52 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 23 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 24 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x00b8 1x 184 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 25 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x02d8 1x 728 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 3
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 26 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x13c4 3x 964 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 4
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 27 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0b84 2x 900 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 5
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 28 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 5
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 31 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 6
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 29 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 6
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 30 Hauppauge Device
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0240 1x 576 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
--
IPB Halle AG Massenspektrometrie & Bioinformatik
Dr. Steffen Neumann http://www.IPB-Halle.DE
Weinberg 3 http://msbi.bic-gh.de
06120 Halle Tel. +49 (0) 345 5582 - 1470
+49 (0) 345 5582 - 0
sneumann(at)IPB-Halle.DE Fax. +49 (0) 345 5582 - 1409
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
[not found] <assp.44329f40f0.1332772017.28771.12.camel@paddy.ipb-sub.ipb-halle.de>
@ 2012-03-26 14:40 ` Ezequiel García
0 siblings, 0 replies; 9+ messages in thread
From: Ezequiel García @ 2012-03-26 14:40 UTC (permalink / raw)
To: Steffen Neumann; +Cc: linux-media
Hi,
2012/3/26 Steffen Neumann <sneumann@ipb-halle.de>:
> sorry for bothering you directly, but I saw that
No problem.
> you kinda work on em288xx. I asked yesterday on linux-media
True about "kinda", I don't own any em28xx devices :)
> about my problems with the em28xx based 930C
> on a 3.3 vanilla kernel.
Yes, I saw the mail. I think indeed you have a device
that is not supported (yet?) by em28xx.
If lsusb says 2040:b130 rather than 2040:1605 then
I guess it's a new kind of device, different chipset,
I'm not sure (not an expert, sorry).
>
> Is this this the correct list to ask,
> and I just need to have more patience ?
> Or should I bring the issue up somewhere else ?
Not sure wherelse you can post your question.
Just wait for a while and ping again in a few weeks,
or so. I believe we are in the middle of a merge window
so developers are a little busy right now.
Hope it helps!
Ezequiel.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2012-03-25 20:09 Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ? Steffen Neumann
@ 2012-03-26 14:46 ` Devin Heitmueller
2012-03-26 14:49 ` Devin Heitmueller
2012-03-26 16:46 ` Neumann, Steffen
0 siblings, 2 replies; 9+ messages in thread
From: Devin Heitmueller @ 2012-03-26 14:46 UTC (permalink / raw)
To: Steffen Neumann; +Cc: linux-media
On Sun, Mar 25, 2012 at 4:09 PM, Steffen Neumann <sneumann@ipb-halle.de> wrote:
> Hi,
>
> I am trying to get a Hauppauge WinTV HVR 930C-HD
> to work under Ubuntu 12.04 with the vanilla 3.3 kernel from [1].
> After (manually) loading the em28xx module,
> there are no additional messages in kern.log,
> only "registered new interface driver em28xx".
>
> What is odd is that lsusb shows for this card "ID 2040:b130 Hauppauge",
> while from [2] I think it should be [2040:1605],
> see below for the full lsusb -v output. The card
> was purchased this week.
>
> Do I have a new revision of the 930C ?
> I tried "modprobe em28xx card=81", but no change.
> Did I miss anything else ?
2040:b130 isn't an em28xx based device. It uses cx231xx. That said,
it's not supported under Linux not because of the cx231xx driver but
because there is no driver for the demodulator (si2163).
Nobody is working on such a driver, and there is no support planned
for this device at this time.
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2012-03-26 14:46 ` Devin Heitmueller
@ 2012-03-26 14:49 ` Devin Heitmueller
2013-05-07 22:39 ` Jan Kiszka
2012-03-26 16:46 ` Neumann, Steffen
1 sibling, 1 reply; 9+ messages in thread
From: Devin Heitmueller @ 2012-03-26 14:49 UTC (permalink / raw)
To: Steffen Neumann; +Cc: linux-media
On Mon, Mar 26, 2012 at 10:46 AM, Devin Heitmueller
<dheitmueller@kernellabs.com> wrote:
> 2040:b130 isn't an em28xx based device. It uses cx231xx. That said,
> it's not supported under Linux not because of the cx231xx driver but
> because there is no driver for the demodulator (si2163).
Correction: it's an si2165 (not 2163).
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2012-03-26 14:46 ` Devin Heitmueller
2012-03-26 14:49 ` Devin Heitmueller
@ 2012-03-26 16:46 ` Neumann, Steffen
2012-03-26 17:09 ` Ezequiel García
1 sibling, 1 reply; 9+ messages in thread
From: Neumann, Steffen @ 2012-03-26 16:46 UTC (permalink / raw)
To: Devin Heitmueller; +Cc: linux-media@vger.kernel.org
Hi,
Not the answer I was looking for,
But thanks everybody for the clarification.
I'll try to register for the wiki and add
That information.
Yours, Steffen
Devin Heitmueller <dheitmueller@kernellabs.com> schrieb:
On Sun, Mar 25, 2012 at 4:09 PM, Steffen Neumann <sneumann@ipb-halle.de> wrote:
> Hi,
>
> I am trying to get a Hauppauge WinTV HVR 930C-HD
> to work under Ubuntu 12.04 with the vanilla 3.3 kernel from [1].
> After (manually) loading the em28xx module,
> there are no additional messages in kern.log,
> only "registered new interface driver em28xx".
>
> What is odd is that lsusb shows for this card "ID 2040:b130 Hauppauge",
> while from [2] I think it should be [2040:1605],
> see below for the full lsusb -v output. The card
> was purchased this week.
>
> Do I have a new revision of the 930C ?
> I tried "modprobe em28xx card=81", but no change.
> Did I miss anything else ?
2040:b130 isn't an em28xx based device. It uses cx231xx. That said,
it's not supported under Linux not because of the cx231xx driver but
because there is no driver for the demodulator (si2163).
Nobody is working on such a driver, and there is no support planned
for this device at this time.
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2012-03-26 16:46 ` Neumann, Steffen
@ 2012-03-26 17:09 ` Ezequiel García
0 siblings, 0 replies; 9+ messages in thread
From: Ezequiel García @ 2012-03-26 17:09 UTC (permalink / raw)
To: Neumann, Steffen; +Cc: Devin Heitmueller, linux-media@vger.kernel.org
On 3/26/12, Neumann, Steffen <sneumann@ipb-halle.de> wrote:
> Not the answer I was looking for,
> But thanks everybody for the clarification.
> I'll try to register for the wiki and add
I guess as a customer you could also contact the vendors
and ask to support the device. Can't hurt, right?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2012-03-26 14:49 ` Devin Heitmueller
@ 2013-05-07 22:39 ` Jan Kiszka
2013-05-08 3:29 ` Devin Heitmueller
0 siblings, 1 reply; 9+ messages in thread
From: Jan Kiszka @ 2013-05-07 22:39 UTC (permalink / raw)
To: Devin Heitmueller; +Cc: Steffen Neumann, linux-media
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
Hi there,
On 2012-03-26 16:49, Devin Heitmueller wrote:
> On Mon, Mar 26, 2012 at 10:46 AM, Devin Heitmueller
> <dheitmueller@kernellabs.com> wrote:
>> 2040:b130 isn't an em28xx based device. It uses cx231xx. That said,
>> it's not supported under Linux not because of the cx231xx driver but
>> because there is no driver for the demodulator (si2163).
>
> Correction: it's an si2165 (not 2163).
To pick up this old topic (as I just got the wrong 930C delivered :( ):
What is blocking the development of a si2165 driver? Lacking specs (due
to NDAs)? Or lacking interest / developer bandwidth? In case of the
latter, how much effort may it take for a kernel hacker without
particular experience in the DVB subsystem to get things running?
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2013-05-07 22:39 ` Jan Kiszka
@ 2013-05-08 3:29 ` Devin Heitmueller
2013-05-08 7:17 ` Jan Kiszka
0 siblings, 1 reply; 9+ messages in thread
From: Devin Heitmueller @ 2013-05-08 3:29 UTC (permalink / raw)
To: Jan Kiszka; +Cc: Steffen Neumann, Linux Media Mailing List
On Tue, May 7, 2013 at 6:39 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
> To pick up this old topic (as I just got the wrong 930C delivered :( ):
>
> What is blocking the development of a si2165 driver? Lacking specs (due
> to NDAs)? Or lacking interest / developer bandwidth?
Probably a bit of both. I've got the documentation under NDA, and
last I checked it's not otherwise publicly available. That said, the
chip has been around for several years and no developer has ever cared
to do a reverse engineered driver. The chip isn't overly complicated
(I could probably write a driver for it in a week even without the
datasheets), alas there has never really been any interest.
> In case of the
> latter, how much effort may it take for a kernel hacker without
> particular experience in the DVB subsystem to get things running?
Not rocket science, for sure. Probably the bigger issue is
familiarity with reverse engineering techniques and a good
understanding of how demodulators work. Learning the API itself is
the easy part (given there are plenty of example drivers to use as a
model).
I can count on one hand the number of developers who are actively
contributing tuner/demod drivers. There just is very little developer
interest in this area nowadays.
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
2013-05-08 3:29 ` Devin Heitmueller
@ 2013-05-08 7:17 ` Jan Kiszka
0 siblings, 0 replies; 9+ messages in thread
From: Jan Kiszka @ 2013-05-08 7:17 UTC (permalink / raw)
To: Devin Heitmueller; +Cc: Steffen Neumann, Linux Media Mailing List
[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]
On 2013-05-08 05:29, Devin Heitmueller wrote:
> On Tue, May 7, 2013 at 6:39 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> To pick up this old topic (as I just got the wrong 930C delivered :( ):
>>
>> What is blocking the development of a si2165 driver? Lacking specs (due
>> to NDAs)? Or lacking interest / developer bandwidth?
>
> Probably a bit of both. I've got the documentation under NDA, and
> last I checked it's not otherwise publicly available.
Does this NDA only prevent revealing the documentation itself or also
code that has been written using it? Could the vendor be motivated to
allow the latter?
> That said, the
> chip has been around for several years and no developer has ever cared
> to do a reverse engineered driver. The chip isn't overly complicated
> (I could probably write a driver for it in a week even without the
> datasheets), alas there has never really been any interest.
Well, the problem today is (if my recherche was correct) that there
aren't that many USB DVB-C adapters on the market with well working
mainline drivers. The old 930C used to be one of, if not the best. But
that version is not longer produced and now practically no longer
obtainable.
>
>> In case of the
>> latter, how much effort may it take for a kernel hacker without
>> particular experience in the DVB subsystem to get things running?
>
> Not rocket science, for sure. Probably the bigger issue is
> familiarity with reverse engineering techniques and a good
> understanding of how demodulators work. Learning the API itself is
> the easy part (given there are plenty of example drivers to use as a
> model).
>
> I can count on one hand the number of developers who are actively
> contributing tuner/demod drivers. There just is very little developer
> interest in this area nowadays.
I would know how to extract the USB communication between the device and
real or virtual machine running Windows and the Hauppauge software
stack. I may also find out which bits are missing during setup compared
to what a basic cx231xx setup [1] is doing, but then it gets hairy for
me as I definitely lack domain knowledge. Ah, and time is also an issue,
of course. ;)
You worked for Hauppauge in the past, right? Do you think they could be
motivated to support you working on this?
Thanks,
Jan
[1] http://forum.ubuntu-it.org/viewtopic.php?t=423395
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-05-08 7:17 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-25 20:09 Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ? Steffen Neumann
2012-03-26 14:46 ` Devin Heitmueller
2012-03-26 14:49 ` Devin Heitmueller
2013-05-07 22:39 ` Jan Kiszka
2013-05-08 3:29 ` Devin Heitmueller
2013-05-08 7:17 ` Jan Kiszka
2012-03-26 16:46 ` Neumann, Steffen
2012-03-26 17:09 ` Ezequiel García
[not found] <assp.44329f40f0.1332772017.28771.12.camel@paddy.ipb-sub.ipb-halle.de>
2012-03-26 14:40 ` Ezequiel García
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).