>
> 041ad449683bb2d54a7f082d78ec15bbc958a175 introduced stats gathering
> into the dib7000p code which seems to generate a lot more i2c traffic which
> would exacerbate the problem, if one existed. The timing (May/June) very
> roughly matches what I remember too. When my recording stops, so do the
> >> Is that two tuners in the same device, or two tuners in different devices?
> >
> > DViCO FusionHDTV DVB-T Dual Express2
> >
> > 2 tuners on one card
>
> Any idea if there were changes or are issues with i2c access when there are
> two tuners in the same device?
>
> That's not really my expe
Mauro,
On 09/22/2014 11:58 AM, James Harper wrote:
>
> Any hints on what I can do to figure out what layer it's stalling at?
I have no idea. I would do a git bisect to try and narrow it down.
>>>
>>> Problem with the bisect is that I can't be sure what version it actually
>>
> >>>
> >>> Any hints on what I can do to figure out what layer it's stalling at?
> >>
> >> I have no idea. I would do a git bisect to try and narrow it down.
> >>
> >
> > Problem with the bisect is that I can't be sure what version it actually
> worked on. It certainly predates when my patch for m
On 09/22/2014 11:46 AM, James Harper wrote:
>>
>>>
>>> Any hints on what I can do to figure out what layer it's stalling at?
>>
>> I have no idea. I would do a git bisect to try and narrow it down.
>>
>
> Problem with the bisect is that I can't be sure what version it actually
> worked on. It cer
>
> >
> > Any hints on what I can do to figure out what layer it's stalling at?
>
> I have no idea. I would do a git bisect to try and narrow it down.
>
Problem with the bisect is that I can't be sure what version it actually worked
on. It certainly predates when my patch for my card was commi
On 09/22/2014 10:30 AM, James Harper wrote:
>>
>> I'll test out the downgrade to 73d8102298719863d54264f62521362487f84256
>> just to be sure, then see if I can take it further back.
>>
>
> 73d8102298719863d54264f62521362487f84256 still breaks for me, so it's
> definitely not related to the conver
>
> I'll test out the downgrade to 73d8102298719863d54264f62521362487f84256
> just to be sure, then see if I can take it further back.
>
73d8102298719863d54264f62521362487f84256 still breaks for me, so it's
definitely not related to the conversion.
Any hints on what I can do to figure out what
> >
> > And important for me, because if it IS related to the vb2 conversion then I
> > need to know asap.
> >
>
> Might take a few days to be completely sure. I've wondered if it's something
> to do with the signal too (maybe some bug when signal error occurs?). So
> many variables :(
>
I can r
> > That sounds plausible wrt timeframe, but if cx23885 only started using vb2
> > after Sept 8 then it couldn't have affected me before then right?
>
> You are right about that. You are using DVB right? Not analog video? (Just to
> be 100% certain).
>
Yes. Australia mostly has no analog anymore
> > I was looking through the patches and saw a date of August 14 on the
> > cx23885 to vb2 patch and thought that could have been around when it
> > started breaking, but then the
> > 73d8102298719863d54264f62521362487f84256 is dated September 3 and I'm
> > pretty sure it had started playing up be
On 09/20/2014 01:05 PM, James Harper wrote:
>>> I was looking through the patches and saw a date of August 14 on the
>>> cx23885 to vb2 patch and thought that could have been around when it
>>> started breaking, but then the
>>> 73d8102298719863d54264f62521362487f84256 is dated September 3 and I'm
On 09/20/2014 12:30 PM, James Harper wrote:
>>> Oops I should have mentioned that. I'm using Debian "Jessie" with
>>> 3.16 kernel and already using the latest v4l as per link you sent (my
>>> DViCO FusionHDTV DVB-T Dual Express2 patch is in 3.17 I think, but
>>> that's not in Debian yet).
>>
>> Ah,
> > Oops I should have mentioned that. I'm using Debian "Jessie" with
> > 3.16 kernel and already using the latest v4l as per link you sent (my
> > DViCO FusionHDTV DVB-T Dual Express2 patch is in 3.17 I think, but
> > that's not in Debian yet).
>
> Ah, yes, that's rather important information :-)
On 09/20/2014 11:26 AM, James Harper wrote:
>>
>> On 09/20/2014 05:32 AM, James Harper wrote:
>>>
>>> My cx23885 based DViCO FusionHDTV DVB-T Dual Express2 (I submitted a
>>> patch for this a little while ago) has been working great but over
>>> the last few months it has started playing up. Nothin
Em Sat, 20 Sep 2014 09:26:23 +
James Harper escreveu:
> >
> > On 09/20/2014 05:32 AM, James Harper wrote:
> > >
> > > My cx23885 based DViCO FusionHDTV DVB-T Dual Express2 (I submitted a
> > > patch for this a little while ago) has been working great but over
> > > the last few months it has
>
> On 09/20/2014 05:32 AM, James Harper wrote:
> >
> > My cx23885 based DViCO FusionHDTV DVB-T Dual Express2 (I submitted a
> > patch for this a little while ago) has been working great but over
> > the last few months it has started playing up. Nothing has really
> > changed that I can put my fi
On 09/20/2014 05:32 AM, James Harper wrote:
>
> My cx23885 based DViCO FusionHDTV DVB-T Dual Express2 (I submitted a
> patch for this a little while ago) has been working great but over
> the last few months it has started playing up. Nothing has really
> changed that I can put my finger on. Basic
18 matches
Mail list logo
