From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: keith.lawson@libertas-tech.com
Cc: linux-media@vger.kernel.org, linux-media-owner@vger.kernel.org
Subject: Re: Support for Empia 2980 video/audio capture chip set
Date: Wed, 15 Jan 2014 22:37:44 +0100 [thread overview]
Message-ID: <52D6FFA8.8060008@googlemail.com> (raw)
In-Reply-To: <de907f83197624a31fc6690a43a21929@www.nowhere.ca>
Am 14.01.2014 01:48, schrieb Keith Lawson:
> On 2014-01-12 11:56, Frank Schäfer wrote:
>
>> On 09.01.2014 02:02, Keith Lawson wrote:
>>
>>> 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
>>
>>
>> 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... ;)
>>
>
> 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,
Frank
next prev parent reply other threads:[~2014-01-15 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 1:02 Support for Empia 2980 video/audio capture chip set Keith Lawson
2014-01-12 16:56 ` Frank Schäfer
2014-01-14 0:48 ` Keith Lawson
2014-01-15 21:37 ` Frank Schäfer [this message]
2014-01-17 0:11 ` Keith Lawson
2014-01-20 20:08 ` Frank Schäfer
2014-02-06 12:57 ` Keith Lawson
2014-02-24 17:38 ` Frank Schäfer
2014-02-27 1:47 ` Keith Lawson
2014-03-02 17:54 ` Frank Schäfer
2014-03-04 1:14 ` Keith Lawson
-- strict thread matches above, loose matches on Subject: below --
2014-02-09 10:34 pepijn de vos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D6FFA8.8060008@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=keith.lawson@libertas-tech.com \
--cc=linux-media-owner@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.