Kodi Community Forum
[LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? - Printable Version

+- 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)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48

- topfs2 - 2011-06-22

awesome, so they have fixed the dev packages. Was a while since I last compiled, will revisit now as it was a major pita to reinstall every time you compiled Smile

- tarzan23 - 2011-06-22

@christian667: How long did it take to compile xbmc trunk on the pandaboard? Compiling now... (on ubuntu 11.04 on the board itself, no cross compilation).

- christian667 - 2011-06-22

@tarzan23:
Oh it took about 4 hours for me i think, but i did it nearly everytime over night, so I'm not quite sure. Are you compiling the official git or the opdenkamp pvr-git?

- tarzan23 - 2011-06-22

I'm using the official git. I'll try to setup my server for cross compiling for the pandaboard, 8x X5570 > omap 4430 Smile.

@topfs2: first of all thank you for the great work you are doing Smile . regarding hardware acceleration, is the gstreamer backend (https://github.com/topfs2/xbmc/commits/gstreamer) useable, and are you planning on hooking up gst-ducati/libdce and your xbmc gstreamer backend?

- christian667 - 2011-06-22

@topfs2:
Do you have visualizations in case of music playing?
Doesn't matter which visualization method I select, nothing is displayed.. :confused2:

- topfs2 - 2011-06-22

@tarzan23
ideally anything able to accelerate gstreamer (totem for example) should work in there. However the current design in dvdp makes it really hard, if not impossible, to make this possible in mainline. Thr gstreamer branch i have is just a teat. It works on h264 for me on desktop but haven't tried on panda, in theory it should work.

@christian667
vissualizers uses standard gl so they won't work until ported.

- Robotica - 2011-06-23

tarzan23 Wrote:I'm using the official git. I'll try to setup my server for cross compiling for the pandaboard, 8x X5570 > omap 4430 Smile.

@topfs2: first of all thank you for the great work you are doing Smile . regarding hardware acceleration, is the gstreamer backend (https://github.com/topfs2/xbmc/commits/gstreamer) useable, and are you planning on hooking up gst-ducati/libdce and your xbmc gstreamer backend?


There is some work done to get XBMC running using gstreamer. See this: http://www.madeo.co.uk/?p=783 But it is on Meego.

- tarzan23 - 2011-06-23

Thanks for the info! I'll provide feedback as soon as i got xbmc up, currently i'm moving my root fs to a usb harddisk hoping for better performance (all sd cards i tried seem to perform quite poor).

- tarzan23 - 2011-06-23

Compiled nicely with:

Code:
--enable-gles --disable-vdpau --disable-optical-drive --enable-ccache --enable-nfs

Unfortunatly the binary segfaults:

Code:
tarzan@panda:/usr/local/lib/xbmc$ gdb ./xbmc.bin
GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/lib/xbmc/xbmc.bin...done.
(gdb) run
Starting program: /usr/local/lib/xbmc/xbmc.bin
[Thread debugging using libthread_db enabled]
params.c:OpenConfFile() - Unable to open configuration file "/home/tarzan/.smb/smb.conf":
    No such file or directory
[New Thread 0x4677b400 (LWP 3173)]
[Thread 0x4677b400 (LWP 3173) exited]
PVR:(Warning): InitContext: ignoring buffer type CBUF_TYPE_PDS_VERT_SECONDARY_PREGEN_BUFFER [777, /eglglue.c]
PVR:(Warning): InitContext: ignoring buffer type CBUF_TYPE_PDS_VERT_SECONDARY_PREGEN_BUFFER [777, /eglglue.c]

Program received signal SIGSEGV, Segmentation fault.
0x0037f4d2 in Matrix4Mul (this=0x20030010, matrix=0xbeffeca0)
    at MatrixGLES.cpp:268
268        );

Edit: Christian667's fix to MatrixGLES.c solves this problem.

- christian667 - 2011-06-23

My main interest in using the XBMC on the pandaboard is to watch TV using the VNSI VDR plugin. The VDR runs like a charm, even watchable from other clients over wifi, but the fresh compiled pandaboard xbmc shows an uncloseable info dialog saying the plugin could not be loaded.

The log says:
Code:
14:29:19 T:1332507648 M:405499904 DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
14:29:19 T:1332507648 M:405499904 DEBUG: ADDON: Dll Initializing - VDR VNSI Client
14:29:19 T:1332507648 M:405499904 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (4) from Create and is not usable
14:29:19 T:1332507648 M:405499904 INFO: Called Add-on status handler for '4' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
14:29:19 T:1332507648 M:405499904 ERROR: PVR - LoadClients - can't initialise client 'VDR VNSI Client'
14:29:19 T:1458115584 M:405499904 DEBUG: Thread Addon Status: VDR VNSI Client start, auto delete: 1

Does anybody know what the bad status (4) means? Is it documented anywhere?
The same git clone works on a i386 machine Sad

BTW native compiling needs 3h and 45 minutes Wink

- tarzan23 - 2011-06-23

Try using ccache to speed up subsequent builds.

- topfs2 - 2011-06-23

christian667 Wrote:My main interest in using the XBMC on the pandaboard is to watch TV using the VNSI VDR plugin. The VDR runs like a charm, even watchable from other clients over wifi, but the fresh compiled pandaboard xbmc shows an uncloseable info dialog saying the plugin could not be loaded.

The log says:
Code:
14:29:19 T:1332507648 M:405499904 DEBUG: PVR - Create - creating PVR add-on instance 'VDR VNSI Client'
14:29:19 T:1332507648 M:405499904 DEBUG: ADDON: Dll Initializing - VDR VNSI Client
14:29:19 T:1332507648 M:405499904 ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (4) from Create and is not usable
14:29:19 T:1332507648 M:405499904 INFO: Called Add-on status handler for '4' of clientName:VDR VNSI Client, clientID:pvr.vdr.vnsi (same Thread=no)
14:29:19 T:1332507648 M:405499904 ERROR: PVR - LoadClients - can't initialise client 'VDR VNSI Client'
14:29:19 T:1458115584 M:405499904 DEBUG: Thread Addon Status: VDR VNSI Client start, auto delete: 1

Does anybody know what the bad status (4) means? Is it documented anywhere?
The same git clone works on a i386 machine Sad

BTW native compiling needs 3h and 45 minutes Wink

Better ask that question in the PVR forum, its probably not related to ARM

- christian667 - 2011-06-23

nice idea but the build is now installed, so I would like to prevent new building in the near future Wink
I've really no idea what
Code:
bad status (4)
means and google doesn't help me out, so I opened a new issue..

EDIT: @topfs2
Sorry you're right - wrong place Smile

- tarzan23 - 2011-06-24

Great, my board has a defective HDMI port... I'll continue as soon as i get a new board...

- madmalkav - 2011-06-24

dandel Wrote:and as a quick note, the OpenGL ES libs are definately included with the root packages (I verified this by looking at the file, arm-buildroot-2010.05-2010-10-12-10.00--svn1957.tgz) the main note is that the build root source tree under 'buildroot-(Release)/package/opengl'

You can get more recent sources if you mail amlogic asking for git access .