Discussion:
Support for Empia 2980 video/audio capture chip set
Keith Lawson
11 years ago
Permalink
Hello,

I sent the following message to the linux-usb mailing list and they
suggested I try here.

I'm trying to get a "Dazzle Video Capture USB V1.0" video capture card
working on a Linux device but it doesn't look like the chip set is
supported yet. I believe this card is the next version of the Pinnacle
VC100 capture card that worked with the em28xx kernel module. The
hardware vendor that sold the card says that this device has an Empia
2980 chip set in it so I'm inquiring about support for that chip set.
I'm just wondering about the best approach for getting the new chip
supported in the kernel. Is this something the em28xx maintainers would
naturally address in time or can I assist in getting this into the
kernel?

Here's dmesg from the Debian box I'm working on:

[ 3198.920619] usb 3-1: new high-speed USB device number 5 usingxhci_hcd
[ 3198.939394] usb 3-1: New USB device found,
idVendor=1b80,idProduct=e60a
[ 3198.939399] usb 3-1: New USB device strings: Mfr=0,
Product=1,SerialNumber=2
[ 3198.939403] usb 3-1: Product: Dazzle Video Capture USB Audio Device
[ 3198.939405] usb 3-1: SerialNumber: 0

l440:~$ uname -a
Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.11-1 (2013-09-10) x86_64
GNU/Linux

If this isn't the appropriate list to ask this question please point me
in the right direction.

Thanks,
Keith
Frank Schäfer
11 years ago
Permalink
...
The em28xx is indeed the dedicated driver for this device, but it's hard
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it is just
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)

Regards,
Frank
Keith Lawson
11 years ago
Permalink
=20
Hello, I sent the following message to the linux-usb mailing list an=
d=20
they suggested I try here. I'm trying to get a "Dazzle Video Capture=
=20
USB V1.0" video capture card working on a Linux device but it doesn'=
t
look like the chip set is supported yet. I believe this card is the=20
next version of the Pinnacle VC100 capture card that worked with the=
=20
em28xx kernel module. The hardware vendor that sold the card says th=
at
this device has an Empia 2980 chip set in it so I'm inquiring about=20
support for that chip set. I'm just wondering about the best approac=
h=20
for getting the new chip supported in the kernel. Is this something=20
the
em28xx maintainers would naturally address in time or can I assist i=
n=20
getting this into the kernel? Here's dmesg from the Debian box I'm=20
working on: [ 3198.920619] usb 3-1: new high-speed USB device number=
5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,=20
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New USB dev=
ice=20
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] usb 3-=
1:=20
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNumber:=
0=20
...
What's the best route to get support for this chip added then? Should I=
=20
start working on a patch myself or will this just happen during the=20
course of development of the em28xx module? I'm a developer but haven't=
=20
done any kernel hacking so this would likely be a steep learning curve=20
for me.
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-media=
"=20
in
More majordomo info at http://vger.kernel.org/majordomo-info.html [1]
Links:
------
[1] http://vger.kernel.org/majordomo-info.html
Frank Schäfer
11 years ago
Permalink
Post by Keith Lawson
Hello, I sent the following message to the linux-usb mailing list
and they suggested I try here. I'm trying to get a "Dazzle Video
Capture USB V1.0" video capture card working on a Linux device but
it doesn't
look like the chip set is supported yet. I believe this card is the
next version of the Pinnacle VC100 capture card that worked with th=
e
Post by Keith Lawson
em28xx kernel module. The hardware vendor that sold the card says t=
hat
...
vice
Post by Keith Lawson
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] usb 3=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNumber=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.11-1
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate list to=
ask
Post by Keith Lawson
this question please point me in the right direction. Thanks, Keith
The em28xx is indeed the dedicated driver for this device, but it's =
hard
Post by Keith Lawson
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it is =
just
Post by Keith Lawson
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? Should
I start working on a patch myself or will this just happen during the
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the output
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.

