29 replies to this topic

[borgorosso]

In download there is only image for DM 7020HD, work good with DM 7020HD v2?

[littlesat]

No.

[borgorosso]

_{Where is it image for Dm7020 HD v2?}

Edited by borgorosso, 8 March 2017 - 13:46.

[Frenske]

We don't build for all newer Dreamboxes. Sorry.

[Lost in Space]

well if you know somebody with a v1 it is only backup/restore, as dFlash allows conversion of the backup to the new flash chips of the v2

 

second alternatvie would be to use Barry Allen to boot the v1 image on a v2 box - but then you will need to install a Dream OE2.0 imagae in Flash.

 

third alternative - use OpenATV Images

 

best Alternative ... use OE 2.0 original images

[littlesat]

and the fith solution......?

Edited by littlesat, 8 March 2017 - 23:22.

[SpaceRat]

One solution is always ...

[mimisiku]

That's a bit radical... The box performs well so why bin it?

[SpaceRat]

Because it's always an option.

My choice would be OpenATV, but that option was already listed and littlesat asked for a different/fifth one.

Gesendet von meinem Siemens C25 mit Tapatalk

[littlesat]

You can also sell the 7020HDv2... and get a newer box from a manufacturer that is still supporting real open source.... Sorry I really do not understand why OpenATV is still supporting these boxes.. This does not help the opensource community at all... Keeping supporting them means they can still sell boxes without feeling the consequences of their decision. It does not give any signal or motivation of reconsidering the decision they made...

 

Of course it might be a huge promotion for OpenATV as they continue to support it.. But is this in solidarity with the opensource minded community?

 

With the decision of Dream Multimedia to abandon open source for their STB’s, our motivation for dealing with the consequences of that has dwindled.

 This has gotten to the point that we are no longer willing to apply Dream Multimedia specific patches, which is why we do not support their v2 STB hardware.

Because current OpenPLi users with Dream Multimedia STB’s expect support from us, we feel the need to make our position clear.

We have decided that:

– We will stop fixing Dream Multimedia specific bugs for existing DMM boxes;
– We will not support the “v2” series of Dream Multimedia STB hardware, like the 7020HDv2 and 800SEv2;
– We will not support future Dream Multimedia STB hardware they may release;

The Dream Multimedia hardware currently supported by OpenPLi will remain active in our automated build environment, which means images will be generated and feeds will remain available, until we get to a point that this is no longer possible without intervention. At that point, we will effectively stop with all support.

Since OpenPLi is open source and available to anyone, feel free to setup your own build environment, and produce images for Dream Multimedia hardware yourself, “Based on OpenPLi”.

 

https://openpli.org/...ultimedia-stbs/

Edited by littlesat, 9 March 2017 - 12:06.

[Lost in Space]

Real Open Source ... interesting ... it this the same as "Real News" ... the Donald T. way ?

[littlesat]

It has nothing to do with trump... It is a real dmm closed the c++ sources... yes this is not fake news... This is really not fake news....dmm sucks... Dmm really socks by closing the c++ soirces. Yes they do... And yes I feed a troll again... Yes I feed a real big fat troll... Indeed a fat troll... It is a troll!

Edited by littlesat, 9 March 2017 - 21:26.

[Lost in Space]

VTi Images are now also Closed source C++ core and their driver support for the community is sh*y - do you now drop support for VU+ too

 

It is like building walls to Mexico, you then move to Kanada and then you buy some air craft carriers for the coast line ...

 

And you should be carefull in calling people trolls ... or live with the consequences ...

Edited by gutemine, 9 March 2017 - 21:32.

[athoik]

The example is completely irrelevant. Remember that VU+ is OpenPLi supported because there is a "line" open.

On the other hand DMM, not only there is no line open, nobody ever tried to fix, the dropped line.

OpenPLi still procuding DMM images, although official support (from DMM) stop ages ago.


Now be smart and find another irrenlevant answer... "trollmine"....

Edited by athoik, 9 March 2017 - 22:08.

[Lost in Space]

People who talk about lines during parties ... normally go to the bathroom to consume them ...

 

Enjoy what ever you are ... doing ...

[littlesat]

And gutemine has always the last word... Really always, without exceptions... And littlesat lies, tell fake news, nothing else then fake, real fake... Yes it's fake!

Edited by littlesat, 9 March 2017 - 23:08.

[ims]

I do not know why unnamed troll has problem, that v2 and newer dmm's boxes are not supported by Pli ... 

 

Graphomania ?

[SpaceRat]

VTi Images are now also Closed source C++ core and their driver support for the community is sh*y - do you now drop support for VU+ too

Uhm, I think VTi images have never been open source. Hey, they aren't even in compliance with the original E2 license.

They steal features from the open source community (I could identify quite some changes inside their changelog which are 1:1 previous commits of mine to the oe-a core, probably there are more changes which they considered too minor to list in the changelog) but do not publish their sources.

On the other hand, VTi is only de facto the Vu+ default image, not de jure.
Officially, the crap built from OpenVuplus is the vendor's default image and that part is open source.


About DMM on the other hand:
They are providing about the same support to the open source teams as any other vendor ... you can get the drivers and if you beg friendly they might even fix bugs.
The only difference in comparison with other vendors is that they really once initiated/participated in the E2 development, but the license always made clear they can stop that any time.

But is there any other vendor paying at least a half full-time coder for E2 development?
Someone who compiles new drivers from time to time or develops patches for E2 that do nothing but make E2 work with driver quirks doesn't count.
I mean someone who really gets paid at least 50% of his work-time for dvbapp2/enigma2 development.

[littlesat]

Why do you think we introduced BSP layers - this forces them at least to somehow contribute. And that is also why we avoid as much as possible "if brand x then do y" commits...-so- they must contribute -or- at least try to be compatible.

 

 

 

But is there any other vendor paying at least a half full-time coder for E2 development?

But it seems the OE-A community does help here to force them to at least minimally contribute because they accept these kind of patches and work-a-rounds and create/support/maintain the BSP layer fro them... (I hope you might really understand now what I mean here).

 

DMM did closed the doors on the c++ part of enigma2 as soon competition appeared.... And with this they did stop supporting the opensource community that also made them big. And just on that part that is most interesting for this opensource community, Indeed they did the most work on the development of E2 (and Enigma1) on the first place, I can not argue this... 

 

VTi is indeed a kind of "pirate" image... They voilating all the (GPL) licenses and as they are closed source you can even not prove what they steal from the OpenSource community. And then they are also the only ones that allow MediaPortal plugin on VU boxes. That is ridiculous, really ridiculous at the current date...

 

There is also a website offering fake genuine DMM images on OpenPLi we do not support.... But as you sometimes can read on this forum - without guarantee and support form the real genuine OpenPLi team...

Edited by littlesat, 10 March 2017 - 12:17.

[SpaceRat]

But it seems the OE-A community does help here to force them to at least minimally contribute because they accept these kind of patches and work-a-rounds and create/support/maintain the BSP layer fro them... (I hope you might really understand now what I mean here).ones that allow MediaPortal plugin on VU boxes. That is ridiculous, really [/size]ridiculous at the current date...[/size]

oe-a basically takes the bsp-layers and maintains an own mirror of them inside oe-alliance-core/meta-brands.

That makes us more flexible when it comes to kernel configs.
We ourself can decice if we want to give building iptables modules inside kernel x a try or not.
Or we can simply enable the USB serial modules, compare https://forums.openp...ix-card-reader/

But basically, what's inside oe-alliance-core/meta-brands/meta-brandx should match what's in brandx' bsp.