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 12:35:39 +0200 [thread overview]
Message-ID: <5347C57B.7000207@xs4all.nl> (raw)
In-Reply-To: <5347BDDE.6080208@sca-uk.com>
On 04/11/2014 12:03 PM, Steve Cookson - IT wrote:
> Hi Hans,
>
> Thanks for this, I'll do as you suggested.
>
> On 11/04/14 10:45, Hans Verkuil wrote:
>> 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.
> Do you think there is another internal card out there that would do the
> job of capturing raw SD video?
>
> What would you recommend.
Actually, I would recommend that you try playing with the 'card=' option to
see if you can get something that works. I suspect that adding support for
this card isn't hard.
Alternatively, you can wait. I've ordered this card myself (it's about time I
start cleaning up the cx23885 driver, so some extra hardware to test with won't
hurt) so once I have it I'll work on adding support for it to the cx23885
driver. The problem is that it has to be ordered, so it may take some time
before it arrives.
There aren't all that many alternatives available for PCIe (PCI is easier). You
can look at the list of supported cards in cx23885-cards.c and see if you can
get any of those other cards.
Regards,
Hans
>
> I'm currently using the Dazzle DVC100, stripping the case off and
> installing it internally with cable ties. It's just a bit basic. I'd
> like something a bit more professional like a half-height PCIe board.
> Which is why I selected the ImpactVCB-e, but really I have no attachment
> to it.
>
> Regards
>
> Steve.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-04-11 10:36 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
2014-04-11 10:03 ` Steve Cookson - IT
2014-04-11 10:35 ` Hans Verkuil [this message]
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=5347C57B.7000207@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