Moderator Control Panel ]

Is Raspberry Pi (ARM) supported?

Is Raspberry Pi (ARM) supported?

Postby orekhovav » Thu May 16, 2013 12:19 pm

Hello.
I use TBS6220 tuner under linux (with patches from CrazyCat for multiPLP support).
But i want USB DVB-T2 tuner for my Raspberry Pi. Is it possible?
Your MOI box just for DVB-S, not for DVB-T2 :(
And one more question: when you can release official linux drivers with MultiPLP support??? :)
orekhovav
 
Posts: 27
Joined: Mon Dec 24, 2012 10:47 am

Re: Is Raspberry Pi (ARM) supported?

Postby crazycat » Fri May 17, 2013 3:36 am

Look like 5280 not have support in linux drivers, only 5880 (same NIM as used in 6220). My patches also replace binary frontend driver with open-source TDA18212/CXD2820r with MultiPLP support. I thinks possible compile 5880 driver for ARM.

P.S. My patches updated for latest TBS V4L drivers(+ fixed support for dual NIM in 6280, 6284).
crazycat
 
Posts: 537
Joined: Mon Jan 31, 2011 2:46 am
Location: Ukraine, Kharkov

Re: Is Raspberry Pi (ARM) supported?

Postby orekhovav » Fri May 17, 2013 9:00 am

Thanks, CrazyCat. Now i focused to 5880 :) And cubieboard :)
orekhovav
 
Posts: 27
Joined: Mon Dec 24, 2012 10:47 am

Re: Is Raspberry Pi (ARM) supported?

Postby orekhovav » Mon May 20, 2013 7:25 pm

Hello, CrazyCat.

Patched and compiled all without problems, but drivers won't work :(

kernel 3.8.13, tbs drivers 2013-05-06, your patches from link.
Compiled and tested on amd64.
dmesg:
[ 287.612537] saa716x_core: disagrees about version of symbol dvb_dmxdev_init
[ 287.612551] saa716x_core: Unknown symbol dvb_dmxdev_init (err -22)
[ 287.612621] saa716x_core: disagrees about version of symbol dvb_register_adapter
[ 287.612627] saa716x_core: Unknown symbol dvb_register_adapter (err -22)
[ 287.612746] saa716x_core: disagrees about version of symbol dvb_net_init
[ 287.612752] saa716x_core: Unknown symbol dvb_net_init (err -22)
[ 287.612765] saa716x_core: disagrees about version of symbol dvb_dmxdev_release
[ 287.612771] saa716x_core: Unknown symbol dvb_dmxdev_release (err -22)
[ 287.612788] saa716x_core: disagrees about version of symbol dvb_frontend_detach
[ 287.612794] saa716x_core: Unknown symbol dvb_frontend_detach (err -22)
[ 287.612838] saa716x_core: disagrees about version of symbol dvb_net_release
[ 287.612844] saa716x_core: Unknown symbol dvb_net_release (err -22)
[ 287.612858] saa716x_core: disagrees about version of symbol dvb_unregister_frontend
[ 287.612863] saa716x_core: Unknown symbol dvb_unregister_frontend (err -22)
[ 287.612878] saa716x_core: disagrees about version of symbol dvb_register_frontend
[ 287.612884] saa716x_core: Unknown symbol dvb_register_frontend (err -22)
[ 287.612898] saa716x_core: disagrees about version of symbol dvb_unregister_adapter
[ 287.612904] saa716x_core: Unknown symbol dvb_unregister_adapter (err -22)
[ 287.713517] saa716x_core: disagrees about version of symbol dvb_dmxdev_init
[ 287.713529] saa716x_core: Unknown symbol dvb_dmxdev_init (err -22)
[ 287.713596] saa716x_core: disagrees about version of symbol dvb_register_adapter
[ 287.713602] saa716x_core: Unknown symbol dvb_register_adapter (err -22)
[ 287.713724] saa716x_core: disagrees about version of symbol dvb_net_init
[ 287.713729] saa716x_core: Unknown symbol dvb_net_init (err -22)
[ 287.713743] saa716x_core: disagrees about version of symbol dvb_dmxdev_release
[ 287.713748] saa716x_core: Unknown symbol dvb_dmxdev_release (err -22)
[ 287.713766] saa716x_core: disagrees about version of symbol dvb_frontend_detach
[ 287.713771] saa716x_core: Unknown symbol dvb_frontend_detach (err -22)
[ 287.713816] saa716x_core: disagrees about version of symbol dvb_net_release
[ 287.713821] saa716x_core: Unknown symbol dvb_net_release (err -22)
[ 287.713835] saa716x_core: disagrees about version of symbol dvb_unregister_frontend
[ 287.713841] saa716x_core: Unknown symbol dvb_unregister_frontend (err -22)
[ 287.713856] saa716x_core: disagrees about version of symbol dvb_register_frontend
[ 287.713862] saa716x_core: Unknown symbol dvb_register_frontend (err -22)
[ 287.713876] saa716x_core: disagrees about version of symbol dvb_unregister_adapter
[ 287.713882] saa716x_core: Unknown symbol dvb_unregister_adapter (err -22)

