From: Steven Toth <stoth@linuxtv.org>
To: David Engel <david@istwok.net>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] A couple HVR-1800 questions
Date: Mon, 16 Jun 2008 14:39:59 -0400 [thread overview]
Message-ID: <4856B37F.20704@linuxtv.org> (raw)
In-Reply-To: <20080615190958.GA6792@opus.istwok.net>
David Engel wrote:
> On Fri, Jun 13, 2008 at 01:16:08PM -0400, Steven Toth wrote:
>> David Engel wrote:
>>> First, what is the status of the analog capture capability? My search
>>> ...
>> The analog encoder is running with the tree form linuxtv.org. It has
>> some cleanup video ioctl2 rework going on by another dev here, but it's
>> functional as is. It's usable today.
>
> Thanks for the repsonse, Steven.
>
>>> Second, as far as I can tell, the hardware can perform simultaneous
>>> analog and digital captures. Is that correct and, if so, does/will
>>> the Linux driver support it?
>> Yes and yes.
>>
>> Typically the analog video devices are exposed as /dev/video0 (analog
>> preview) /dev/video1 (encoder output) and /dev/dvb/... for the digital
>> side.
>
> Excellent.
>
> Regarding the encoder and preview devices, that's different than the
> ivtv convention of using /dev/video(N) and and /dev/video(N+16). Is
> there a reason you did it differently and should it be standardized
> across drivers?
Hi david,
This is how the cx88 driver model works. Pfft, who needs standards ;)
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-06-16 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 16:39 [linux-dvb] A couple HVR-1800 questions David Engel
2008-06-13 17:16 ` Steven Toth
2008-06-15 19:09 ` David Engel
2008-06-16 18:39 ` Steven Toth [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=4856B37F.20704@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=david@istwok.net \
--cc=linux-dvb@linuxtv.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