enigma2 and drivers

[pop_eye]

Hello all,

1st question: If one wants to develop drivers for a stb board where should he look in enigma2 for the ioctl interface ? Where enigma2 keeps the code for the hardware interfacing ?

2nd question: if external turner is developed for sh4 using v4linux dvb-core.ko, how can this driver work with enigma2 and ufs910 ?
I am looking for the method of getting this driver recognized by kathi.

I have full driver: vt-dvb-core.ko, dvb-usb.ko and dvb-usb-gp8psk.ko compiled for sh4 and error message when loading is "cannot allocate memory" vt-dvb-core.ko is attaching to kernel using major 213. Normally dvb-core.ko is using major 212 - so I did the change to have no conflict. - Unless this does not work with sh4 and need to find other method.

Thank you

[munche]

1. /cvs/cdk/linux/drivers/i2c/ and cvs/cdk/linux/drivers/media/dvb/ may be?
2. Whats mean "external"? USB attached? Or what?

[BPanther]

I think the problem is the different kernel. He try's the *.ko from a kernel 2.6.18 on a 2.6.17 kernel.

[pop_eye]

Guys - defn it is not related to 2.6.18 kernel.

BPanther - what I meant to say is dvb-core.ko, dvb-usb.ko and dvb-usb-gp8psk.ko are originally from v4linux tree, working perfectly with 2.6.18 kernel used by dm800. Even enigma2 is working with this solution and tuner is recognized as dvb-s2.

munche - yes, usb-dvb tuner attached to kathi.

To make things easier I have used the kernel code from 2.6.17 and applied all the changes required and used with 2.6.18 dvb-usb-gp8psk.ko driver, nothing more so the main dvb-core.ko and dvb-usb.ko are from GIT 2.6.17 kernel. (usb tuner driver is back ported and compatible with kernel 2.6.17 and 2.6.18.)

So what should I do so dvb-core.ko not to conflict with stmdvb.ko ?

Can you generate dvb-core.ko for kathi so I can try this usb tuner ?

Thanks

[BPanther]

You want to load 2 dvb-core (stmdvb & dvb-core)? IMHO thats not possible, only one can be used. I think you should try to recompile the driver related to stmdvb.

[pop_eye]

Following are the common calls between 2 dvb-core :

stmdvb.ko is using following calls:
U dvb_dmx_init --> also found in dvb-usb.ko
U dvb_dmx_release --> also found in dvb-usb.ko
U dvb_dmx_swfilter_packet --> also found in dvb-core.ko
U dvb_dmxdev_init --> also found in dvb-usb.ko
U dvb_dmxdev_release --> also found in dvb-usb.ko
U dvb_generic_ioctl --> also found in dvb-usb.ko
U dvb_generic_open --> also found in dvb-usb.ko
U dvb_generic_release --> also found in dvb-usb.ko
U dvb_register_adapter --> also found inn dvb-usb.ko
U dvb_register_device --> also found in dvb-usb.ko
U dvb_unregister_adapter --> also found in dvb-usb.ko
U dvb_unregister_device --> also found in dvb-usb.ko

In the dvbdev.h we need to change "#define DVB_MAJOR 212" to another one (example 213).
In dvbdev.c we need to change the "DVB" in the following line to another value ex: vt_dvb

if ((retval = register_chrdev_region(dev, MAX_DVB_MINORS, "VT-DVB")) != 0) {

Also we rename all the calls to something else example:
vt_dvb_dmx_init, vt_dvb_dmx_release and so on in each v4linux ko (vt-dvb-core.ko and dvb-usb.ko)

Also we need to change Makefile so dvb-core.ko will be called vt-dvb-core.ko

This method is working with dm800 and stb-core.ko

Please explain why is not possible. If kernel can load this I don't see why it cannot be possible.

[pop_eye]

Bump

OK - this is really pissing me off, I have downgraded v4linux to old branch from

cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/video4linux co -P v4l-dvb

and implemented all the said "changes" as mentioned in previous post and only message I can see from kernel is:

insmod sh4-dvb-core.ko: invalid module format

As this suggests the kernel headers are not same as the one included with kathi image - I do not understand why this is happening since I using GIT 2.6.17-stm14 to build all this.


Anyone ?

[munche]

Some new tuners (not included in kernel) req API5 for compile. U can see HL101 API5 patch for STM23. But if u compile STM22 this patch missed

[pop_eye]

Munche,

I was reading somewhere STM linux is not compatible with dvb-core api.

I will try my luck moving away from STM22 maybe STM23 gives better results.

Is HL101 STM23 working currently or is work in progress ?

I wonder if UFS910 can be compiled with STM23 and be stable enough.

[munche]

HL101 working, and it stable only for STM23 0119.

[pop_eye]

How can we determine the i2c address for usb device..is this a random value i can choose or need to investigate on a linux computer ?

hxxp://gitorious.org/open-duckbox-project-sh4/tdt/blobs/master/tdt/cvs/driver/frontends/hl101/core.c

#define I2C_ADDR_STB0899        (0xd4 >> 1)

#define I2C_ADDR_STB6100        (0xc0 >> 1)

#define I2C_ADDR_STV090X        (0xd0 >> 1)

#define I2C_ADDR_STV6110X       (0xc0 >> 1)

#define I2C_ADDR_CX24116        (0x0a >> 1)

#define I2C_ADDR_IX7306         (0xc0 >> 1)

#define CLK_EXT_IX7306           4000000

Thanks

[munche]

if you want to do autodetect, then better way is use STAPI

[pop_eye]

I think I know what STAPI means can you show me how-to on private ?
Where do I find it ? Thank you munche.

[pop_eye]

Update: we cannot use i2c bus method with dvb-usb adapter unfortunately - since this is not a physical tuner connected to i2c bus.
I am still convinced this can be done if someone who knows TDT code very well, gets involved.

Issues:
1. why STM 2.6.17 kernel does not have dvb-core.ko enabled - i have reworked and with some help already have very small usb driver using minimum resources which cannot load on kathi kernel (segmentation fault)

2. we can inject data into STM video0 if we use the pump method, something like vtuner header should be included with stmdvb.ko and not in the usb driver. Without STM documentation this cannot be achieved.

3. we cannot implement dvb-usb driver tuner without using small portion of dvb-core, i am now certain kernel needs to support this natively to get the driver loaded - after this an user space utility will copy the stream to STM video0.

All this effort will bring support to all kinds of tuners including DVB-S/C/T.

[gipas]

Original von pop_eye
All this effort will bring support to all kinds of tuners including DVB-S/C/T.

It's sad there is no interest on this topic from developers. I can understand germans- they don't really need dvb-c/t since they has all tv channels FTA on dvb-s. dvb-t would be great for people from contries where FTA is only available via DVB-T, and attaching USB tuners to Kathrein will give a forever life for it- as a STB for second/third/* TV or STB for old gandmas' TV currently after purchasing new sat tuner kathi will go to trash- it's not good enougth as universal media player due hardware limitations. Well, 3 years is good enougth to serve.