cache manipulation outside locks is evil, and the variables have been
initialized in tuxtxt_init earlier anyway
Origin commit data
------------------
Commit: aab075bd70
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2016-01-02 (Sat, 02 Jan 2016)
This need buildfixes and some functional updates...
Origin commit data
------------------
Commit: eeee5bacab
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2015-12-13 (Sun, 13 Dec 2015)
the CRCInput class is used for input anyway, so
this does not make any sense.
Origin commit data
------------------
Commit: e06e845eae
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2013-11-09 (Sat, 09 Nov 2013)
TODO: check if plugins etc. need extra treatment
Origin commit data
------------------
Commit: c68ffa2155
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2013-09-28 (Sat, 28 Sep 2013)
the code is unmaintained and probably non-functional, everyone
should use libstb-hal instead
Origin commit data
------------------
Commit: d2d8218885
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2013-03-06 (Wed, 06 Mar 2013)
when enabling tuxtxt caching, saving settings and then
starting tuxtxt, the start page was not initialized
Origin commit data
------------------
Commit: cb36c6e712
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-07-15 (Sun, 15 Jul 2012)
tuxtxt_cache_lock does not prevent from calling tuxtxt_clear_cache
while the cache thread is in the middle of inserting pages, thus
leading to a hard-to-reproduce crash when trying to start up tuxtxt.
The simplest fix is to use an additional "big hammer" lock arond
the whole critical area. Since tuxtxt_clear_cache is only called
very seldom, there should be no lock contention problem.
Origin commit data
------------------
Commit: 9af56e1852
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-07-15 (Sun, 15 Jul 2012)
this is very experimental and depends on more fixes in
libstb-hal, but audio / video / OSD are basically working
Origin commit data
------------------
Commit: 2541edc918
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-06-18 (Mon, 18 Jun 2012)
no, the CFrameBuffer::blit2FB() API is *not* intuitive
(transp == true means: no transparency...)
Origin commit data
------------------
Commit: 20f20c8511
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-04-04 (Wed, 04 Apr 2012)
* Use a separate framebuffer and backbuffer on SPARK (the framebuffer
is not big enough to have both buffers in it).
* make tuxtxt work correctly with scaling FB (1080 full-HD modes)
* improve performance by using the blitter to copy from back- to frame
buffer if available (spark)
Origin commit data
------------------
Commit: 99952cb9d7
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-03-11 (Sun, 11 Mar 2012)
Origin message was:
------------------
tuxtxt: fix display with scaling FB, use hw accel if available
* Use a separate framebuffer and backbuffer on SPARK (the framebuffer
is not big enough to have both buffers in it).
* make tuxtxt work correctly with scaling FB (1080 full-HD modes)
* improve performance by using the blitter to copy from back- to frame
buffer if available (spark)
In order to improve portability, libtriple will be split off and
built separately as "libneutrino-hal" (for hardware abstraction layer)
Enable the makefiles to deal with that.
Origin commit data
------------------
Commit: c8a561244e
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-02-03 (Fri, 03 Feb 2012)
With the new input device, no need for special casing in neutrino.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-beta@2052 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 0fa97c1652
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2012-01-09 (Mon, 09 Jan 2012)
tuxtxt does not need the config file, but it needs the *directory*
$(CONFIGDIR)/tuxtxt
Since tuxtxt is no longer standalone, moving the config into main
neutrino.conf would be better, but for now (and in order to not
invalidate all the docs) just create the directory during installation.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-beta@1862 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 3259f26dfe
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2011-11-18 (Fri, 18 Nov 2011)
Let the code use the same defaults as are in the config file,
so that installing the config file is no longer necessary.
This makes for easier packaging of neutrino.
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-beta@1829 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: e69a204e73
Author: Stefan Seyfried <seife@tuxbox-git.slipkontur.de>
Date: 2011-11-05 (Sat, 05 Nov 2011)
v4l support has been dropped in recent kernel versions and therefore <linux/videodev.h> is gone. If you want to compile with new kernel headers add -DNEW_CST_KERNEL to your neutrino CFLAGS
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-beta@1603 e54a6e83-5905-42d5-8d5c-058d10e6a962
Origin commit data
------------------
Commit: 09a496cdfa
Author: gixxpunk <thomas.harfmann@gmail.com>
Date: 2011-07-27 (Wed, 27 Jul 2011)
Origin message was:
------------------
- fix compile with kernel headers from new kernels (e.g. 2.6.39.3)
v4l support has been dropped in recent kernel versions and therefore <linux/videodev.h> is gone. If you want to compile with new kernel headers add -DNEW_CST_KERNEL to your neutrino CFLAGS
git-svn-id: file:///home/bas/coolstream_public_svn/THIRDPARTY/applications/neutrino-beta@1603 e54a6e83-5905-42d5-8d5c-058d10e6a962
