Sundtek dvb-c driver problem

[DaMacFunkin]

Hello I have a driver conflict on my Vu+ duo2 using your mediahome (III) dvb-c stick with my other USB dvb-s2 tuner, I am running the latest VIX Apollo (008) image.
My tuner config is:
A: vu+ (avl6222) dvbs-2 single 28.2
B: vu+ (avl6222) dvbs-2 usals
C: vu+ ssh108 dvb-c 40967
D: sundtek USB dvb-c 40967

The problem I am having is when I install my dvbsky 960 using dw2102 driver from VIX feeds and then restart, my sundtek tuner disappears, a quick look at tuner information in sundtek control center plugin shows stick is recognised but it's resources are being assigned/stolen by dvbsky 960 :-(
As soon as I uninstall dw2102 driver and reboot sundtek tuner reappears.

[Sundtek]

Well I think there's no support for that also since we don't have this one here for testing either. Our Engineers are currently working on a DVB-S/S2 USB Stick (not box) which will have smooth support again.

[DaMacFunkin]

So you are saying that your USB dvb-s2 tuner and dvb-c USB tuner will definitely co-exist in the same enigma 2 box with no driver conflict?

[Sundtek]

Yes, because in our case both are using the same driver and we can coordinate the communication and allocation between both.
Please note we do not lock out anything or any other brand but neither do we support such kind of special mixed brand setup.

[DaMacFunkin]

But basically if I have the dvbs960 installed, your sundtek won't work, it's your driver install that isn't checking and procuring it's own resources, it's pretty poor really.

[Sundtek]

Nope totally wrong we check everything. However some settopboxes aren't made that way (The interfaces aren't consistent over all different settopbox manufacturers, some manufacturers allow multiple opens some don't and that is the main problem).
As mentioned we'll bring up our own DVB-S/S2 Sticks soon and there's no problem with it.

https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=http%3A%2F%2Fsupport.sundtek.com%2Findex.php%2Ftopic%2C1436.0.html&edit-text=&act=url

And according to your first post, the other device is stealing the interface because it is not checking.

[DaMacFunkin]

Not true, The Vu+ duo2 supports upto 8 tuners, if BOTH DVBsky960 and Sundtek are installed, DVBsky960 works, sundtek doesn't, i have had 2 x DVBsky960 installed on the same machine previously with no problems or extra configuration required whatsoever, i'm quite sure you could easily fix this if you wanted to, just incase you have a change of heart here are my tuner infos, one with dvbsky960 installed, one without:

DVB Tuner info
--------------------------------------
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1
  [SERIAL]:
     ID: U140610192543
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 0
        I2C_Device: 2
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 1
        I2C_Device: 2
NIM Socket 2:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(SSH108)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 2
        I2C_Device: 3


NIM Socket 3:
        Type: DVB-S2
        Name: S960
        Frontend_Device: 3

and without:

DVB Tuner info
--------------------------------------
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 2-1
  [SERIAL]:
     ID: U140610192543
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 0
        I2C_Device: 2
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 1
        I2C_Device: 2
NIM Socket 2:
        Type: DVB-C
        Name: Vuplus DVB-C NIM(SSH108)
        Mode 0: DVB-C
        Mode 1: DVB-T2
        Frontend_Device: 2
        I2C_Device: 3


NIM Socket 3:
        Type: DVB-C
        Name: Sundtek DVB-C (III) (0/0) (USB)
        Frontend_Device: 3

It is my opinion that your device driver struggles to be adapter2.
??

Maybe if you are certain your dvb-s2 adapter will work with dvb-c adapter you could send me a discount code so i can buy one?

[DaMacFunkin]

Check out this guys config
http://www.world-of-satellite.com/showthread.php?38704-Installation-of-driver-DVB-USB-SIANO-fails&p=298695&viewfull=1#post298695

[Sundtek]

Yes, because the legacy system is not checking or not able to check if ports are allocated, this is not our problem.
We do those checks. Neither do we support other devices attached to the USB bus because we do not know if they interfere with each other.
DVB-T in any case might be fine because the bandwidth is only ~16mbit, DVB-C/S can go up to 90 MBit with our controllers.

[DaMacFunkin]

You do contradict yourself, the point I was making is other vendors usb products have no problems installing alongside the dvbsky960, only yours has a problem, also you don't seem to think that your USB dvb-c and USB dvbs-2 would have any bandwidth problems alongside each other.
I personally think you have tried to be too clever by having install via a control panel instead of releasing a driver ipk, why don't you just release the driver to everyone, it's not exactly in the spirit of Linux is it?

[Sundtek]

You can modify the enigma2 code to fit your needs if you need to. There is no problem with it.
Every parameter you need is configurable in our driver.

You need to understand the problem with your Settopbox, then you can solve it.
And again the problem is not our driver.

The correct way would be to fix this problem in the VU+ Broadcom drivers, everything else is just papering the issue.