Regards,
=46rank
Keith Lawson
11 years ago
Permalink
Hello, I sent the following message to the linux-usb mailing list
and they suggested I try here. I'm trying to get a "Dazzle Video
Capture USB V1.0" video capture card working on a Linux device bu=
t
it doesn't
look like the chip set is supported yet. I believe this card is t=
he
next version of the Pinnacle VC100 capture card that worked with =
the
em28xx kernel module. The hardware vendor that sold the card says=
that
this device has an Empia 2980 chip set in it so I'm inquiring abo=
ut
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is thi=
s
something the
em28xx maintainers would naturally address in time or can I assis=
t
in getting this into the kernel? Here's dmesg from the Debian box
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB device
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New USB =
device
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] usb=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNumb=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.11-=
1
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate list =
to ask
this question please point me in the right direction. Thanks, Kei=
th
The em28xx is indeed the dedicated driver for this device, but it'=
s hard
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it i=
s just
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? Shou=
ld
I start working on a patch myself or will this just happen during t=
he
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
=20
Can you create USB-Traces of the Windows driver and send us the outpu=
t
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
=46or the USB-trace will the Win7 logman output do or is there a Win7 6=
4-bit utility like usbsnoop I should use?

Here's the lsusb output:=20


Bus 001 Device 002: ID 1b80:e60a Afatech=20
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0=20
bDeviceProtocol 0=20
bMaxPacketSize0 64
idVendor 0x1b80 Afatech
idProduct 0xe60a=20
bcdDevice 1.00
iManufacturer 0=20
iProduct 1=20
iSerial 2=20
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 406
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0=20
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 2
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0ad0 2x 720 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 3
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0c00 2x 1024 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 4
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1300 3x 768 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 5
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1380 3x 896 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 6
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x13c0 3x 960 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 0
bAlternateSetting 7
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0=20
bInterfaceProtocol 255=20
iInterface 0=20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 1024 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03ac 1x 940 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8a EP 10 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 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0=20
iInterface 0=20
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 40
bInCollection 1
baInterfaceNr( 0) 2
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0603 Line Connector
bAssocTerminal 0
bNrChannels 2
wChannelConfig 0x0000
iChannelNames 0=20
iTerminal 0=20
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 2
bSourceID 1
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
bmaControls( 2) 0x00
iFeature 0=20
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 2
iTerminal 0=20
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0=20
iInterface 0=20
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0=20
iInterface 0=20
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 3
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 48000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x00c4 1x 196 bytes
bInterval 4
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
=20
Regards,
Frank
=20
Frank Schäfer
11 years ago
Permalink
Hello, I sent the following message to the linux-usb mailing list
and they suggested I try here. I'm trying to get a "Dazzle Video
Capture USB V1.0" video capture card working on a Linux device bu=
t
it doesn't
look like the chip set is supported yet. I believe this card is t=
he
next version of the Pinnacle VC100 capture card that worked with =
the
em28xx kernel module. The hardware vendor that sold the card says=
that
this device has an Empia 2980 chip set in it so I'm inquiring abo=
ut
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is thi=
s
something the
em28xx maintainers would naturally address in time or can I assis=
t
in getting this into the kernel? Here's dmesg from the Debian box
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB device
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New USB =
device
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] usb=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNumb=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.11-=
1
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate list =
to ask
this question please point me in the right direction. Thanks, Kei=
th
The em28xx is indeed the dedicated driver for this device, but it'=
s hard
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it i=
s just
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? Shou=
ld
I start working on a patch myself or will this just happen during t=
he
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the outp=
ut
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a Win7 6=
4-bit utility like usbsnoop I should use?

AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win 7.
You may also want to try USBPcap (http://desowin.org/usbpcap/), but I=20
don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them are=20
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
=2E..
...
This endpoint configuration is different from the Empia devices we've=20
seen so far.
We have never seen any devices using endpoint address 0x8a and endpoint=
=20
0x84 looks strange.
It's hard to say what they are used for.
The current em28xx driver will assume 0x84 is used for DVB, but that=20
makes no sense for this device.

Regards,
=46rank
Keith Lawson
11 years ago
Permalink
Post by Frank Schäfer
Hello, I sent the following message to the linux-usb mailing lis=
t
Post by Frank Schäfer
and they suggested I try here. I'm trying to get a "Dazzle Video
Capture USB V1.0" video capture card working on a Linux device b=
ut
Post by Frank Schäfer
it doesn't
look like the chip set is supported yet. I believe this card is =
the
Post by Frank Schäfer
next version of the Pinnacle VC100 capture card that worked with=
the
Post by Frank Schäfer
em28xx kernel module. The hardware vendor that sold the card say=
s that
Post by Frank Schäfer
this device has an Empia 2980 chip set in it so I'm inquiring ab=
out
Post by Frank Schäfer
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is th=
is
Post by Frank Schäfer
something the
em28xx maintainers would naturally address in time or can I assi=
st
Post by Frank Schäfer
in getting this into the kernel? Here's dmesg from the Debian bo=
x
Post by Frank Schäfer
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB devic=
e
Post by Frank Schäfer
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New USB=
device
Post by Frank Schäfer
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] us=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNum=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.11=
-1
Post by Frank Schäfer
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate list=
to ask
Post by Frank Schäfer
this question please point me in the right direction. Thanks, Ke=
ith
Post by Frank Schäfer
The em28xx is indeed the dedicated driver for this device, but it=
's hard
Post by Frank Schäfer
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it =
is just
Post by Frank Schäfer
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? Sho=
uld
Post by Frank Schäfer
I start working on a patch myself or will this just happen during =
the
Post by Frank Schäfer
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the out=
put
Post by Frank Schäfer
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a Win7 =
64-bit utility like usbsnoop I should use?
Post by Frank Schäfer
=20
AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win 7.
You may also want to try USBPcap (http://desowin.org/usbpcap/), but
I don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them are
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
Thanks for the pointer. I used USBPcap and exported text out of wiresha=
rk.=20

Here's the capture of connecting the device:=20

https://www.libertas-tech.com/dazzle_usb_connect.txt

Here's a capture of the device recording a 1 minute video. This one is =
almost 700 meg so you probably don't want to try and open it in a brows=
er:=20

https://www.libertas-tech.com/dazzle_recording_video.txt=20

I can arrange to get one of these devices in the hands of a developer i=
f that would help too.=20
...
" in
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
Frank Schäfer
11 years ago
Permalink
Post by Frank Schäfer
Hello, I sent the following message to the linux-usb mailing li=
st
Post by Frank Schäfer
and they suggested I try here. I'm trying to get a "Dazzle Vide=
o
Post by Frank Schäfer
Capture USB V1.0" video capture card working on a Linux device =
but
Post by Frank Schäfer
it doesn't
look like the chip set is supported yet. I believe this card is=
the
Post by Frank Schäfer
next version of the Pinnacle VC100 capture card that worked wit=
h the
Post by Frank Schäfer
em28xx kernel module. The hardware vendor that sold the card sa=
ys that
Post by Frank Schäfer
this device has an Empia 2980 chip set in it so I'm inquiring a=
bout
Post by Frank Schäfer
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is t=
his
Post by Frank Schäfer
something the
em28xx maintainers would naturally address in time or can I ass=
ist
Post by Frank Schäfer
in getting this into the kernel? Here's dmesg from the Debian b=
ox
Post by Frank Schäfer
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB devi=
ce
Post by Frank Schäfer
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New US=
B device
Post by Frank Schäfer
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403] u=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: SerialNu=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10.1=
1-1
Post by Frank Schäfer
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate lis=
t to ask
Post by Frank Schäfer
this question please point me in the right direction. Thanks, K=
eith
Post by Frank Schäfer
The em28xx is indeed the dedicated driver for this device, but i=
t's hard
Post by Frank Schäfer
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory it=
is just
Post by Frank Schäfer
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? Sh=
ould
Post by Frank Schäfer
I start working on a patch myself or will this just happen during=
the
Post by Frank Schäfer
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the ou=
tput
Post by Frank Schäfer
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a Win7=
64-bit utility like usbsnoop I should use?
Post by Frank Schäfer
AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win 7.
You may also want to try USBPcap (http://desowin.org/usbpcap/), but
I don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them are
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
Thanks for the pointer. I used USBPcap and exported text out of wires=
hark.=20
Here's the capture of connecting the device:=20
https://www.libertas-tech.com/dazzle_usb_connect.txt
Here's a capture of the device recording a 1 minute video. This one i=
s almost 700 meg so you probably don't want to try and open it in a bro=
wser:=20
https://www.libertas-tech.com/dazzle_recording_video.txt=20
I can arrange to get one of these devices in the hands of a developer=
if that would help too.=20
Sorry for the delay, I'm currently burried under lots other stuff...
I haven't finished evaluating these logs yet, but so far I can say that
there's a lot of known stuff but also much new/unknown stuff.
Which capturing settings (resolution, video format, ...) did you use fo=
r
these logs ?
Does the device consist of any other chips (AC97, demodulator, ...) ?

Regards,
=46rank
...
a" in
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
Keith Lawson
11 years ago
Permalink
Post by Frank Schäfer
=20
Post by Frank Schäfer
Hello, I sent the following message to the linux-usb mailing =
list
Post by Frank Schäfer
Post by Frank Schäfer
and they suggested I try here. I'm trying to get a "Dazzle Vi=
deo
Post by Frank Schäfer
Post by Frank Schäfer
Capture USB V1.0" video capture card working on a Linux devic=
e but
Post by Frank Schäfer
Post by Frank Schäfer
it doesn't
look like the chip set is supported yet. I believe this card =
is the
Post by Frank Schäfer
Post by Frank Schäfer
next version of the Pinnacle VC100 capture card that worked w=
ith the
Post by Frank Schäfer
Post by Frank Schäfer
em28xx kernel module. The hardware vendor that sold the card =
says that
Post by Frank Schäfer
Post by Frank Schäfer
this device has an Empia 2980 chip set in it so I'm inquiring=
about
Post by Frank Schäfer
Post by Frank Schäfer
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is=
this
Post by Frank Schäfer
Post by Frank Schäfer
something the
em28xx maintainers would naturally address in time or can I a=
ssist
Post by Frank Schäfer
Post by Frank Schäfer
in getting this into the kernel? Here's dmesg from the Debian=
box
Post by Frank Schäfer
Post by Frank Schäfer
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB de=
vice
Post by Frank Schäfer
Post by Frank Schäfer
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New =
USB device
Post by Frank Schäfer
Post by Frank Schäfer
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403]=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: Serial=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10=
=2E11-1
Post by Frank Schäfer
Post by Frank Schäfer
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate l=
ist to ask
Post by Frank Schäfer
Post by Frank Schäfer
this question please point me in the right direction. Thanks,=
Keith
Post by Frank Schäfer
Post by Frank Schäfer
The em28xx is indeed the dedicated driver for this device, but=
it's hard
Post by Frank Schäfer
Post by Frank Schäfer
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory =
it is just
Post by Frank Schäfer
Post by Frank Schäfer
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? =
Should
Post by Frank Schäfer
Post by Frank Schäfer
I start working on a patch myself or will this just happen duri=
ng the
Post by Frank Schäfer
Post by Frank Schäfer
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the =
output
Post by Frank Schäfer
Post by Frank Schäfer
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a Wi=
n7 64-bit utility like usbsnoop I should use?
Post by Frank Schäfer
Post by Frank Schäfer
AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win 7.
You may also want to try USBPcap (http://desowin.org/usbpcap/), bu=
t
Post by Frank Schäfer
Post by Frank Schäfer
I don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them ar=
e
Post by Frank Schäfer
Post by Frank Schäfer
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
Thanks for the pointer. I used USBPcap and exported text out of wir=
eshark.=20
Post by Frank Schäfer
Here's the capture of connecting the device:=20
https://www.libertas-tech.com/dazzle_usb_connect.txt
Here's a capture of the device recording a 1 minute video. This one=
is almost 700 meg so you probably don't want to try and open it in a b=
rowser:=20
Post by Frank Schäfer
https://www.libertas-tech.com/dazzle_recording_video.txt=20
I can arrange to get one of these devices in the hands of a develop=
er if that would help too.=20
Post by Frank Schäfer
Sorry for the delay, I'm currently burried under lots other stuff...
No worries. I know that feeling all too well.=20
Post by Frank Schäfer
I haven't finished evaluating these logs yet, but so far I can say th=
at
Post by Frank Schäfer
there's a lot of known stuff but also much new/unknown stuff.
Which capturing settings (resolution, video format, ...) did you use =
for
Post by Frank Schäfer
these logs ?
Someone else did the capture for me since I didn't have a Windows box i=
t would work on. He had it connected to a video camera but didn't have =
an audio connection so there's no sound.

Here's the settings from the Pinnical software.

The properties of the video are:

Codec IPB MPEG-2 ***@ML 4:2:0
Bitrate 8000 kBit/s
Duration 00:00:05.10
Color Depth 16 Bit
=46rame Aspect 4:3
Alpha No
Dimensions 720 x 480 px
Pixel Aspect 0.89
=46ramestart 0
=46rames 29.97 FPS
Interlacing Top Field First

The properties of the audio are:
Codec MP2
Bitrate 224kBit/s
Duration 00:00:5.17
Sample Rate 48 kHz
Channels Stereo
Resolution 16 Bit
Sample Type Stereo
=46ormat PCM

When I click on 'Import' there aren't a tone of settings:

Dazzle Video Capture is set to 'Video Composite', 4:3, and NTSC

Mode is set to 'Scene detection ON'
Post by Frank Schäfer
Does the device consist of any other chips (AC97, demodulator, ...) ?
=20
Not that I see. There's a couple smaller chips on the device. I uploade=
d pictures here:=20

Failed to load image: https://www.libertas-tech.com//dazzle1.jpg
Failed to load image: https://www.libertas-tech.com//dazzle2.jpg
...
at
Post by Frank Schäfer
Post by Frank Schäfer
makes no sense for this device.
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-me=
dia" in
Post by Frank Schäfer
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
=20
--
To unsubscribe from this list: send the line "unsubscribe linux-media=
" in
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
Frank Schäfer
11 years ago
Permalink
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
Hello, I sent the following message to the linux-usb mailing =
list
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
and they suggested I try here. I'm trying to get a "Dazzle Vi=
deo
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
Capture USB V1.0" video capture card working on a Linux devic=
e but
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
it doesn't
look like the chip set is supported yet. I believe this card =
is the
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
next version of the Pinnacle VC100 capture card that worked w=
ith the
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
em28xx kernel module. The hardware vendor that sold the card =
says that
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
this device has an Empia 2980 chip set in it so I'm inquiring=
about
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
support for that chip set. I'm just wondering about the best
approach for getting the new chip supported in the kernel. Is=
this
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
something the
em28xx maintainers would naturally address in time or can I a=
ssist
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
in getting this into the kernel? Here's dmesg from the Debian=
box
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB de=
vice
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: New =
USB device
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.939403]=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: Serial=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.10=
=2E11-1
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate l=
ist to ask
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
this question please point me in the right direction. Thanks,=
Keith
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
The em28xx is indeed the dedicated driver for this device, but=
it's hard
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
to say how much work would be necessary to add support for it.
We currently don't support any em29xx chip yet, but in theory =
it is just
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
an extended em28xx device.
Whatever that means when it comes to the low level stuff... ;)
What's the best route to get support for this chip added then? =
Should
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
I start working on a patch myself or will this just happen duri=
ng the
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
course of development of the em28xx module? I'm a developer but
haven't done any kernel hacking so this would likely be a steep
learning curve for me.
Can you create USB-Traces of the Windows driver and send us the =
output
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a Wi=
n7 64-bit utility like usbsnoop I should use?
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win 7.
You may also want to try USBPcap (http://desowin.org/usbpcap/), bu=
t
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
I don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them ar=
e
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
Thanks for the pointer. I used USBPcap and exported text out of wir=
eshark.=20
Post by Keith Lawson
Post by Frank Schäfer
Here's the capture of connecting the device:=20
https://www.libertas-tech.com/dazzle_usb_connect.txt
Here's a capture of the device recording a 1 minute video. This one=
is almost 700 meg so you probably don't want to try and open it in a b=
rowser:=20
Post by Keith Lawson
Post by Frank Schäfer
https://www.libertas-tech.com/dazzle_recording_video.txt=20
I can arrange to get one of these devices in the hands of a develop=
er if that would help too.=20
Post by Keith Lawson
Post by Frank Schäfer
Sorry for the delay, I'm currently burried under lots other stuff...
No worries. I know that feeling all too well.=20
Post by Frank Schäfer
I haven't finished evaluating these logs yet, but so far I can say t=
hat
Post by Keith Lawson
Post by Frank Schäfer
there's a lot of known stuff but also much new/unknown stuff.
Which capturing settings (resolution, video format, ...) did you use=
for
Post by Keith Lawson
Post by Frank Schäfer
these logs ?
Someone else did the capture for me since I didn't have a Windows box=
it would work on. He had it connected to a video camera but didn't hav=
e an audio connection so there's no sound.
Post by Keith Lawson
Here's the settings from the Pinnical software.
Bitrate 8000 kBit/s
Duration 00:00:05.10
Color Depth 16 Bit
Frame Aspect 4:3
Alpha No
Dimensions 720 x 480 px
Pixel Aspect 0.89
Framestart 0
Frames 29.97 FPS
Interlacing Top Field First
Hmm... looking at the logs, I would have expected 720x240 + YUV422...
Post by Keith Lawson
Codec MP2
Bitrate 224kBit/s
Duration 00:00:5.17
Sample Rate 48 kHz
Channels Stereo
Resolution 16 Bit
Sample Type Stereo
Format PCM
Dazzle Video Capture is set to 'Video Composite', 4:3, and NTSC
Mode is set to 'Scene detection ON'
Post by Frank Schäfer
Does the device consist of any other chips (AC97, demodulator, ...) =
?
Post by Keith Lawson
Not that I see. There's a couple smaller chips on the device. I uploa=
ded pictures here:=20
Post by Keith Lawson
https://www.libertas-tech.com//dazzle1.jpg
https://www.libertas-tech.com//dazzle2.jpg
Ok, thanks, I suspected that. :/
It seems like the em298x has a built-in demodulator (and likely also an
audio codec).
I can see lots of reads/writes to a "special" address in the log.


Ok, here is a summary of what needs to be done to support this device
and what is already more or less in place:

Should work out of the box or can be made work with minor changes:
1.) chip type detection (can be added easily with a small patch)
2.) eeprom access
3.) i2c bus access
4.) capturing configuration and start/stop (bridge part)
5.) frame processing (seems to be at least very similar to the one used
by the other em27xx/em28xx, I can see the same header type)
6.) audio part

