From: Hans Verkuil <hverkuil@xs4all.nl>
To: Steve Cookson - IT <it@sca-uk.com>, linux-media@vger.kernel.org
Subject: Re: Hauppauge ImpactVCB-e 01385
Date: Fri, 11 Apr 2014 11:45:07 +0200 [thread overview]
Message-ID: <5347B9A3.2050301@xs4all.nl> (raw)
In-Reply-To: <5347B132.6040206@sca-uk.com>
On 04/11/2014 11:09 AM, Steve Cookson - IT wrote:
> So I'm back to the Hauppauge ImpactVCB-e 01385.
>
> Apparently it's fully supported by the current Linux kernel:
>
> Model Standard Interface Supported Comments
> ImpactVCB-e Video PCIe ✔ Yes No
> tuners, only video-in. S-Video Capture works with kernel 3.5.0 (Ubuntu
> 12.10).
>
> http://linuxtv.org/wiki/index.php/Hauppauge.
>
> So is this a typo or have I just encountered an install problem?
I have serious doubts whether this is actually supported. I see no mention of
that board in the cx23885 driver. I wonder if there is a mixup between the
ImpactVCB (which IS supported) and the ImpactVCB-e.
>
>> When I plug in my 01385 I get the same old stuff in dmseg, ie:
>>
>> cx23885 driver version 0.0.3 loaded
>> [ 8.921390] cx23885[0]: Your board isn't known (yet) to the driver.
>> [ 8.921390] cx23885[0]: Try to pick one of the existing card configs via
>> [ 8.921390] cx23885[0]: card=<n> insmod option. Updating to the latest
>> [ 8.921390] cx23885[0]: version might help as well.
>> [ 8.921393] cx23885[0]: Here is a list of valid choices for the
>> card=<n> insmod option:
You can try some of the existing cards: one of 1, 2, 3, 6, 20, 24, 32 might
just work. Look in drivers/media/pci/cx23885/cx23885-cards.c.
Each card definition there defines the inputs that are supported by the card.
There is no perfect match, so you will have to change inputs to see which
input produces an image. You can also add a card definition yourself and
just fiddle around with the vmux/amux/gpio values to see which work. It is
probably something close to what is used by other Hauppauge cards.
>>
>> Etc.
> Would the daily build resolve this? I haven't installed it on this test
> system, but I'm never clear when I should install it or whether I should
> just download a single driver from somewhere.
There is no point in using the daily build. The cx23885 driver hasn't been
updated in a long time.
Regards,
Hans
next prev parent reply other threads:[~2014-04-11 9:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 10:43 Hauppauge ImpactVCB-e 01385 Steve Cookson - IT
2014-04-10 14:49 ` Steven Toth
2014-04-11 9:09 ` Steve Cookson - IT
2014-04-11 9:45 ` Hans Verkuil [this message]
2014-04-11 10:03 ` Steve Cookson - IT
2014-04-11 10:35 ` Hans Verkuil
2014-04-11 12:18 ` Steve Cookson - IT
[not found] ` <5347E2AF.6030205@xs4all.nl>
[not found] ` <5347EB5D.2020408@sca-uk.com>
[not found] ` <5347EC3D.7040107@xs4all.nl>
[not found] ` <5348392E.40808@sca-uk.com>
[not found] ` <534BEA8A.2040604@xs4all.nl>
2014-04-15 16:45 ` Steve Cookson - IT
2014-04-15 17:13 ` Hans Verkuil
2014-04-15 17:30 ` Steve Cookson
2014-04-15 18:44 ` Steve Cookson
2014-04-15 20:07 ` Steve Cookson
2014-04-16 9:58 ` Hans Verkuil
2014-04-16 13:14 ` Steve Cookson
2014-04-16 13:20 ` Hans Verkuil
2014-04-16 13:25 ` Devin Heitmueller
2014-04-16 16:56 ` Steve Cookson
2014-04-16 17:11 ` Steve Cookson
2014-04-16 17:34 ` Hans Verkuil
-- strict thread matches above, loose matches on Subject: below --
2014-04-10 15:27 Steve Cookson
2014-04-10 15:59 ` Steven Toth
2014-04-16 18:15 Steve Cookson
2014-04-17 9:18 ` Steve Cookson
2014-04-17 9:59 ` Hans Verkuil
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=5347B9A3.2050301@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=it@sca-uk.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