14 replies to this topic

[ecureuil35]

Hello. My question is how to compile bm750 linux kernel dvb-usb drivers? they are not included in the openpli image obtened with the Makefile for the new head 2.1. The recipes v4ll-dvb and firmwares contains the information, but i am unable to use the related bb file! (I am interested by af9035 driver). Curiously the compilation of softcam oscam is easy! Thanks for this great work and a solution for this problem.

[MiLo]

If you want to compile extra kernel modules or change the kernel, then the command you're looking for is "bitbake -c menuconfig virtual/kernel". There is no "make" target for that, it requires raw bitbake control.

This will bring up the kernel config UI, and let you select modules and drivers. Copy the resulting ".config" back into the defconfig file in the OE tree (recipes/linux/linux-$MACHINE/..) to preserve your work, and increment the kernel PR (suggest appending a ".1", ".2" etc) prior to configuring to make it easy to upgrade your kernel in the box with your changes.

[stick50jr]

Hello. My question is how to compile bm750 linux kernel dvb-usb drivers? they are not included in the openpli image obtened with the Makefile for the new head 2.1. The recipes v4ll-dvb and firmwares contains the information, but i am unable to use the related bb file! (I am interested by af9035 driver). Curiously the compilation of softcam oscam is easy! Thanks for this great work and a solution for this problem.

I don't know why these (af9035) drivers are missing from the OpenPLi... I found that they are present in the latest Vix (based on OpenPLi 2.1). I was able to install these (opkg install kernel-module-dvb-usb-af9035) and then I copied the files from the appropriate diectories and back into the same directories of OpenPli. So I have them working well on the current OpenPLi images (VuDuo + AverMedia TwinStar [a825 dual usb dvb-t based on af9035] ). All this and I have no idea of what would be required to compile them...

cheers

[Gennar1]

If I remember correctly, to compile the v4l drivers you can use:

bitbake v4l-dvb-modules -c clean
bitbake v4l-dvb-modules -c build

