On 02/14/17 19:18, Jonathan Sims wrote:
> This is a code cleanup after recent changes introduced by commit
> a503ff812430e104f591287b512aa4e3a83f20b1.
>
> Signed-off-by: Jonathan Sims
> ---
>
> drivers/media/usb/hdpvr/hdpvr-video.c | 18 +++---
> 1
On 05/12/14 07:41, Hans Verkuil wrote:
Ryley, Keith, can you test this one more time and if it works reply with
a 'Tested-by' tag that I can add to the patch?
Thanks!
Hans
This issue was reported by Ryley Angus:
quote
I record from my satellite set top box using component video
. This works well, but obviously seeking isn't relevant.
ryley
-Original Message-
From: Keith Pyle [mailto:kp...@austin.rr.com]
Sent: Wednesday, April 09, 2014 12:28 AM
To: Ryley Angus; 'Hans Verkuil'; linux-media@vger.kernel.org
Subject: Re: [RFC] Fix interrupted recording with Hauppauge HD-PVR
On 04/07/14 22:32, Ryley Angus wrote:
Thanks Hans for getting back to me.
I've been trying out your patch and I found the device wasn't actually
restarting the streaming/recording properly after a channel
change. I changed msecs_to_jiffies(500)) to msecs_to_jiffies(1000)) and
had the same
On 04/08/14 12:07, Ryley Angus wrote:
Hi Kyle.
It may be possible that the delay in acceptable grace periods is due to a
difference in our input AV sources more so than the Hauppauge units
themselves. I'm wondering if it would be useful to control the timeout
period via a module parameter that
On 09/26/12 21:42, Keith Pyle wrote:
I recently purchased a Hauppauge HD-PVR (the 1212 version, label on
bottom 49001LF, Rev F2). I have consistent capture failures on Linux
where data from the device simply stops, generally within a few
minutes of starting a capture. Yet, the device works
On 10/13/12 14:17, David Röthlisberger wrote:
On Wed, 26 Sep 2012 21:42:32 -0500
Keith Pyle kp...@austin.rr.com wrote:
I recently purchased a Hauppauge HD-PVR (the 1212 version, label on
bottom 49001LF, Rev F2). I have consistent capture failures on Linux
where data from the device simply
I recently purchased a Hauppauge HD-PVR (the 1212 version, label on
bottom 49001LF, Rev F2). I have consistent capture failures on Linux
where data from the device simply stops, generally within a few minutes
of starting a capture. Yet, the device works flawlessly on Windows with
the same