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.