At the end of the process you will find the ipk modules in build-*/tmp/deploy/ipk/*

[ecureuil35]

Many thanks. It’s a good idea to manually install af 9035 driver (3 ko files+firmware) copied from an installed VTI image, working perfectly but very frustrating!
Errors trying "bitbake v4l-dvb-modules -c build ": 1) ***WARNING:*** You do not have the full kernel sources installed.This does not prevent you from building the v4l-dvb tree if you have the kernel headers, but the full kernel source may be required in order to use make menuconfig / xconfig / qconfig. 2) /home/mouton/vuplus/bm750/build/tmp/work/bm750-oe-linux/v4l-dvb-modules-0.0+hg20100904-r5/v4l-dvb/v4l/tuner-xc2028.c:1178: error: 'T_DIGITAL_TV' undeclared (first use in this function)
And "bitbake -c menuconfig virtual/kernel" gives many errors, for the same reason? What is the solution? The compilation of an af9035 driver for i386 ubuntu 11.10 is very easy and perfectly functional, cross compilation is another job! Regards.

[Gennar1]

You need to configure the environment before running bitbake. This is done by the command:

source env.source

in the "build-*" directory.

[andyblac]

this is because Pli decided not to use the ViX kernel 3.1.1 for vu boxes, but waited for vu to supply a 3.1.1 kernel patch, the vix kernel for vu boxes has ALL the patches that where used in 3.1.0 for xtrends kernel. this the main reason i spent hours of coding my own kernel for Vu 3.1.1, so i could use all the patches that where available for xtrend 3.1.0.

and is why vix maintains it own kernel for Vu's and does not rely on vu, as vu can be very slow in updating.

[pieterg]

i spent hours of coding my own kernel for Vu 3.1.1

Should we call you andytorvalds

[stick50jr]

this is because Pli decided not to use the ViX kernel 3.1.1 for vu boxes, but waited for vu to supply a 3.1.1 kernel patch, the vix kernel for vu boxes has ALL the patches that where used in 3.1.0 for xtrends kernel. this the main reason i spent hours of coding my own kernel for Vu 3.1.1, so i could use all the patches that where available for xtrend 3.1.0.

and is why vix maintains it own kernel for Vu's and does not rely on vu, as vu can be very slow in updating.

Andy, your efforts are very much appreciated by me and at Vix and the af9035 drivers from the Vix feed work well under OpenPLi. I don't understand why the OpenPLi tribe doesn't offer the af9035 in their feeds... I wonder what the issue is? I was under the impression that Gennar1 and Ambrosa did some good work here under the OpenPLi banner and that this has been picked up by Vix... but it is not available in the OpenPLi feeds... is this a bit bizarre?

Edited by stick50jr, 22 March 2012 - 10:54.

[kocebs]

How to install bitbake tool on openpli 6.0? I want install dtiver
I write " opkg install bitbake" and objekt not found:(

[Pr2]

bitbake is not to use on your STB.

bitbake is used for compilation on your local PC when you decide to build your own image locally.

 

Would be better to create your own thread explaining for which hardware you are looking for driver.

There are already many pre-build drivers that can be installed in OpenPLi 6.

[kocebs]

bitbake is not to use on your STB.
bitbake is used for compilation on your local PC when you decide to build your own image locally.
 
Would be better to create your own thread explaining for which hardware you are looking for driver.
There are already many pre-build drivers that can be installed in OpenPLi 6.

I want installing Mt7610u driver and inklude module on my kernel 3.13.5
I faund this https://github.com/o...610u_3.0.0.2.bb

[WanWizard]

You need:

• to skim over the Yocto manual and the Bitbake manual to have any idea of what you are doing
• a linux machine (or VM), running gcc 6.x (Unbuntu, Fedora 25, CentOS with devtools6)
• to install all dependencies Yocto needs (see the manual, chapter 3)
• to clone the OpenPLi repository (https://github.com/O...openpli-oe-core, and checkout the desired branch)
• cd to the directory you cloned the repository in
• enter "MACHINE=<yourbox> make image" to build your image

Once that is done and you have a working build environment, you can start fiddling with recipes.

 

Note that you quite a bit of diskspace for a complete build, a single build for 3 environments (1 x MIPSEL, 2 x ARM) we support needs about 200-250GB. And you need time, a first build run on my build server (a Core i7 920) takes about 4 hours.  

 

I personally prefer CentOS, as it runs gcc 4.x native (which is needed to build OpenPLi 4), gcc 6.x with devtools-6 (needed for OpenPLi 6.x), and gcc 7.x with devtools-7 (needed for develop and OpenPLi 7.x), and you can switch very easily between the environments. 

[kocebs]

You need:
[LIST][*]to skim over the Yocto manual and the Bitbake manual to have any idea of what you are doing[/*]
[*]a linux machine (or VM), running gcc 6.x (Unbuntu, Fedora 25, CentOS with devtools6)[/*]
[*]to install all dependencies Yocto needs (see the manual, chapter 3)[/*]
[*]to clone the OpenPLi repository (https://github.com/O...openpli-oe-core, and checkout the desired branch)[/*]
[*]cd to the directory you cloned the repository in[/*]
[*]enter "MACHINE=<yourbox> make image" to build your image[/*]
[/LIST]Once that is done and you have a working build environment, you can start fiddling with recipes.
 
Note that you quite a bit of diskspace for a complete build, a single build for 3 environments (1 x MIPSEL, 2 x ARM) we support needs about 200-250GB. And you need time, a first build run on my build server (a Core i7 920) takes about 4 hours.  
 
I personally prefer CentOS, as it runs gcc 4.x native (which is needed to build OpenPLi 4), gcc 6.x with devtools-6 (needed for OpenPLi 6.x), and gcc 7.x with devtools-7 (needed for develop and OpenPLi 7.x), and you can switch very easily between the environments.

Thank you very much Master!

[Erik Slagter]

Also note:

 

- the driver you're searching for is probably part of the kernel, just not of the kernel version you're (and the manufacturer is) using

- changing kernel config may change the kernel signature and break loading of the DVB drivers

- you cannot use another kernel version without breaking loading of the DVB drivers

 

So it may pay off to investigate before you begin.