public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jed <jedi.theone@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Hw capabilities of the HVR-2200
Date: Sat, 19 Sep 2009 02:24:26 +1000	[thread overview]
Message-ID: <4AB3B43A.2030103@gmail.com> (raw)
In-Reply-To: <4AAF568D.1070308@gmail.com>


> **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
>
>
[Follow-up post] *Delivery issues resolved, although there's still 
delays of 7hrs or more being investigated with postmasters*

Attention Kernellabs devs,
I've deliberately delayed these two posts as Steve mentioned he wouldn't 
have time to respond for at least 1wk.

It's now been almost two weeks, do you think you might have 5-minutes to 
spare now?
I realise you might not "know" the answer to some of my questions 
yet!...  :-D

All the best,
Jed

  parent reply	other threads:[~2009-09-18 16:23 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 [this message]
2009-09-18 16:45   ` Steven Toth
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=4AB3B43A.2030103@gmail.com \
    --to=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