35 replies to this topic

[pop_eye]

Incidentally what for DVB-C tuner you use?

 

http://www.linuxtv.o...B-C_USB_Devices

 

Any tuner listed with linux support - in the same time you need to find if driver exists in linux 3.1

 

Maybe there is a limitation (which should not be) with Sundtek driver.

 

I can confirm two usb tuners: dvb-s2 and atsc type are working with vu-duo so your stb is working correctly.

Edited by pop_eye, 27 September 2013 - 15:06.

[sundtek]

Unfortunately I have no other USB tuner. Only Sundtek (dvb-c) and  MSI Digivox (dvb-t).

No, I can`t  switch between the tuner. If both tuners connect, then DVB-T recognizes but works Sundtek... weird right? To force work DVB-T actually, I need to get Sundtek out. So they only work separately from each other.

Yes, I also think that  Sundtek may another usb tuner disturb. Not sure but ...
Incidentally what for DVB-C tuner you use?

you can try to insert a config line in /etc/sundtek.conf

vtuner_skip0=vtuner0

[westsib]

you can try to insert a config line in /etc/sundtek.conf

vtuner_skip0=vtuner0

Yeaaaah!
Fourth tuner has appeared to me.

 

root@vuduo:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
Frontend_Device: 0
NIM Socket 1:
Type: DVB-S2
Name: BCM7335 DVB-S2 NIM (internal)
Frontend_Device: 1

NIM Socket 2:
Type: DVB-T
Name: DVB-T 2
Frontend_Device: 2
NIM Socket 3:
Type: DVB-C
Name: Sundtek MediaTV Digital Home (USDVB-C
Frontend_Device: 3root@vuduo:~#

But .... there again though.
Both the tuner does not work with existing settings.
After the setting and Autoscanning they have no channels found.

What disturbs now???

 

root@vuduo:~# dmesg
tfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-8: SAMSUNG HD105SI, 1AJ10001, max UDMA/133
ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD105SI  1AJ1 PQ: 0 ANSI: 5
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 1:0:0:0: [sda] Attached SCSI disk
usb 1-1: new high speed USB device number 3 using ehci-brcm
scsi2 : usb-storage 1-1:1.0
usb 2-1: new high speed USB device number 2 using ehci-brcm
Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 16 -> 8
input: Afatech DVB-T 2 as /devices/platform/ehci-brcm.1/usb2/2-1/2-1:1.1/input/input0
generic-usb 0003:15A4:9016.0001: input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-ehci_hcd-1/input1
usb 1-2.4: new high speed USB device number 4 using ehci-brcm
UBI: max. sequence number:       2029
UBI: attached mtd0 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            118 MiB
UBI: number of good PEBs:        943
UBI: number of bad PEBs:         1
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 943
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 10/2
UBI: image sequence number:  1307672705
UBIFS: parse sync
UBI: background thread "ubi_bgt0d" started, PID 48
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   116690944 bytes (113956 KiB, 111 MiB, 919 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 240k freed
scsi 2:0:0:0: Direct-Access     JetFlash Transcend 4GB    1100 PQ: 0 ANSI: 4
sd 2:0:0:0: [sdb] 7913472 512-byte logical blocks: (4.05 GB/3.77 GiB)
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
scsi: killing requests for dead queue
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
scsi: killing requests for dead queue
scsi: killing requests for dead queue
scsi: killing requests for dead queue
scsi: killing requests for dead queue
scsi: killing requests for dead queue
scsi: killing requests for dead queue
scsi: killing requests for dead queue
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
procmk_init
dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (bm750)
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
brcm_demux_init: $Id: bcm7335_demux.c,v 0.6 $
[VID]: <6>bcm7335_video_init
[AUD]: <6>bcm7335_audio_init
DVB: registering adapter 0 frontend 0 (BCM7335 FE)...
DVB: registering adapter 0 frontend 0 (BCM7335 FE)...
[MPVR]: >> misc_pvr_init
input: dreambox advanced remote control (native) as /devices/virtual/input/input1
[LCD]: registered
[CI]:-BM750_PCB_2_1

[CI]: registered ci0
[CI]: registered ci1
[DFP]: registered dbox fp
[DFP]: bcm7335_i2c_write: Error 1114113

[DFP]: bcm7335_max_i2c_write: Error 1114113

[DFP]: Scart 4707 is found 4

[SC]: registered sci0
[SC]: registered sci1
system_time_set wakeup mode get
system_time_set wakeup mode get 0xc1
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
af9013: firmware version:4.95.0.0
DVB: registering adapter 1 frontend 0 (Afatech AF9013 DVB-T)...
tda18271 0-00c0: creating new instance
TDA18271HD/C2 detected @ 0-00c0
Registered IR keymap rc-msi-digivox-ii
input: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/rc/rc0/input2
rc0: IR-receiver inside an USB DVB receiver as /devices/platform/ehci-brcm.1/usb2/2-1/rc/rc0
dvb-usb: schedule remote query interval to 500 msecs.
dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9015
Adding 131068k swap on /media/usb/swapfile.  Priority:-1 extents:3 across:143356k
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1  
[VID]: VIDEO_PLAY 1  2 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  
NET: Registered protocol family 10
DVB: registering adapter 0 frontend 0 (Sundtek DVB-C (0/0))...
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1  
[VID]: VIDEO_PLAY 1  2 0
[VID]: VIDEO_CONTINUE 1  1
[VID]: VIDEO_CLEAR_BUFFER 1  1 0
[VID]: VIDEO_STOP 0  1
[VID]: VIDEO_SELECT_SOURCE 0  
eth0: no IPv6 routers present
[CI]:ci_dev_open

[CI]:Opening A GPIO's for 7335 platform

[CI]:Opening A GPIO's for 7335 platform....done

[CI]:entering.. A NEXUS_DvbCi_Open

[CI]:NEXUS_DvbCi_Open done..

[CI]:Installing callbacks

[CI]:Forcing card check

[CI]:Card insertion status changed

[CI]:Opening B GPIO's for 7335 platform

[CI]:Opening B GPIO's for 7335 platform....done

[CI]:entering.. B NEXUS_DvbCi_Open

[CI]:NEXUS_DvbCi_Open done..

[CI]:Installing callbacks

[CI]:Forcing card check

[CI]:Card B insertion status changed

[CI]: CI interface initialised

[CI]:ci1_dev_open

[CI]:NEXUS_Remux_Start CI0 0 0

[CI]:>>close_mpod tuner:0

[CI]:remux stop

[CI]:get_remux_startcnt() count : 1

[CI]:get_remux_startcnt() count : 1

[CI]:>>close_mpod tuner:1

[CI]:remux stop

[CI]:get_remux_startcnt() count : 0

[CI]:get_remux_startcnt() count : 0

tda18271: performing RF tracking filter calibration
tda18271: RF tracking filter calibration complete
DVB: registering adapter 0 frontend 0 (Sundtek DVB-C (0/0))...
CIFS VFS: default security mechanism requested.  The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.2
sh: page allocation failure: order:0, mode:0x20
Call Trace:
[<805760f8>] dump_stack+0x8/0x34
[<80087524>] warn_alloc_failed+0xe4/0x12c
[<80089724>] __alloc_pages_nodemask+0x148/0x650
[<80577368>] cache_alloc_refill+0x368/0x658
[<800bc4ec>] kmem_cache_alloc+0xe0/0x104
[<800446a4>] __sigqueue_alloc+0xa8/0x26c
[<8004616c>] __send_signal.constprop.22+0x254/0x2b8
[<800475b0>] do_notify_parent+0x13c/0x1c0
[<80038b58>] do_exit+0x50c/0x764
[<80038e34>] do_group_exit+0x4c/0xd0
[<80038ecc>] __wake_up_parent+0x0/0x18

Mem-Info:
Normal per-cpu:
CPU    0: hi:   90, btch:  15 usd:  78
CPU    1: hi:   90, btch:  15 usd:  78
active_anon:8625 inactive_anon:8678 isolated_anon:0
 active_file:2850 inactive_file:6444 isolated_file:31
 unevictable:0 dirty:0 writeback:0 unstable:0
 free:992 slab_reclaimable:1105 slab_unreclaimable:2158
 mapped:3772 shmem:33 pagetables:124 bounce:0
Normal free:3968kB min:20480kB low:25600kB high:30720kB active_anon:34500kB inactive_anon:34712kB active_file:11400kB inactive_file:25776kB unevictable:0kB isolated(anon):0kB isolated(file):124kB present:260096kB mlocked:0kB dirty:0kB writeback:0kB mapped:15088kB shmem:132kB slab_reclaimable:4420kB slab_unreclaimable:8632kB kernel_stack:856kB pagetables:496kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:33 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 48*4kB 86*8kB 43*16kB 41*32kB 9*64kB 0*128kB 2*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 3968kB
9352 total pagecache pages
7 pages in swap cache
Swap cache stats: add 73, delete 66, find 1/2
Free swap  = 130812kB
Total swap = 131068kB
65536 pages RAM
30997 pages reserved
7032 pages shared
28583 pages non-shared
[AUD]: AUDIO_SET_MUTE 0
[AUD]: AUDIO_SET_MIXER -2026095120
[AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
[AUD]: AUDIO_SET_MIXER : next left volume 0, right volume 0
[AUD]: AUDIO_SET_MIXER : next left volume -200, right volume -200
[AUD]: AUDIO_SET_MIXER -2026095120
[AUD]: AUDIO_SET_MIXER : amixl 51, amixr 51
[AUD]: AUDIO_SET_MIXER : next left volume -200, right volume -200
[AUD]: AUDIO_SET_MIXER : next left volume -3842, right volume -3842
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6896080
[AUD]: AUDIO_PLAY 6896080 decoder start : 0
[VID]: VIDEO_GET_SIZE src w: 1280 h:720 display w:1280 h:720
[VID]: VIDEO_GET_SIZE aspect: 1 6
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 6896080  0
[VID]: VIDEO_PLAY 6896080  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6896080  1
[AUD]: AUDIO_CONTINUE 6896080 1 audio pid_hndl : 0xc0b5b0dc
[AUD]: setting mute : 0
[AUD]: AUDIO_CHANNEL_SELECT 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP 6896080
[AUD]: AUDIO_CONTINUE 6896080 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6896080
[AUD]: AUDIO_PLAY 6896080 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 6896080  0
[VID]: VIDEO_PLAY 6896080  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6896080  1
[AUD]: AUDIO_CONTINUE 6896080 1 audio pid_hndl : 0xc0b5b0dc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP 6896080
[AUD]: AUDIO_CONTINUE 6896080 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
EXT4-fs (sda1): error count: 1189
EXT4-fs (sda1): initial error at 1343820535: ext4_mb_generate_buddy:738
EXT4-fs (sda1): last error at 1380375723: ext4_mb_generate_buddy:738
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6896080
[AUD]: AUDIO_PLAY 6896080 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 6896080  0
[VID]: VIDEO_PLAY 6896080  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6896080  1
[AUD]: AUDIO_CONTINUE 6896080 1 audio pid_hndl : 0xc0b5b0dc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP 6896080
[AUD]: AUDIO_CONTINUE 6896080 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6896080
[AUD]: AUDIO_PLAY 6896080 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 6896080  0
[VID]: VIDEO_PLAY 6896080  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6896080  1
[AUD]: AUDIO_CONTINUE 6896080 1 audio pid_hndl : 0xc0b5b0dc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP 6896080
[AUD]: AUDIO_CONTINUE 6896080 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
[AUD]: AUDIO_SET_BYPASS_MODE 1
[AUD]: downmix 0 state : 0
[AUD]: AUDIO_PAUSE 6896080
[AUD]: AUDIO_PLAY 6896080 decoder start : 0
[VID]: VIDEO_SET_STREAMTYPE 1
[VID]: VIDEO_FREEZE 6896080  0
[VID]: VIDEO_PLAY 6896080  5 2
[VID]: VIDEO_SLOWMOTION 0    1
[VID]: VIDEO_FAST_FORWARD 0    1
[VID]: VIDEO_CONTINUE 6896080  1
[AUD]: AUDIO_CONTINUE 6896080 1 audio pid_hndl : 0xc0b5b0dc
[AUD]: setting mute : 0
[VID]: VIDEO_STOP 1  1
[AUD]: AUDIO_STOP 6896080
[AUD]: AUDIO_CONTINUE 6896080 0 audio pid_hndl : 0x0
[AUD]: AUDIO_CONTINUE:bcm7335->audio_pid_hndl is null 0 0
DVB: adapter 1 frontend 0 frequency 122000000 out of range (174000000..862000000)
DVB: adapter 1 frontend 0 frequency 130000000 out of range (174000000..862000000)
DVB: adapter 1 frontend 0 frequency 146000000 out of range (174000000..862000000)
DVB: adapter 1 frontend 0 frequency 154000000 out of range (174000000..862000000)
DVB: adapter 1 frontend 0 frequency 162000000 out of range (174000000..862000000)
DVB: adapter 1 frontend 0 frequency 170000000 out of range (174000000..862000000)
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
tda18271_set_params: [0-00c0|M] bandwidth not set!
af9013: invalid bw or clock
root@vuduo:~#

[betacentauri]

fyi http://openpli.org/f...ndpost&p=376624

[sundtek]

fyi http://openpli.org/f...ndpost&p=376624

 

I guess openpli mixes up the frontend allocation once someone registers vtuner1 first and afterwards vtuner0

Registering vtuner1 will probably bind it to /dev/dvb/adapter0/frontend1 (maybe 2) while vtuner0 will bind it to frontend2 (maybe 3).

We added some identifier to the frontend name to be able to match up /dev/dvb/adapterX/frontend0 with /dev/dvb/adapter0/frontendY

[pop_eye]

Registering vtuner1 will probably bind it to /dev/dvb/adapter0/frontend1 (maybe 2) while vtuner0 will bind it to frontend2 (maybe 3).

We added some identifier to the frontend name to be able to match up /dev/dvb/adapterX/frontend0 with /dev/dvb/adapter0/frontendY

 

Actually the dvb-core should take care properly of the dvb adapters numbering. I guess you are missing this functionality in the driver.

Not sure why you need to do binding inside of the driver when kernel module  should be taking care of that.

I understand driver is not open source. Too bad.

Edited by pop_eye, 30 September 2013 - 17:50.

[sundtek]

Registering vtuner1 will probably bind it to /dev/dvb/adapter0/frontend1 (maybe 2) while vtuner0 will bind it to frontend2 (maybe 3).

We added some identifier to the frontend name to be able to match up /dev/dvb/adapterX/frontend0 with /dev/dvb/adapter0/frontendY

 

Actually the dvb-core should take care properly of the dvb adapters numbering. I guess you are missing this functionality in the driver.

Not sure why you need to do binding inside of the driver when kernel module  should be taking care of that.

I understand driver is not open source. Too bad.

 

[ ] you have no idea what you are writing about.

our dongles can also be used via network (eg. from a NAS server, Router, upcoming even windows). There's no kernel Module available for doing that (and it would even be useless to work around that one).

Aside of that we are only using interfaces which were designed to be used on Linux.

Obviously we probably submitted more code to the kernel as you ever did in your life and are still helping to improve the USB performance.

Plus that said we have signed various NDAs with Chip vendors which guarantees active support for all chipsets we use and thus we also keep our drivers up to date. And to clarify what NDA means Non disclosure agreement, so we are not even allowed to disclose anything.

 

We forwarded the issue to VU+ that vtuner nodes shouldn't be allowed to be opened multiple times, I think this is one problem I read on this forum.

Edited by sundtek, 30 September 2013 - 19:33.

[sundtek]

Aside of that if you want more or less perfect integration of external tuners (by using a plugin interface)

 

You can have a look at that openpli patch which has been done within 2012

 

http://sundtek.de/su.../e2-plugin.diff

[pop_eye]

 

Registering vtuner1 will probably bind it to /dev/dvb/adapter0/frontend1 (maybe 2) while vtuner0 will bind it to frontend2 (maybe 3).

We added some identifier to the frontend name to be able to match up /dev/dvb/adapterX/frontend0 with /dev/dvb/adapter0/frontendY

 

Actually the dvb-core should take care properly of the dvb adapters numbering. I guess you are missing this functionality in the driver.

Not sure why you need to do binding inside of the driver when kernel module  should be taking care of that.

I understand driver is not open source. Too bad.

 

[ ] you have no idea what you are writing about.

our dongles can also be used via network (eg. from a NAS server, Router, upcoming even windows). There's no kernel Module available for doing that (and it would even be useless to work around that one).

 

No problem - I stand corrected.

Then please tell why an opensource dongle driver is working properly with the also closed source vuplus driver.

Except that they are using opensource dvb-core to control the functionality.

Why should they adapt around your closed source driver ?

It`s your product...not mine. Myself I will rather buy opensource dongle instead, if it cannot work properly.