What may be wrong?
orekhovav
 
Posts: 27
Joined: Mon Dec 24, 2012 10:47 am

Re: Is Raspberry Pi (ARM) supported?

Postby updatelee » Tue May 21, 2013 2:42 am

You've got the old drivers mixed in with the new drivers.

Usually a sudo make rminstall before the install and reboot will fix it. If the folder layout is different then singles you'll need to move or rename the lib modules media folder then make install

UDL
TBS6925/5980, Prof 7301/7500/8000, Genpix Skywalker-1, Skystar 2 Express HD
Hauppauge 950Q, Kworld 330U/435v3/445v3
Dreambox 800

I use Linux and support open source projects.
User avatar
updatelee
 
Posts: 374
Joined: Wed Jul 25, 2012 11:48 am
Location: CFB Edmonton

Re: Is Raspberry Pi (ARM) supported?

Postby orekhovav » Tue May 21, 2013 11:51 am

after removing media from lib/modules/(uname -r) and make install all works fine, thanks.

One more qustion, updatelee:
What about multiPLP support in official drivers? :)
orekhovav
 
Posts: 27
Joined: Mon Dec 24, 2012 10:47 am

Re: Is Raspberry Pi (ARM) supported?

Postby crazycat » Wed May 22, 2013 1:39 am

First need update TBS V4L to current official V4L :) Next implement MultiPLP in precompiled binaries or better replace with open-source TDA18212/CXD2820R drivers.

P.S. My BitBucket repository with patched linux-tbs-drivers with integrated firmware install (TBS, TT, Technisat and popular demod firmwares)/.
crazycat
 
Posts: 537
Joined: Mon Jan 31, 2011 2:46 am
Location: Ukraine, Kharkov

Re: Is Raspberry Pi (ARM) supported?

Postby orekhovav » Wed May 22, 2013 9:49 am

crazycat Wrote:First need update TBS V4L to current official V4L :) Next implement MultiPLP in precompiled binaries or better replace with open-source TDA18212/CXD2820R drivers.


Sounds like "five, may be six years" :-D

Thanks for patches. :)
orekhovav
 
Posts: 27
Joined: Mon Dec 24, 2012 10:47 am

Re: Is Raspberry Pi (ARM) supported?

Postby madasahatter » Mon Sep 02, 2013 7:21 pm

Hi there

I am new to all this, and just trying to migrate my MythTV Backend onto Raspberry Pi after making a Frontend on a different Pi.

The problem appears to be that the driver.o file shipped by Turbosight is ELF format, and won't work for ARM.

Is it possible that the source code can be made available so the ARM processors can have a compile attempted for them? I appreciate that this is proprietary code, but a raspberry pi would just be SUCH an elegant solution - imagine how many TBS5280's you'd sell if the entry point hardware for a media centre was £35...

Go on....
madasahatter
 
Posts: 10
Joined: Sat Aug 31, 2013 4:21 am


Return to Linux

Who is online

Users browsing this forum: No registered users and 1 guest