ToDo:
1.) figure out the meaning of the USB endpoints and extend the current
logic to handle them properly
2.) add support for the built-in demodulator (an access routine is easy
to add, but the registers meaning/setup is completely unknown)
3.) figure out the meaning of some new/unknown bridge registers (0x2e,
0x38, 0x44, 0x4f, 0xb0-0xb8), xclk (reg 0x0f) is set to an unknown freq=
uency

1.) and 3.) could probably be achieved with a good piece of reverse
engineering work and some dirty hacks.
But 2.) is hardly possible without the datasheet of the em298x. :(

Any chance to get access to the datasheet ? :-)

Regards,
=46rank
...
at
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
makes no sense for this device.
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-me=
dia" in
Post by Keith Lawson
Post by Frank Schäfer
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-medi=
a" in
Post by Keith Lawson
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
Keith Lawson
11 years ago
Permalink
Post by Frank Schäfer
=20
Post by Keith Lawson
Post by Frank Schäfer
On Wed, Jan 15, 2014 at 10:37:44PM +0100, Frank Sch=E4fer wrote=
Hello, I sent the following message to the linux-usb mailin=
g list
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
and they suggested I try here. I'm trying to get a "Dazzle =
Video
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
Capture USB V1.0" video capture card working on a Linux dev=
ice but
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
it doesn't
look like the chip set is supported yet. I believe this car=
d is the
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
next version of the Pinnacle VC100 capture card that worked=
with the
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
em28xx kernel module. The hardware vendor that sold the car=
d says that
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
this device has an Empia 2980 chip set in it so I'm inquiri=
ng about
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
support for that chip set. I'm just wondering about the bes=
t
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
approach for getting the new chip supported in the kernel. =
Is this
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
something the
em28xx maintainers would naturally address in time or can I=
assist
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
in getting this into the kernel? Here's dmesg from the Debi=
an box
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
I'm working on: [ 3198.920619] usb 3-1: new high-speed USB =
device
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
number 5
usingxhci_hcd [ 3198.939394] usb 3-1: New USB device found,
idVendor=3D1b80,idProduct=3De60a [ 3198.939399] usb 3-1: Ne=
w USB device
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
strings: Mfr=3D0, Product=3D1,SerialNumber=3D2 [ 3198.93940=
Product: Dazzle
Video Capture USB Audio Device [ 3198.939405] usb 3-1: Seri=
0 l440:~$ uname -a Linux l440 3.10-3-amd64 #1 SMP Debian 3.=
10.11-1
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
(2013-09-10) x86_64 GNU/Linux If this isn't the appropriate=
list to ask
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
this question please point me in the right direction. Thank=
s, Keith
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
The em28xx is indeed the dedicated driver for this device, b=
ut it's hard
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
to say how much work would be necessary to add support for i=
t.
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
We currently don't support any em29xx chip yet, but in theor=
y it is just
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
an extended em28xx device.
Whatever that means when it comes to the low level stuff... =
;)
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
What's the best route to get support for this chip added then=
? Should
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
I start working on a patch myself or will this just happen du=
ring the
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
course of development of the em28xx module? I'm a developer b=
ut
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
haven't done any kernel hacking so this would likely be a ste=
ep
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
learning curve for me.
Can you create USB-Traces of the Windows driver and send us th=
e output
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
of "lsusb -v -d 1b80:e60a" for this device ?
That will give us a hint how much work will be needed.
For the USB-trace will the Win7 logman output do or is there a =
Win7 64-bit utility like usbsnoop I should use?
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
AFAIK the logman output doesn't contain any transferred data.
SniffUSB would be preferred, but AFAIK it doesn't work with Win =
7.
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
You may also want to try USBPcap (http://desowin.org/usbpcap/), =
but
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
I don't know if it runs on the 64bit version of Win 7.
There are also various commercial USB-Sniffers and some of them =
are
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
providing a free trial period/version.
In any case we need a readable (text) sniffing output.
Thanks for the pointer. I used USBPcap and exported text out of w=
ireshark.=20
Post by Frank Schäfer
Post by Keith Lawson
Here's the capture of connecting the device:=20
https://www.libertas-tech.com/dazzle_usb_connect.txt
Here's a capture of the device recording a 1 minute video. This o=
ne is almost 700 meg so you probably don't want to try and open it in a=
browser:=20
Post by Frank Schäfer
Post by Keith Lawson
https://www.libertas-tech.com/dazzle_recording_video.txt=20
I can arrange to get one of these devices in the hands of a devel=
oper if that would help too.=20
Post by Frank Schäfer
Post by Keith Lawson
Sorry for the delay, I'm currently burried under lots other stuff.=
=2E.
Post by Frank Schäfer
Post by Keith Lawson
No worries. I know that feeling all too well.=20
I haven't finished evaluating these logs yet, but so far I can say=
that
Post by Frank Schäfer
Post by Keith Lawson
there's a lot of known stuff but also much new/unknown stuff.
Which capturing settings (resolution, video format, ...) did you u=
se for
Post by Frank Schäfer
Post by Keith Lawson
these logs ?
Someone else did the capture for me since I didn't have a Windows b=
ox it would work on. He had it connected to a video camera but didn't h=
ave an audio connection so there's no sound.
...
) ?
Post by Frank Schäfer
Post by Keith Lawson
Not that I see. There's a couple smaller chips on the device. I upl=
oaded pictures here:=20
Post by Frank Schäfer
Post by Keith Lawson
https://www.libertas-tech.com//dazzle1.jpg
https://www.libertas-tech.com//dazzle2.jpg
=20
Ok, thanks, I suspected that. :/
It seems like the em298x has a built-in demodulator (and likely also =
an
Post by Frank Schäfer
audio codec).
I can see lots of reads/writes to a "special" address in the log.
=20
=20
Ok, here is a summary of what needs to be done to support this device
=20
1.) chip type detection (can be added easily with a small patch)
2.) eeprom access
3.) i2c bus access
4.) capturing configuration and start/stop (bridge part)
5.) frame processing (seems to be at least very similar to the one us=
ed
Post by Frank Schäfer
by the other em27xx/em28xx, I can see the same header type)
6.) audio part
=20
1.) figure out the meaning of the USB endpoints and extend the curren=
t
Post by Frank Schäfer
logic to handle them properly
2.) add support for the built-in demodulator (an access routine is ea=
sy
Post by Frank Schäfer
to add, but the registers meaning/setup is completely unknown)
3.) figure out the meaning of some new/unknown bridge registers (0x2e=
,
Post by Frank Schäfer
0x38, 0x44, 0x4f, 0xb0-0xb8), xclk (reg 0x0f) is set to an unknown fr=
equency
Post by Frank Schäfer
=20
1.) and 3.) could probably be achieved with a good piece of reverse
engineering work and some dirty hacks.
But 2.) is hardly possible without the datasheet of the em298x. :(
=20
Any chance to get access to the datasheet ? :-)
Thanks for the detailed explanation. My client is following up with the=
ir hardware vendor to see if they can get a copy of the data sheet and =
I emailed the hardware manufacturer myself. We'll see if we get a respo=
nse.=20
...
that
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
makes no sense for this device.
Regards,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-=
media" in
Post by Frank Schäfer
Post by Keith Lawson
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.ht=
ml
Post by Frank Schäfer
Post by Keith Lawson
--
To unsubscribe from this list: send the line "unsubscribe linux-me=
dia" in
Post by Frank Schäfer
Post by Keith Lawson
More majordomo info at http://vger.kernel.org/majordomo-info.html
=20
--
To unsubscribe from this list: send the line "unsubscribe linux-media=
" in
Post by Frank Schäfer
More majordomo info at http://vger.kernel.org/majordomo-info.html
pepijn de vos
11 years ago
Permalink
Hey,

I signed up to this list because I found this thread in the archives when googling for a driver for my Dazzle. Unfortunately I can't reply to an email I did not get.

Like Keith Lawson I'm a developer with no kernel experience, although I have some experience with C and libusb. I'd be happy to help in any way possible.

If there are any Dutch linux-media developers we could do a little hackathon maybe?

Unrelated: How do people manage to not be ovewhelmed by such a high-volume list?

Cheers,
Pepijn de Vos
Loading...