Edited by pop_eye, 30 September 2013 - 19:55.

[pop_eye]

Aside of that if you want more or less perfect integration of external tuners (by using a plugin interface)

 

You can have a look at that openpli patch which has been done within 2012

 

http://sundtek.de/su.../e2-plugin.diff

 

I really doubt you can find this in current openpli code.

I can see you hardcoded the adapter number in your patch. Is this a requirement of your driver ?

 

 

/*
+         * Some frontend devices might have been just created, if
+         * they are virtual (vtuner) frontends.
+         * In that case, we cannot be sure the devicenodes are available yet.
+         * So it is safer to scan for sys entries, than for device nodes
+         */
+        snprintf(filename, sizeof(filename), "/dev/dvb/adapter0/frontend%d", num_fe);

Attached Files

•  dvb.cpp.txt   55.86KB   2 downloads

Edited by pop_eye, 30 September 2013 - 20:07.

[pop_eye]

@westisib

 

I also noticed your vu-duo is failing with i2c writting. Strange behaviour.

 

[DFP]: bcm7335_i2c_write: Error 1114113

[DFP]: bcm7335_max_i2c_write: Error 1114113

[westsib]

I do not know whether that strange or not.
Unfortunately, I am not an expert
Where exactly is a mistake? On PLi, Sundtek or Vu +?
What else should I set?

