From: Steven Saner <ssaner@hubris.net>
To: linux-media@vger.kernel.org
Subject: Re: wintv-hvr-1955 status
Date: Mon, 08 Dec 2014 14:53:11 -0600 [thread overview]
Message-ID: <54860FB7.40208@hubris.net> (raw)
In-Reply-To: <5480CE12.4040309@hubris.net>
It is certainly possible that I have not found the right place in which
to ask this question. If someone could direct me to the correct
person/forum, I would most appreciate it.
Thanks
Steve
On 12/04/2014 03:11 PM, Steven Saner wrote:
> Hi:
>
> I have a wintv-hvr-1955 (sold as a wintv-hvr-1950) from Hauppauge.
>
> I referenced a thread in this list in June 2014
>
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/78952/match=wintv+hvr+1955
>
> as well as this wiki page
>
> http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1950
>
> Both of the above suggest that a Linux driver for this device is
> available from Hauppauge after signing an NDA. So I contacted them on
> Nov 19 and they responded with the following message:
>
> ---
> A driver has been recently submitted to Linux TV and is awaiting
> approval. This process can take anywhere from 2 weeks to 3 months.
> ---
>
> I am wondering if this is true and if I can get a status of this or an
> ETA. Is there anything available that I can try? Will support for this
> device be included in the pvrusb2 driver (like the 1950) or in something
> else?
>
> Thanks for any information or suggestions.
>
> Steve
>
--
--------------------------------------------------------------------------
Steven Saner <ssaner@hubris.net> Voice: 316-858-3000
Director of Network Operations Fax: 316-858-3001
Hubris Communications http://www.hubris.net
prev parent reply other threads:[~2014-12-08 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:11 wintv-hvr-1955 status Steven Saner
2014-12-08 20:53 ` Steven Saner [this message]
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=54860FB7.40208@hubris.net \
--to=ssaner@hubris.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 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.