linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Scheel <julian@jusst.de>
To: Andy Walls <awalls@md.metrocast.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Hauppauge HVR-2200 analog
Date: Tue, 14 Dec 2010 18:23:53 +0100	[thread overview]
Message-ID: <4D07A829.6080406@jusst.de> (raw)
In-Reply-To: <1291726869.2073.5.camel@morgan.silverblock.net>

Am 07.12.2010 14:01, schrieb Andy Walls:
> On Tue, 2010-12-07 at 12:04 +0100, Julian Scheel wrote:
>> Hi,
>>
>> is there any progress on adding analog support to the HVR-2200?
>> It seems support for the used chipsets in general is already in the kernel?
> It appears to be in the media_tree.git repository on the
> staging/for_v2.6.37-rc1 branch:
>
> http://git.linuxtv.org/media_tree.git?a=tree;f=drivers/media/video/saa7164;h=0acaa4ada45ae6881bfbb19447ae9db43f06ef9b;hb=staging/for_v2.6.37-rc1
>
> saa7164-cards.c appears to have analog entries added for HVR-2200's and
> saa7164-encoder.c has a number of V4L ioctl()'s for MPEG streams.
Is there any reason, why the additional card-information found here:
http://www.kernellabs.com/hg/~stoth/saa7164-dev/
is not yet in the kernel tree?


       reply	other threads:[~2010-12-14 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CFE14A1.3040801@jusst.de>
     [not found] ` <1291726869.2073.5.camel@morgan.silverblock.net>
2010-12-14 17:23   ` Julian Scheel [this message]
2010-12-14 18:41     ` Hauppauge HVR-2200 analog Julian Scheel
2010-12-14 19:51     ` Steven Toth
2010-12-15  7:04       ` Julian Scheel
2011-01-04  2:19         ` Julian Scheel
2011-01-06 22:31           ` Julian Scheel
2011-01-08 15:40             ` Julian Scheel
2011-02-01 13:22               ` Mauro Carvalho Chehab
2011-02-25  7:38                 ` Julian Scheel
2010-12-27 11:48       ` Julian Scheel

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=4D07A829.6080406@jusst.de \
    --to=julian@jusst.de \
    --cc=awalls@md.metrocast.net \
    --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;
as well as URLs for NNTP newsgroup(s).