[sundtek]

 

 

Registering vtuner1 will probably bind it to /dev/dvb/adapter0/frontend1 (maybe 2) while vtuner0 will bind it to frontend2 (maybe 3).

We added some identifier to the frontend name to be able to match up /dev/dvb/adapterX/frontend0 with /dev/dvb/adapter0/frontendY

 

Actually the dvb-core should take care properly of the dvb adapters numbering. I guess you are missing this functionality in the driver.

Not sure why you need to do binding inside of the driver when kernel module  should be taking care of that.

I understand driver is not open source. Too bad.

 

[ ] you have no idea what you are writing about.

our dongles can also be used via network (eg. from a NAS server, Router, upcoming even windows). There's no kernel Module available for doing that (and it would even be useless to work around that one).

 

No problem - I stand corrected.

Then please tell why an opensource dongle driver is working properly with the also closed source vuplus driver.

Except that they are using opensource dvb-core to control the functionality.

Why should they adapt around your closed source driver ?

It`s your product...not mine. Myself I will rather buy opensource dongle instead, if it cannot work properly.

 

I don't even know what your problem is, our devices work very well for most people out there.

[sundtek]

Aside of that if you want more or less perfect integration of external tuners (by using a plugin interface)

 

You can have a look at that openpli patch which has been done within 2012

 

http://sundtek.de/su.../e2-plugin.diff

 

I really doubt you can find this in current openpli code.

I can see you hardcoded the adapter number in your patch. Is this a requirement of your driver ?

 

 

/*
+         * Some frontend devices might have been just created, if
+         * they are virtual (vtuner) frontends.
+         * In that case, we cannot be sure the devicenodes are available yet.
+         * So it is safer to scan for sys entries, than for device nodes
+         */
+        snprintf(filename, sizeof(filename), "/dev/dvb/adapter0/frontend%d", num_fe);

 

The virtual ones (using vtuner) always register within adapter0.

[pop_eye]

@sundtek

I have no problem with you - except trying to help out.

In the same time I also gain some more knowledge -  BTW you got pm.

[sundtek]

@sundtek

I have no problem with you - except trying to help out.

In the same time I also gain some more knowledge -  BTW you got pm.

 

Maybe someone else is also interested in this, we have some vtuner module for SH4 based settopboxes.

At the first stage we're trying to improve support for it, once our new devices are available the module will be officially released so image groups can take over maintainance for it.

 

Our drivers already have support for SH4 for a long time, but the vtuner interface on SH4 STBs was missing.

This also means that other STB companies can reference to this upcoming vtuner module, and possibly improve support for their implementation.

 

References:

http://www.dbox2-tun...92&hilit=vtuner

http://support.sundt...6.html#msg10296