On 05-12-2011 21:47, Devin Heitmueller wrote:
On Mon, Dec 5, 2011 at 6:32 PM, Eddi De Pierie...@depieri.net wrote:
Sorry, I think I applied follow patch on my tree while I developed
the driver trying to fix tuner initialization.
http://patchwork.linuxtv.org/patch/6617/
I forgot to remove
On 11-12-05 06:47 PM, Devin Heitmueller wrote:
On Mon, Dec 5, 2011 at 6:32 PM, Eddi De Pieri e...@depieri.net wrote:
Sorry, I think I applied follow patch on my tree while I developed
the driver trying to fix tuner initialization.
http://patchwork.linuxtv.org/patch/6617/
I forgot to remove
On 06-12-2011 10:51, Mark Lord wrote:
On 11-12-05 06:47 PM, Devin Heitmueller wrote:
On Mon, Dec 5, 2011 at 6:32 PM, Eddi De Pierie...@depieri.net wrote:
Sorry, I think I applied follow patch on my tree while I developed
the driver trying to fix tuner initialization.
On Tue, Dec 6, 2011 at 8:43 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
The driver who binds everything is the bridge driver. In your case, it is
the au0828 driver.
What you're experiencing seems to be some race issue inside it, and not at
xc5000.
On a quick look on it, I'm noticing
On 11-12-06 08:56 AM, Devin Heitmueller wrote:
On Tue, Dec 6, 2011 at 8:43 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
The driver who binds everything is the bridge driver. In your case, it is
the au0828 driver.
What you're experiencing seems to be some race issue inside it, and not
On Tue, Dec 6, 2011 at 10:28 AM, Mark Lord ker...@teksavvy.com wrote:
It's always exhibited races for me here. I have long since worked around
the issue(s), so my own systems currently behave. But with the newer
HVR-950Q revision (B4F0), the issue is far more prevalent than before.
I'll ask
On 06-12-2011 13:28, Mark Lord wrote:
On 11-12-06 08:56 AM, Devin Heitmueller wrote:
On Tue, Dec 6, 2011 at 8:43 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
The driver who binds everything is the bridge driver. In your case, it is
the au0828 driver.
What you're experiencing seems to
On Sun, Nov 20, 2011 at 9:56 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
diff --git a/drivers/media/common/tuners/xc5000.c
b/drivers/media/common/tuners/xc5000.c
index ecd1f95..048f489 100644
--- a/drivers/media/common/tuners/xc5000.c
+++ b/drivers/media/common/tuners/xc5000.c
@@
On 05-12-2011 16:23, Devin Heitmueller wrote:
On Sun, Nov 20, 2011 at 9:56 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
diff --git a/drivers/media/common/tuners/xc5000.c
b/drivers/media/common/tuners/xc5000.c
index ecd1f95..048f489 100644
--- a/drivers/media/common/tuners/xc5000.c
+++
On Mon, Dec 5, 2011 at 1:35 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
What's up with this change? Is this a bugfix for some race condition?
Why is it jammed into a patch for some particular product?
It seems like a change such as this could significantly change the
timing of tuner
On Mon, Dec 5, 2011 at 1:46 PM, Devin Heitmueller
dheitmuel...@kernellabs.com wrote:
On Mon, Dec 5, 2011 at 1:35 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
What's up with this change? Is this a bugfix for some race condition?
Why is it jammed into a patch for some particular
Sorry, I think I applied follow patch on my tree while I developed
the driver trying to fix tuner initialization.
http://patchwork.linuxtv.org/patch/6617/
I forgot to remove from my tree after I see that don't solve anything.
Regards
Eddi
On Mon, Dec 5, 2011 at 9:01 PM, Devin Heitmueller
On Mon, Dec 5, 2011 at 6:32 PM, Eddi De Pieri e...@depieri.net wrote:
Sorry, I think I applied follow patch on my tree while I developed
the driver trying to fix tuner initialization.
http://patchwork.linuxtv.org/patch/6617/
I forgot to remove from my tree after I see that don't solve
13 matches
Mail list logo
