From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Lorenzo Marcantonio <l.marcantonio@logossrl.com>,
linux-media@vger.kernel.org
Subject: Re: strange empia device
Date: Sun, 31 Aug 2014 16:50:08 +0200 [thread overview]
Message-ID: <54033620.4000105@googlemail.com> (raw)
In-Reply-To: <5403358C.4070504@googlemail.com>
Am 31.08.2014 um 16:47 schrieb Frank Schäfer:
> Hi Lorenzo,
>
> Am 25.08.2014 um 21:01 schrieb Lorenzo Marcantonio:
>> Just bought a roxio video capture dongle. Read around that it was an
>> easycap clone (supported, then); it seems it's not so anymore :(
>>
>> It identifies as 1b80:e31d Roxio Video Capture USB
>>
>> (it also uses audio class for audio)
>>
>> Now comes the funny thing. Inside there is the usual E2P memory,
>> a regulator or two and an empia marked EM2980 (*not* em2890!); some
>> passive and nothing else.
>>
>> Digging around in the driver cab (emBDA.inf) shows that it seems an
>> em28285 driver rebranded by roxio... it installs emBDAA.sys and
>> emOEMA.sys (pretty big: about 1.5MB combined!); also a 16KB merlinFW.rom
>> (presumably a firmware for the em chip? I tought they were fixed
>> function); also the usual directshow .ax filter and some exe in
>> autorun (emmona.exe: firmware/setup loader?).
>>
>> Looking in the em28xx gave me the idea that that thing is not
>> supported (at least in my current 3.6.6)... however the empia sites says
>> (here http://www.empiatech.com/wp/video-grabber-em282xx/) 28284 should
>> be linux supported. Nothing said about 28285. And the chip is marked
>> 2980?! by the way, forcing the driver to load I get this:
>>
>> [ 3439.787701] em28xx: New device Roxio Video Capture USB @ 480 Mbps (1b80:e31d, interface 0, class 0)
>> [ 3439.787704] em28xx: Video interface 0 found
>> [ 3439.787705] em28xx: DVB interface 0 found
>> [ 3439.787866] em28xx #0: em28xx chip ID = 146
>>
>> Is there any hope to make it work (even on git kernel there is nothing
>> for chip id 146...)?
>>
> See http://www.spinics.net/lists/linux-media/msg73699.html
>
> HTH,
> Frank
Hmm... could you send us the output of "lsusb -v -d 1b80:e31d ?
Thanks,
Frank
next prev parent reply other threads:[~2014-08-31 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 19:01 strange empia device Lorenzo Marcantonio
2014-08-31 14:47 ` Frank Schäfer
2014-08-31 14:50 ` Frank Schäfer [this message]
2014-08-31 15:41 ` Lorenzo Marcantonio
2014-09-01 18:14 ` Frank Schäfer
2014-09-01 19:03 ` Lorenzo Marcantonio
2014-09-01 20:29 ` Frank Schäfer
2014-09-01 23:58 ` Andy Walls
2014-09-02 6:28 ` Lorenzo Marcantonio
2014-09-02 11:43 ` Andy Walls
2014-09-02 16:22 ` Frank Schäfer
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=54033620.4000105@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=l.marcantonio@logossrl.com \
--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 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).