From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Lorenzo Marcantonio <l.marcantonio@logossrl.com>
Cc: linux-media@vger.kernel.org
Subject: Re: strange empia device
Date: Tue, 02 Sep 2014 18:22:34 +0200 [thread overview]
Message-ID: <5405EECA.6060801@googlemail.com> (raw)
In-Reply-To: <20140902062822.GA2805@aika.logos.lan>
Am 02.09.2014 um 08:28 schrieb Lorenzo Marcantonio:
> On Mon, Sep 01, 2014 at 07:58:52PM -0400, Andy Walls wrote:
>> A Merlin firmware of 16 kB strongly suggests that this chip has an
>> integarted Conexant CX25843 (Merlin Audio + Thresher Video = Mako)
>> Broadtcast A/V decoder core. The chip might only have a Merlin
>> integrated, but so far I've never encountered that. It will be easy
>> enough to tell, if the Thresher registers don't respond or only respond
>> with junk.
> However I strongly suspect that these drivers are for a whole *family*
> of empia device. The oem ini by roxio talks about three different
> parts... probably they give one sys file for everyone and the oem
> customizes the ini.
>
> In short the merlin fw may not be actually used for *this* part but only
> for other empia devices/configurations.
>
> Otherwise I wonder *why* a fscking 1.5MB of sys driver for a mostly dumb
> capture device...
Right. There is also no firmware upload in the USB-log I have checked.
Regards,
Frank
prev parent reply other threads:[~2014-09-02 16:21 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
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 [this message]
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=5405EECA.6060801@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).