View: 12121|Reply: 13

OPi One - TBS DVB-S2 drivers

[Copy link]

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
Published in 2016-3-23 23:56:56 | Show all floors |Read mode
Hi,
I have OPi One with OpenELEC. Everythings fine, but now I want to use it with my USB DVB-S2 tuner. Problem is with TBS drivers. TBS company made only x86,x64 drivers. But someone made drivers usable for an ARM arch.

For RBPi is an image already prepared on OpenELEC forum:

http://openelec.tv/forum/83-dvb- ... dia-build-liplianin
https://github.com/CvH/OpenELEC.tv
https://github.com/ljalves/linux_media/wiki

So it means it should work on OrangePi.

My problem is, I can't insert these drivers inside source files from jernejsk   ("I can't" means, I don't have proper knowledge)

In this moment I'm trying something, but I'm not sure if I have to insert these drivers somehow in the source files and build it together or take prepared image and then try to compile only these drivers and where. If I can compile it on OPi (dont know the possibility) or it it is possible to make cross compile on my pc....

I will appreciate every hint.






4

threads

1118

posts

9497

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9497
Published in 2016-3-24 00:45:45 | Show all floors
What you have to do is this:
1) Pull my openelec-7.0 branch.
2) Following packages must be updated/created (take them from CvH github):
packages/linux-firmware/dvb-firmware/
packages/linux-drivers/ljalves-cc
packages/linux-drivers/ljalves
3) edit distributions/OpenELEC/options - under ADDITIONAL_DRIVERS you should add one of the following drivers:
ljalves-cc
ljalves
4) Build image. For One you should use:
  1. PROJECT=H3 DEVICE=OPiOne ARCH=arm make image
Copy code

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
 Author| Published in 2016-3-24 01:34:06 | Show all floors
Hi, thanks. build is running right now. I will let you know here.

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
 Author| Published in 2016-3-24 03:24:28 | Show all floors
something is wrong:

  1. 2016-03-23 19:38:13 (7.36 MB/s) - 'sources/ljalves-cc/ljalves-cc-2016-03-11.tar.xz' saved [86659692/86659692]

  2.   UNPACK   ljalves-cc
  3.       APPLY PATCH (common)   /home/jan/OpenELEC-OPi2/packages/linux-drivers/ljalves-cc/patches/ljalves-cc-01-dont-run-rmmod.pl.patch
  4. can't find file to patch at input line 5
  5. Perhaps you used the wrong -p or --strip option?
  6. The text leading up to this was:
  7. --------------------------
  8. |diff --git a/media_build/v4l/Makefile b/media_build/v4l/Makefile
  9. |index 22fa318..e2128ed 100644
  10. |--- a/media_build/v4l/Makefile
  11. |+++ b/media_build/v4l/Makefile
  12. --------------------------
  13. File to patch:
  14. Skip this patch? [y]
  15. Skipping patch.
  16. 1 out of 1 hunk ignored
  17. make: *** [image] Error 1
  18. root@jan-VirtualBox:/home/jan/OpenELEC-OPi2#
Copy code

4

threads

1118

posts

9497

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9497
Published in 2016-3-24 03:55:08 | Show all floors
remove or comment out line which start with ADDITIONAL_DRIVERS in projects/H3/options and then execute following command:
  1. PROJECT=H3 DEVICE=OPiOne ARCH=arm scripts/clean media_build
Copy code

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
 Author| Published in 2016-3-24 04:35:24 | Show all floors
ok, but what is the purpose of commenting additional drivers, when I want these ?

4

threads

1118

posts

9497

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9497
Published in 2016-3-24 04:52:18 | Show all floors
I'm talking about different files:
distributions/OpenELEC/options
projects/H3/options

They both have ADDITIONAL_DRIVERS option. You can add your driver name to any of those, but "media_build" driver must not be present in any.

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
 Author| Published in 2016-3-24 04:58:21 | Show all floors
my bad, thank you

1

threads

8

posts

69

credits

Registered member

Rank: 2

credits
69
 Author| Published in 2016-3-24 18:05:29 | Show all floors
