From: Steven Toth <stoth@kernellabs.com>
To: Jed <jedi.theone@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hw capabilities of the HVR-2200
Date: Fri, 18 Sep 2009 12:45:59 -0400 [thread overview]
Message-ID: <4AB3B947.1040202@kernellabs.com> (raw)
In-Reply-To: <4AB3B43A.2030103@gmail.com>
On 9/18/09 12:24 PM, Jed wrote:
>
>> **a repost because of earlier issues in getting emails to the list**
>>
>> Hi Kernellabs or anyone involved with driver development of the
>> HVR-2200...
Hello.
>>
>> I know this is a loooong way down the priority list of features to be
>> added, if ever!
>> But I'm wanting to know if the *possibility* is there 'hardware-wise'
>> for the following:
>>
>> 1) h.263/mpeg4/VC-1/DivX/Xvid hardware encode of A/V-in
Yes, this exists in hardware on the SAA7164 and therefore the HVR2200 and HVR2250.
>> 2) Component input for the A/V-in
Yes, this exists on the HVR2250 product only.
>> 3) Hw encode bypass for A/V-in
No idea. Regardless of whether it does or does not I wouldn't plan to add basic
raw TV support to the driver, without going through the encoder.
>> 4) Is Hw encode purely for A/V-in? (hauppauge's site suggests
>> otherwise but it may be a typo)
Yes.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-09-18 16:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 8:55 Hw capabilities of the HVR-2200 Jed
2009-09-16 17:23 ` Jed
2009-09-18 16:24 ` Jed
2009-09-18 16:45 ` Steven Toth [this message]
2009-09-18 17:21 ` Jed
2009-09-18 17:52 ` Steven Toth
2009-09-18 18:13 ` Jed
2009-09-18 18:26 ` Steven Toth
2009-09-19 5:37 ` Jed
2010-03-09 17:16 ` Jed
2010-03-11 15:38 ` Steven Toth
2010-03-11 16:46 ` Jed
2010-03-12 17:26 ` Jed
2010-03-12 17:39 ` Devin Heitmueller
2010-03-10 4:22 ` Jed
2009-09-18 16:24 ` Jed
2009-09-18 16:27 ` Jed
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=4AB3B947.1040202@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=jedi.theone@gmail.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 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.