All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Steffen Neumann <sneumann@ipb-halle.de>, linux-media@vger.kernel.org
Subject: Re: Hauppauge WinTV HVR 930C-HD - new USB ID 2040:b130 ?
Date: Wed, 08 May 2013 00:39:01 +0200	[thread overview]
Message-ID: <51898285.507@web.de> (raw)
In-Reply-To: <CAGoCfiza2FcrFETEeP_PdZvzdW0YuiKm4AP=wMTG465f9zBA9w@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2013-05-07 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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=51898285.507@web.de \
    --to=jan.kiszka@web.de \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sneumann@ipb-halle.de \
    /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.