Hi, Here's the result:

  1. UNPACK   ljalves
  2.           APPLY PATCH (common)   /home/jan/OpenELEC-OPi2/packages/linux-drivers/ljalves/patches/ljalves-01-dont-run-rmmod.pl.patch
  3. patching file media_build/v4l/Makefile
  4.           APPLY PATCH (common)   /home/jan/OpenELEC-OPi2/packages/linux-drivers/ljalves/patches/ljalves-02-tbs-5220-5881-support.patch
  5. can't find file to patch at input line 14
  6. Perhaps you used the wrong -p or --strip option?
  7. The text leading up to this was:
  8. --------------------------
  9. |From 36e253f91dae4006f4e105da1fa5cce585170cda Mon Sep 17 00:00:00 2001
  10. |From: CrazyCat <crazycat69@narod.ru>
  11. |Date: Tue, 24 Nov 2015 02:27:12 +0200
  12. |Subject: [PATCH 1/2] dvb-usb-cxusb: Minor fix for Geniatech T230 init,
  13. |
  14. |---
  15. | drivers/media/usb/dvb-usb/cxusb.c | 3 +--
  16. | 1 file changed, 1 insertion(+), 2 deletions(-)
  17. |
  18. |diff --git a/drivers/media/usb/dvb-usb/cxusb.c b/drivers/media/usb/dvb-usb/cxusb.c
  19. |index ab71511..eb74793 100644
  20. |--- a/drivers/media/usb/dvb-usb/cxusb.c
  21. |+++ b/drivers/media/usb/dvb-usb/cxusb.c
  22. --------------------------
  23. File to patch:
  24. Skip this patch? [y]
  25. Skipping patch.
  26. 2 out of 2 hunks ignored
  27. can't find file to patch at input line 54
  28. Perhaps you used the wrong -p or --strip option?
  29. The text leading up to this was:
  30. --------------------------
  31. |
  32. |From 2e7929505a11aa9bf0059d04f1b38e6fe74ed1ed Mon Sep 17 00:00:00 2001
  33. |From: CrazyCat <crazycat69@narod.ru>
  34. |Date: Tue, 24 Nov 2015 02:28:04 +0200
  35. |Subject: [PATCH 2/2] Support fir TBS 5220, 5881.
  36. |
  37. |---
  38. | drivers/media/usb/dvb-usb/Kconfig   |  18 +
  39. | drivers/media/usb/dvb-usb/Makefile  |   6 +
  40. | drivers/media/usb/dvb-usb/tbs5220.c | 500 ++++++++++++++++++++++
  41. | drivers/media/usb/dvb-usb/tbs5220.h |   8 +
  42. | drivers/media/usb/dvb-usb/tbs5881.c | 816 ++++++++++++++++++++++++++++++++++++
  43. | drivers/media/usb/dvb-usb/tbs5881.h |   8 +
  44. | 6 files changed, 1356 insertions(+)
  45. | create mode 100644 drivers/media/usb/dvb-usb/tbs5220.c
  46. | create mode 100644 drivers/media/usb/dvb-usb/tbs5220.h
  47. | create mode 100644 drivers/media/usb/dvb-usb/tbs5881.c
  48. | create mode 100644 drivers/media/usb/dvb-usb/tbs5881.h
  49. |
  50. |diff --git a/drivers/media/usb/dvb-usb/Kconfig b/drivers/media/usb/dvb-usb/Kconfig
  51. |index 5949575..5094bc7 100644
  52. |--- a/drivers/media/usb/dvb-usb/Kconfig
  53. |+++ b/drivers/media/usb/dvb-usb/Kconfig
  54. --------------------------
  55. File to patch:
  56. Skip this patch? [y]
  57. Skipping patch.
  58. 1 out of 1 hunk ignored
  59. can't find file to patch at input line 80
  60. Perhaps you used the wrong -p or --strip option?
  61. The text leading up to this was:
  62. --------------------------
  63. |diff --git a/drivers/media/usb/dvb-usb/Makefile b/drivers/media/usb/dvb-usb/Makefile
  64. |index 11d6be4..cba817c 100644
  65. |--- a/drivers/media/usb/dvb-usb/Makefile
  66. |+++ b/drivers/media/usb/dvb-usb/Makefile
  67. --------------------------
  68. File to patch:
  69. Skip this patch? [y]
  70. Skipping patch.
  71. 1 out of 1 hunk ignored
  72. patching file drivers/media/usb/dvb-usb/tbs5220.c
  73. patching file drivers/media/usb/dvb-usb/tbs5220.h
  74. patching file drivers/media/usb/dvb-usb/tbs5881.c
  75. patching file drivers/media/usb/dvb-usb/tbs5881.h
  76. make: *** [image] Error 1
  77. root@jan-VirtualBox:/home/jan/OpenELEC-OPi2#
Copy code


I don't want you to think I'm lazy or something. I'm trying to understand it and search over the internet. But you have obviously more experiences.
thanks

4

threads

1118

posts

9497

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9497
Published in 2016-3-25 00:28:26 | Show all floors
johnyor replied at 2016-3-24 11:05
Hi, Here's the result:

There is nothing wrong if you ask for help. That's why forums exist

First I would try clean build, e.g. delete build folder. If not, then you have a bit of a problem - you would need to fix package.mk and/or add patches.

You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list