oe-alliance / oe-alliance-core

The openembedded alliance core.
GNU General Public License v2.0
163 stars 175 forks source link

Strange colours on front panel LCD (GigaBlue Quad Plus) since driver update (8e2ab69) #301

Closed outrageuk closed 6 years ago

outrageuk commented 6 years ago

Strange colours on front panel LCD (GigaBlue Quad Plus) since driver update.

https://www.world-of-satellite.com/showthread.php?59392-Strange-colours-on-front-panel-after-latest-driver-update

atvcaptain commented 6 years ago

vix team must change e2 code, no issue:

ViX-Sicilian commented 6 years ago

Theres nothing in our configure.ac for this.

Do we need these commits?

https://github.com/openatv/enigma2/commit/b0e17f7d6499bfad4f5fc0a55d16737988550b70#diff-295386107bd1763beba0be67031b8fa1

Anything else we need?

betacentauri commented 6 years ago

I guess this is not needed anymore: https://github.com/OpenViX/enigma2/blob/master/lib/gdi/lcd.cpp#L305-L315

ViX-Sicilian commented 6 years ago

That code is still in OpenATV lcd.cpp, so can anyone please advise exactly what we need to cherry pick.

betacentauri commented 6 years ago

Afaik all gigablue boxes don't need the workaround any longer. Workaround was deactivated here: https://github.com/openatv/enigma2/commit/1ba3e5601decb8b1b4eb0a9ae6d3ac94d7fcbab0#diff-67e997bcfdac55191033d57a16d1408a https://github.com/openatv/enigma2/commit/14a9a1d2bdeb7160665b90d8116d0151df1e69ab#diff-67e997bcfdac55191033d57a16d1408a ATV uses the workaround also for other boxes. It looks like you not. So I think you can remove the code.

betacentauri commented 6 years ago

Sorry closed accidentially

arn354 commented 6 years ago

if you build for gb7325 (old models) - then you need that part and you have to modify it like openatv or teamblue. gb7325 - still require that code section. gb7358, gb7362, gb73625, gb7356, gb7252 - no longer need that color switching in E2.

ViX-Sicilian commented 6 years ago

We no longer build the gb7325 models, so should be ok.

outrageuk commented 2 years ago

I seem to have this same problem again since updating for 5.2.

OpenVIX 6.2.006

Has this fix been removed in new builds for some reason?