On 20.05.2015 16:53, Michael Niedermayer wrote:
> On Wed, May 20, 2015 at 04:34:49PM +0200, Andreas Cadhalpun wrote:
>> nut.h|1 +
>> nutdec.c |5 -
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>> b32d36842ae472ac23d4445d35cee09c8a9adc46
>> 0001-nutdec-fix-infinite-resync-l
On Wed, May 20, 2015 at 04:34:49PM +0200, Andreas Cadhalpun wrote:
> On 20.05.2015 02:00, Michael Niedermayer wrote:
> > On Wed, May 20, 2015 at 12:49:49AM +0200, Andreas Cadhalpun wrote:
> >> nut->last_syncpoint_pos doesn't necessarily change between resync
> >> attempts, so find_any_startcode can
On Wed, May 20, 2015 at 04:34:49PM +0200, Andreas Cadhalpun wrote:
> On 20.05.2015 02:00, Michael Niedermayer wrote:
> > On Wed, May 20, 2015 at 12:49:49AM +0200, Andreas Cadhalpun wrote:
> >> nut->last_syncpoint_pos doesn't necessarily change between resync
> >> attempts, so find_any_startcode can
On 20.05.2015 02:00, Michael Niedermayer wrote:
> On Wed, May 20, 2015 at 12:49:49AM +0200, Andreas Cadhalpun wrote:
>> nut->last_syncpoint_pos doesn't necessarily change between resync
>> attempts, so find_any_startcode can return the same startcode again.
>>
>> Thus remember where the last resync
On Wed, May 20, 2015 at 12:49:49AM +0200, Andreas Cadhalpun wrote:
> nut->last_syncpoint_pos doesn't necessarily change between resync
> attempts, so find_any_startcode can return the same startcode again.
>
> Thus remember where the last resync happened and don't try to resync
> before that.
>
>
nut->last_syncpoint_pos doesn't necessarily change between resync
attempts, so find_any_startcode can return the same startcode again.
Thus remember where the last resync happened and don't try to resync
before that.
This can't be done locally in nut_read_packet, because this wouldn't
prevent inf
