Origin commit data
------------------
Branch: ni/coolstream
Commit: 9695798213
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: d6e1ec6a0e
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-25 (Sun, 25 Feb 2018)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 1a96881f98
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-02-18 (Sun, 18 Feb 2018)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 9d6055a3ea
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2018-01-28 (Sun, 28 Jan 2018)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
Origin commit data
------------------
Branch: ni/coolstream
Commit: 7e85889d7b
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-09-24 (Sun, 24 Sep 2017)
------------------
No further description and justification available within origin commit message!
------------------
This commit was generated by Migit
time_monotonic_ms values did wrap every ~24 days, leading to problems
in code that did not cope with that. Instead of fixing all places where
relative comparisons with time_monotonic_ms() are made, just use a
bigger datatype. Convert all users to the new type.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 99ff4857ff
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-09-23 (Sat, 23 Sep 2017)
------------------
This commit was generated by Migit
This reverts commit 59814b0731.
Not a locking problem, but a wrap issue with time_monotonic_ms()
Origin commit data
------------------
Branch: ni/coolstream
Commit: ad19e58032
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-09-23 (Sat, 23 Sep 2017)
------------------
This commit was generated by Migit
I suspect something is wrong with OpenThreads::ScopedLock, so I'm using
plain pthread_mutex_timedlock() instead now.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 50165b8be9
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-09-06 (Wed, 06 Sep 2017)
------------------
This commit was generated by Migit
This seems to help spurious deadlocks in the STI framebuffer blit code.
Not 100% sure why, butthis helps, but I have not seen lockups with this.
Origin commit data
------------------
Branch: ni/coolstream
Commit: 56c24f4031
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-08-19 (Sat, 19 Aug 2017)
------------------
This commit was generated by Migit
this should allow to use fb_pixel_t pointer arithmetics more often
instead of byte pointers
Origin commit data
------------------
Branch: ni/coolstream
Commit: a6fc59ad6c
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-02-15 (Wed, 15 Feb 2017)
------------------
This commit was generated by Migit
also add a generic helper class for other accelerated
framebuffer implementations
Origin commit data
------------------
Branch: ni/coolstream
Commit: e56fde4082
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2017-02-05 (Sun, 05 Feb 2017)
------------------
This commit was generated by Migit
