From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-media-owner@vger.kernel.org>
Received: from fg-out-1718.google.com ([72.14.220.153]:35240 "EHLO
	fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752473AbZIPRW3 (ORCPT
	<rfc822;linux-media@vger.kernel.org>);
	Wed, 16 Sep 2009 13:22:29 -0400
Received: by fg-out-1718.google.com with SMTP id 22so1251422fge.1
        for <linux-media@vger.kernel.org>; Wed, 16 Sep 2009 10:22:32 -0700 (PDT)
Message-ID: <4AB11EF6.3040106@gmail.com>
Date: Thu, 17 Sep 2009 03:23:02 +1000
From: Jed <jedi.theone@gmail.com>
MIME-Version: 1.0
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hw capabilities of the HVR-2200
References: <4AAF568D.1070308@gmail.com>
In-Reply-To: <4AAF568D.1070308@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-media-owner@vger.kernel.org
List-ID: <linux-media.vger.kernel.org>

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...
>
> 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
> 2) Component input for the A/V-in
> 3) Hw encode bypass for A/V-in
> 4) Is Hw encode purely for A/V-in? (hauppauge's site suggests 
> otherwise but it may be a typo)
> 5) If not then questions 1) & 3) also apply to RF-in!
>
> Here are the reference cards spec sheets again:
> http://www.picamatic.com/view/5094357_75016126_P1/
> http://www.picamatic.com/view/5094364_75016126_P2/
> http://www.picamatic.com/view/5094375_75016207_P1/
> http://www.picamatic.com/view/5094373_75016207_P2/
>
> I would be proactive in providing feed-back (as needed) for the dev. 
> of such features.
>
> Most Sincerely,
> Jed
>
>
Just a test feel free to ignore........