+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222)
+--- Forum: Feature Requests (https://forum.kodi.tv/forumdisplay.php?fid=9)
+--- Thread: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? (/showthread.php?tid=35139)
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - gpborges - 2012-04-17
(2012-04-17, 20:13)davilla Wrote: yes... but I'd have to...
You would have to...
:-) You got me curious...RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - holle - 2012-04-17
Is there some developer along who could help understanding why video on my EfikaMX/Freescale i.MX is jerky? It looks like people in any movie is jumping
To describe it in frames: If a clip is running at 10 fps it looks like one second you see 5 frame in a second and the other second it will display the remaining 15 frames at high speed. Any ideas?
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - slicemaster - 2012-04-27
Not sure how if this is news or not but I was just bumming around the pandaboard website and came across a library that allows for direct access to the IVA-HD hardware video engine. its called libdce and it would seem that it is opensource...something i found interesting considering most SoC vendors like to keep access to features like that locked down. Anyways just though i'd mention it and see if anybody had heard about it, or any other library for video decoding on omap.
cheers,
P.S. I also noticed that hardware decode and support for IVA-HD was/is on the XBMC road map...any status update on that? working code or work in progress? or neither...just curious.
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - OrcD3vil - 2012-05-14
I'm very interested in seeing if this will work the with Rasberry PI that is being offered to ship for $25/$35. As I currently run a WDTV Live hub and Love the setup my dad has at home using a Asus Box using XBMC, I would turn my QNap NAS Box into a Debian Box and then load XBMC that way but I almost lost all my movies, music, and files last time I tired that
SO I'm looking into the PI to run XBMC via HDMI to my TV any thoughts on if this will get ported to ARM?
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - Memphiz - 2012-05-15
sure https://github.com/xbmc/xbmc-rbp
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - speedway - 2012-05-20
Hi,
Just came across an USB dongle based on OMAP4:
http://www.youtube.com/watch?v=6uovbhcRv3Q&feature=youtube_gdata_player.
This looks like the 'perfect' match: small, no developers board = comes with enclosure/case, remote and powerful.
Since it is running the same chipset as the Pandaboard ES, I suppose (running ahead a little bit, since not yet available) XBMC will run on it?
This is a pure speculative question, only based on the specs
http://www.cnx-software.com/2012/01/10/always-innovating-unveils-open-source-android-4-0-hdmi-dongle-stb/
to allow dreaming :-)
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - McGeagh - 2012-05-24
There seems to be a lot of these dongle type designs coming out, such as cotton candy (based on GalaxySII SoC) or this cheap little thing:
http://www.engadget.com/2012/05/18/mk802-beats-cotton-candy-to-market/
RE: - tuxg - 2012-06-07
robclark, you mentioned below that implementing vaapi-egl in XBMC should not be a big change. The support doesn't seem to be in the upstream git tree yet. Is anyone already working on a patch?
I am basically trying to get XBMC+libva+OpenGL ES working. With XBMC vaapi only being supported on GLX, I am getting errors when building against OpenGL ES/EGL. Any input there will be helpful.
(2011-11-22, 17:48)robclark Wrote:RockerC Wrote:Would it not be best to try to utilize existing API standard for video acceleration like VAAPI or OpenMAX as much as possible?
In related news to this there is now a new VAAPI backend design that is primarily made for ARM devices. Haihao Xiang from Intel recently published a branch of VAAPI with a VA/EGL backend. This new vaapi-egl driver is a generic implementation for VAAPI with EGL and then there are backend drivers for Intel and PowerVR hardware support using an EGL display with OpenGL ES rather than GLX/OpenGL such as the normal VAAPI
http://lists.freedesktop.org/archives/libva/2011-November/000717.html
http://cgit.freedesktop.org/libva/log/?h=vaapi-egl
vaapi-egl could be interesting.. does XBMC support this already? I guess it shouldn't be too big a change. I'll look more closely at how rendering is handled in vaapi decode case..
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - jimi82 - 2012-08-09
Hi, i'm trying compile XBMC with PVR and Gstreamer (for Hardware acceleration) in the PandaBoard_ES. I use the configure options:
Code:
--enable-gles --disable-optical-drive --enable-vdpau --enable-neon --enable-gstreamer.I get the compile error:
Code:
RenderManager.cpp:787:40: error: no matching function for call to CLinuxRendererGLES::AddProcessor(CVDPAU*&)Any idea?
Thanks
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - Memphiz - 2012-08-09
VDPAU on a pandaboard? Are you sure this will work? AFAIK only nvidia cards support VDPAU.
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - jimi82 - 2012-08-09
(2012-08-09, 16:23)Memphiz Wrote: VDPAU on a pandaboard? Are you sure this will work? AFAIK only nvidia cards support VDPAU.
if i put nothing (neither --enable-vdpau or --disable-vdpau) by default vdpau is actived. If i put --disable-vdpau i get error compile:
Code:
In file included from JSONServiceDescription.cpp:28:0:
PlayerOperations.h:31:5: error: expected identifier before numeric constant
PlayerOperations.h:31:5: error: expected ‘}’ before numeric constant
PlayerOperations.h:31:5: error: expected unqualified-id before numeric constant
PlayerOperations.h:37:38: error: ‘Video’ was not declared in this scope
PlayerOperations.h:37:46: error: ‘Audio’ was not declared in this scope
PlayerOperations.h:37:54: error: ‘Picture’ was not declared in this scope
PlayerOperations.h:40:3: error: expected class-name before ‘{’ token
PlayerOperations.h:42:12: error: ‘JSON_STATUS’ does not name a type
In file included from JSONServiceDescription.cpp:28:0:
PlayerOperations.h:43:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:44:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:46:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:47:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:48:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:49:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:51:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:52:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:53:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:54:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:56:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:57:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:58:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:59:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:61:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:62:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:63:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:64:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:65:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:66:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:67:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:69:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:70:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:73:12: error: ‘PlayerType’ does not name a type
PlayerOperations.h:74:28: error: ‘PlayerType’ has not been declared
PlayerOperations.h:75:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:78:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:80:1: error: expected declaration before ‘}’ token
make[1]: *** [JSONServiceDescription.o] Error 1
make: *** [xbmc/interfaces/json-rpc/json-rpc.a] Error 2RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - pszab - 2012-08-10
Hi guys.
I'd like to inform about neon development.
Is there any limitation of its usage or everything can be solve with that?
What is the current status?
In my interpretation I thought it can be a default arm-xbmc solution but I can just see (on wikipedia) that neon will be used under android in 12.0
why not under linux also? I do not understand that.
As I see this can be a soc manufacturer independent solution. if neon is present xbmc could be work and not needed to wait 3rd party binary blobs, VPU drivers, etc.
Or am I wrong?
Thanks
RE: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - Memphiz - 2012-08-10
(2012-08-09, 16:58)jimi82 Wrote:(2012-08-09, 16:23)Memphiz Wrote: VDPAU on a pandaboard? Are you sure this will work? AFAIK only nvidia cards support VDPAU.
if i put nothing (neither --enable-vdpau or --disable-vdpau) by default vdpau is actived. If i put --disable-vdpau i get error compile:
Code:In file included from JSONServiceDescription.cpp:28:0:
PlayerOperations.h:31:5: error: expected identifier before numeric constant
PlayerOperations.h:31:5: error: expected ‘}’ before numeric constant
PlayerOperations.h:31:5: error: expected unqualified-id before numeric constant
PlayerOperations.h:37:38: error: ‘Video’ was not declared in this scope
PlayerOperations.h:37:46: error: ‘Audio’ was not declared in this scope
PlayerOperations.h:37:54: error: ‘Picture’ was not declared in this scope
PlayerOperations.h:40:3: error: expected class-name before ‘{’ token
PlayerOperations.h:42:12: error: ‘JSON_STATUS’ does not name a type
In file included from JSONServiceDescription.cpp:28:0:
PlayerOperations.h:43:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:44:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:46:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:47:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:48:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:49:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:51:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:52:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:53:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:54:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:56:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:57:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:58:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:59:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:61:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:62:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:63:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:64:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:65:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:66:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:67:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:69:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:70:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:73:12: error: ‘PlayerType’ does not name a type
PlayerOperations.h:74:28: error: ‘PlayerType’ has not been declared
PlayerOperations.h:75:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:78:12: error: ‘JSON_STATUS’ does not name a type
PlayerOperations.h:80:1: error: expected declaration before ‘}’ token
make[1]: *** [JSONServiceDescription.o] Error 1
make: *** [xbmc/interfaces/json-rpc/json-rpc.a] Error 2
You are using an outdated source tree. No support for that one.