107 replies to this topic

[schneider87]

hi

please update drivers for usb turbo tuner 

 

thanks

[Erik Slagter]

They have been in the image for some time. See changelog (git commit log).

[Huevos]

Do any of the PLi team members actually have the device and have checked that it works in the image?

Edited by Huevos, 27 May 2015 - 08:26.

[Dimitrij]

https://github.com/v...vuplus/issues/4

Or I'm wrong?

[Huevos]

I'm asking if anyone has tested the device. I'm only asking because I don't have a sample.

 

Why did ATV need these changes to get it working?

https://github.com/o...f2f7b218e255134

[Erik Slagter]

Indeed, we don't have them.

[littlesat]

I'm afraid we do not accept this part....

 

from boxbranding import getMachineBrand

Edited by littlesat, 27 May 2015 - 14:43.

[Dimitrij]

I'm afraid we do not accept this part....

 

from boxbranding import getMachineBrand

if getBoxType().startswith('vu')

It's very easy

[littlesat]

I understand how it works, but It is not as it should be in code... We intend to prevent from these kind of checks as far as possible....

[Dimitrij]

This patch will solve this bug here http://forums.openpl...ndpost&p=479418

[Huevos]

I'm afraid we do not accept this part....

 

from boxbranding import getMachineBrand

I don't see that used anywhere in that py. Not sure why the import is there.

[Dimitrij]

+				if getMachineBrand() in ('Vu+'):
+					skip_t2 = True

Edited by Dimitrij, 27 May 2015 - 19:57.

[littlesat]

getMachineBrand is used to check if the box is a VU box and do some other stuff in E2 when used in a VU box. in fact I think this is not the way it should be done in a general enigma2 code... It should switch on feature, not on Brand.

 

I know there are still some places were some kind of stuff is still somehow included in our E2 (more as left-over) ... but still we should avoid it as far as possible.... E.g. when ET or another Brand at a feature than we can get complete lists of if brand x or brand y or brand z... enz... At the end difficult to cover and maintain... (it looks simple in the beginning but...)

 

And I also know OE-A did introduce this getMachineBrand stuff to be able to check for possible (non)features and perform work-a-rounds for specific Brands in the Enigma2 code... But still I think we should keep this out of E2. There are better or other ways to do this kind of stuff... e.g. check/switch for (non)features instead... 

Edited by littlesat, 27 May 2015 - 20:02.

[Huevos]

Well we might as well put this on hold until one of us has the device.

[Dimitrij]

Most requested.
Let's all still apply this patch.

https://github.com/o...f2f7b218e255134

[bacicciosat]

We have turbo tuners.

They are working without the patch but there are issues with DVB-C scan.

 

Open Black Hole and Pli enigma2 ScanSetup are about the same. There is only a little patch to fix Dvb-C/T tuner detection.

http://git.vuplus-co...e60ef913a333a03

 

To add drivers in the image is simply, you can find everywere and in OBH meta-vuplus folder.

Only remember that additional kernel module firmware is needed.

Here is the example:

vuplus-tuner-turbo \

....

${@base_contains('PREFERRED_VERSION_linux-vuplus', '3.13.5', 'kernel-module-cypress-firmware', '', d)} \
${@base_contains('PREFERRED_VERSION_linux-vuplus', '3.9.6', 'kernel-module-dvb-usb-cypress-firmware', '', d)} \

 

[Erik Slagter]

Then VU+ should fix the issues instead of relying on us to workaround them.

Edited by Erik Slagter, 29 May 2015 - 08:57.

[bacicciosat]

Then VU+ should fix the issues instead of relying on us to workaround them.

 

There are various commits in Vu+ enigma2 git about scansetup and Turbo

 

2015-04-22     hschang    [ScanSetup] Fix error on complete scan with T2 tuners. vuplus_experimental     commit | commitdiff | tree | snapshot
2015-04-16     hschang    [ScanSetup] fix TT3L10 automatic scan problem.     commit | commitdiff | tree | snapshot
2015-02-17     hschang    [ScanSetup] Fix DVB-T2 Scan when tuner does not have...     commit | commitdiff | tree | snapshot
2015-02-16     hschang    [ScanSetup] Support VUPLUS TURBO automatic scan.     commit | commitdiff | tree | snapshot

 

I have not Cvb-C and cannot test but Ev0 have it and it seems that the changes doesn't fix the issues.

The problem with Vu+ is that they are too much slow in updating and fixing for this reason we don't use their meta-vuplus module in OBH

It is much better to fix and update by yourself than to wait and wait and wait and become old and frustrating....

 

If you need any kind of test i can ask to Ev0 to help.

[Erik Slagter]

I really don't care if VU+ workarounds it in enigma or we do it. It's not the right way. All tuners should be driven equally according to api rules. We can't begin making exceptions for every tuner. VU+ simply must supply a driver that enables enigma to treat it as any other tuner.

[bacicciosat]

yes you are right Erik.