Will drivers compile on Raspberry Pi?

[esqmo]

As anybody tried compiling these drivers on an ARM CPU. Or more specifically does anybody know if this product will work with a Raspberry Pi?

[imperia]

bump

[updatelee]

Does it use TBS's precompiled binaries? if so your out of luck. TBS only supplies x86 and x86_64 binaries. Another reason opensource is better. TBS you listening?

UDL

[crazycat]

5910, 5920, 5928, 5980 drivers 100% open-source.
5925 driver also easy converted to 100% open-source

[steven]

As anybody tried compiling these drivers on an ARM CPU. Or more specifically does anybody know if this product will work with a Raspberry Pi?

unfortunately, our Linux drivers currently does not support platforms like Raspberry PI - the reason for that are complex...
To address the ARM market, we already made ARM box with build-in Dual DVB-S2 tuner :

http://www.tbsdtv.com/launch/moi-dvb-s2 ... g-box.html

and you can use your Raspberry PI as client to it - that in fact should be quite more flexible solution - just stream DVB channels to your Raspberry PI, because as ARM hardware our box is more powerful than Raspberry PI.

[mcinano]

unfortunately, our Linux drivers currently does not support platforms like Raspberry PI - the reason for that are complex...

Is this true?
I compiled the drivers for arm (raspberry pi) and it loaded correctly.

But I never got a picture out of my box. It crashs when i'm going to use the qbox (starting vdr, vdr plugin and xbmc). Is this a sign of a not functional driver? What would be to do to make it work on ARM architectures? What are these complex reasons?

greetings
Michael

[mcs]

Hi,

Can you explain how you compiled the drivers? My compile always dies. When I compile I get:
/home/pi/tbs5922/linux-tbs-drivers/v4l/sh_mobile_csi2.c:369:20: error: expected declaration specifiers or '...' before string constant

No picture can have to do with some problem of the pi with this:

http://openelec.tv/forum/124-raspberry- ... n-no-audio

There is a problem of the pi with livetv, and if I understand correctly the pi guys blame it on tvheadend and xbmc and vice versa ( firmware problem??)
Maybe we can try and pull this off.
Cheers

mcs

[mcinano]

Can you explain how you compiled the drivers?

I did this on Arch Linux ARM. With AUR Packaging System and though I had to satisfy special needs of this distribution. But maybe you can adapt it to others. Driver version is 121021 from http://www.tbsdtv.com/download/document/common/tbs-linux-sources_v121021.zip

Howto compile

Code: Select all

  src="linux-tbs-sources"
  tar xjf ${src}.tar.bz2
  cd "$src"
  patch -p1 < ../patch_121021.patch
  make

  cp dvb-usb-tbsqbox-id5980.fw /lib/firmware/
  make install

  depmod -a


patch_121021.patch

Code: Select all

diff -rup linux-tbs-sources_orig/linux/drivers/media/video/sh_mobile_csi2.c linux-tbs-sources/linux/drivers/media/video/sh_mobile_csi2.c
--- linux-tbs-sources_orig/linux/drivers/media/video/sh_mobile_csi2.c 2013-01-07 22:40:39.616089270 +0000
+++ linux-tbs-sources/linux/drivers/media/video/sh_mobile_csi2.c  2013-01-07 22:45:14.113554447 +0000
@@ -8,6 +8,8 @@
  * published by the Free Software Foundation.
  */

+#include <linux/kernel.h>
+#include <linux/module.h>
 #include <linux/delay.h>
 #include <linux/i2c.h>
 #include <linux/io.h>
diff -rup linux-tbs-sources_orig/v4l/Makefile linux-tbs-sources/v4l/Makefile
--- linux-tbs-sources_orig/v4l/Makefile 2013-01-07 22:40:23.026242468 +0000
+++ linux-tbs-sources/v4l/Makefile  2013-01-07 22:41:04.615858413 +0000
@@ -179,7 +179,7 @@ ifeq ($(inst-m),)
   inst-m := $(obj-m)
 endif

-v4l_modules := $(shell /sbin/lsmod|cut -d' ' -f1 ) $(patsubst %.ko,%,$(inst-m))
+v4l_modules := $(shell /usr/bin/lsmod|cut -d' ' -f1 ) $(patsubst %.ko,%,$(inst-m))

 #################################################
 # locales seem to cause trouble sometimes.



Please tell me if you can get it to work.