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 13:52:37 -0400 [thread overview]
Message-ID: <4AB3C8E5.4010700@kernellabs.com> (raw)
In-Reply-To: <4AB3C17D.1030300@gmail.com>
>>>> 2) Component input for the A/V-in
>>
>> Yes, this exists on the HVR2250 product only.
>
> Ah shite, are you sure?
> If you look at the specs for the reference card it was there, did they
> take it out at the last minute?
It's not feature Hauppauge supports on the HVR2200 today. I have a suspicion
this may change but I'm neither confirming, denying or announcing anything. It
would make sense to officially support component cables on the HVR2200 since the
silicon supports it. If/when it does I'm sure it will be mentioned in the forums
or on the HVR2200 product packaging.
>
>>>> 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.
>
> Why do you rule it out unequivocally, is it just because I've annoyed
> you? :-(
Raw analog TV isn't a high priority feature on my mental check-list. Analog TV
via the encoder is much more interesting and applicable to many people.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-09-18 17:52 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
2009-09-18 17:21 ` Jed
2009-09-18 17:52 ` Steven Toth [this message]
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=4AB3C8E5.4010700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox