linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans Petter Selasky <hps@bitfrost.no>
Cc: Ulf <mopp@gmx.net>, linux-media@vger.kernel.org
Subject: Re: Hauppauge HVR-900 HD and HVR 930C-HD with si2165
Date: Sun, 18 Aug 2013 15:15:30 +0300	[thread overview]
Message-ID: <5210BAE2.6010007@iki.fi> (raw)
In-Reply-To: <5210B5F3.4040607@bitfrost.no>

On 08/18/2013 02:54 PM, Hans Petter Selasky wrote:
> On 08/17/13 13:53, Antti Palosaari wrote:
>> On 08/17/2013 02:30 PM, Ulf wrote:
>>> Hi,
>>>
>>> I know the topic Hauppauge HVR-900 HD and HVR 930C-HD with si2165
>>> demodulator was already discussed
>>> http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/40982
>>>
>>> and
>>> http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/46266.
>>>
>>>
>>> Just for me as a confirmation nobody plans to work on a driver for
>>> si2165.
>>> Is there any chance how to push the development?
>>
>> comment mode
>> http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/46266
>>
>>
>>
>> As far as I know there is none working with si2165 Linux driver.
>>
>> Last week I dumped out simple sniff from initial tuning to DVB-T channel
>> and parsed log - it was 1.1 MB after parsing - wow. I haven't analyzed
>> if it yet, but if it appears it is si2165 which generates that much
>> control I/O it could be big task to write driver.
>>
>> Anyone has the idea if that amount of USB I/O traffic is caused by
>> cx231xx ?
>>
>> regards
>> Antti
>>
>
> Hi,
>
> FYI: The Si2168 driver is available from "dvbsky-linux-3.9-hps-v2.diff"
> inside. Maybe the Si2165 is similar?
>
> http://www.selasky.org/hans_petter/distfiles/webcamd-3.10.0.7.tar.bz2

It is DVB-S driver. HVR-900 is DVB-T and DVB-C.

regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2013-08-18 12:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 11:30 Hauppauge HVR-900 HD and HVR 930C-HD with si2165 Ulf
2013-08-17 11:53 ` Antti Palosaari
2013-08-18 11:54   ` Hans Petter Selasky
2013-08-18 12:15     ` Antti Palosaari [this message]
2013-08-18 19:02     ` Steven Toth
2013-08-19 19:47       ` Hans Petter Selasky
2013-08-19 20:09         ` Antti Palosaari
2013-08-19 22:43         ` Konstantin Dimitrov
2013-08-20  6:46           ` Hans Petter Selasky
2013-08-20  8:26           ` nibble.max
2013-08-20  8:43             ` Hans Petter Selasky
     [not found] ` <52426BB0.60809@gentoo.org>
     [not found]   ` <52444AA3.8020205@iki.fi>
2013-10-01  5:34     ` Matthias Schwarzott
2013-10-01 14:45       ` Antti Palosaari
2013-10-07 19:30         ` Matthias Schwarzott
2013-10-07 20:16           ` Antti Palosaari
2013-10-16  4:50             ` Matthias Schwarzott
2013-10-16 10:21               ` Antti Palosaari
2013-10-07 20:21           ` pierigno
2013-10-15 18:52             ` Matthias Schwarzott
  -- strict thread matches above, loose matches on Subject: below --
2013-08-18 15:00 Ulf
2013-08-18 15:23 ` Hans Petter Selasky
2013-08-18 15:26 ` Antti Palosaari
2013-08-18 18:58 ` Steven Toth

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=5210BAE2.6010007@iki.fi \
    --to=crope@iki.fi \
    --cc=hps@bitfrost.no \
    --cc=linux-media@vger.kernel.org \
    --cc=mopp@gmx.net \
    /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).