Hi,
> In OpenBricks it appears to have been reverted back to 3.6.
> I want the integrated hdhomerun thats in tvheadend since Nov/18/2014 and
> apparently included in 3.9.
> What was the reason for the revert?.
I don't know.
> If I use the current GeexBox-git with tvheadend 3.9 will it work?.
I don't think Tom reverted it just for fun. So it's pretty clear that
some problem exists. But I cannot tell if it's a build or a runtime
issue.
> Its for an RPi or A20 (cubieboard) if that matters.
Cubieboard is A10. A20 is used in Cubieboard2 and Cubietruck.
> Any suggestions appreciated.
The Cubieboards never worked as good as Raspberries or CuBoxes. There
are major issues with the (closed source) video decoder code (libve,
libcedarx) that the vendor refused to fix. There are several reverse
engineering attempts, but AFAIK none of them ever got to the point
of working in XBMC. For the latest and greatest look here:
http://linux-sunxi.org/Cedrus
https://github.com/linux-sunxi/libvdpau-sunxi
I have not tried to use VDPAU in XBMC because the readme says that
it's not feature complete enough. Therefore we got stuck with the
blobs.
About the blobs: AllWinner provided two sets. One with the A10 and
one with the A20. We had the A10 stuff working (with a known bug when
decoding certain MPEG4 files). There also was an attempt to use the
Android blobs in Linux via a project named 'hybris'. The libraries
needed for this are built in Geexbox as well and it's possible to
switch between the two approaches by changing a symlink. However,
at least for me this didn't fully work either. It played some files
that the 'native' lib did not, but failed with others...
There were high hopes that the second set of blobs would fix these
issues, but they were a big disappointment. First thing was, that
these new libs require a kernel driver for memory managment that
is not present in sunxi-3.4. The driver needs to be backported
from the original AllWinner 3.3 kernel. This has been done. Even
though it currently conflicts with CMA. The second is that the new
blobs don't come with a wrapper library as the old ones did. So
it's neccessary to create one that offers the same interface to
XBMC. This also has been done. However, initial tests failed and
I did not find the time and the mood to debug this further.
Maybe over the hollidays...
Just recently we tried the old blobs on A20 systems. Look here:
https://github.com/OpenBricks/openbricks/issues/38
At least on my Cubieboard2 they show another problem, which is
probably related to caching / DMA coherence. ISTR having read
something about this in the sunxi kernel mailing list...
> On a side note whats the status of (openbricks,geexbox) for the banana pi,
> I see that was a new addition, does it build/run?.
The BananaPi just uses another kernel config / u-boot config / fex file
than the other A20 systems. So it's expected to behave the same as
CubieBoard2 and CubieTruck. However, I'm not aware of anyone having
tried it.
If only the video issues on the A20 could be solved! These devices would
be very nice and it would be worth to look after the other problems (libcec,
multichannel audio). But in the current state they are pretty much unusable
as media center.
--
Ruediger "Rudi" Ihle