Page 1 of 1

Porting files into the current kernel

PostPosted: Tue Sep 17, 2013 6:37 pm
by patrickTBS
Hi all

I am trying to get up and running a TBS6928 on my Linux 3.10.2, but I prefer to take the relevant files from the 1st September 2013 release. Indeed by this way I avoid to take some risks to break other cards.

There are saa716x_**** tuners and frontend file to place in their folder and the Makefile and Kconfig to update. The chip parts are now working (or looks like), but in the /dev/dvb/adapterXYZ folder, I have only 3 of the 4 devices as the frontend is missing.

After investigation the tbs6928de.c is missing (like all the frontends from TBS) and I have to fix a Kconfig problem that prevent to select any frontend. After forcing the real function tbs6928de_attach in the tbs6928.h file, I don't have the printk message anymore saying that the frontend has been disabled by Kconfig, but I have a link error on the saa716x_tbs.o on the second stage build modules.

I am trying to find these files, but I can't in both the Linux and the v4l folders. After searching for the function using a command like fgrep tbs6928de_attach * -R -A 5 -B 2 in all the zip file, I can find (external) declarations, dummy function and matches in the binary driver, but nothing that looks like a function instantiation.
Also the file tbsctrl.c (saa716x folder) is missing.

Does these files stored somewhere else? On the linuxtv site? Did I missed a code generator that produces the files (in which case it is normal to not find the files by their full name or content).

Thanks

Re: Porting files into the current kernel

PostPosted: Tue Sep 17, 2013 10:47 pm
by updatelee
That card uses the tax present compiled libs, I wouldn't recommend using present compiled libs from another kernel with the new v4l kernel.

UDL

Re: Porting files into the current kernel

PostPosted: Wed Sep 18, 2013 7:29 pm
by patrickTBS
I understand it is not recommended but I don't have choices. i) I get rid of the TBS card ii) I merge your drivers into the main kernel tree.

If you like I can send back to you the (big) patch if I succeed.

In the dvb, the merging are not so difficult as the numeric is slightly standard: tuner fronted main device. The parameters are also more or less standard.

Another question: in the actual state of my build, I can not see the common interface. Have you designed the saa716x driver for the CI?

Thanks

Re: Porting files into the current kernel

PostPosted: Wed Sep 18, 2013 9:00 pm
by updatelee
If all the includes in the TBS tree are 100% identical to those in the v4l tree it might work, if there are changes I can tell you it wont work.

I dont use a CI so I have zero knowlage of how they work or how to interface them. They just arent used here in NA

UDL

Re: Porting files into the current kernel

PostPosted: Thu Sep 19, 2013 1:10 am
by patrickTBS
To come back to the initial question, could you post the missing files such as saa716x_ctrl.c and tbs6928de.c

Re: Porting files into the current kernel

PostPosted: Thu Sep 19, 2013 9:35 am
by updatelee
Not sure if your talking to me or not but I don't work for TBS. I don't have access to any of TBS's code.

Re: Porting files into the current kernel

PostPosted: Thu Sep 19, 2013 8:56 pm
by patrickTBS
Sorry for the confusion but I assumed you are a TBS staff member (perhaps due to your nickname)

Is there TBS people on this forum?

Re: Porting files into the current kernel

PostPosted: Thu Sep 19, 2013 11:31 pm
by updatelee
Now you have me curious, I can't seem to see the connection between my Nick and TBS.

There defn are TBS staff on this sure though, hopefully they will chime in.

UDL

Re: Porting files into the current kernel

PostPosted: Thu Sep 26, 2013 9:56 pm
by dahlSTROM