120 replies to this topic

[jpuigs]

I don't have it either.

[CescoAiel]

I only have a single box that's on that list (Golden Interstar Xpeed), so I'm not gonna complain... Just means I need to go look for a new small box for the bedroom TV Cabinet...  *shrugs*

For all the efforts the team put in to building ever better images, I can only be thankful, so replacing an old box once in a while...

So go for it guys! 

[WanWizard]

The current OpenPLi will remain available, so as long as the box does what you want it to do, no need to replace it, I think.

[CescoAiel]

The current OpenPLi will remain available, so as long as the box does what you want it to do, no need to replace it, I think.

True, but I try to keep all the tuners I work with (Also the ones at parents) on the same image to keep it simple... And it gives me an excuse to look for a new toy to play with! 

 

[Alex_NL]

Not as much stir and complaints as I expected. Nobody really minds that we stop building for these brands for release 8?

I just read this now, and it would be nice if my Xtrend ET10000 could run version 8, but without the manufactors' support I understand this will be difficult?

[rantanplan]

You would have to know what is meant by version 8?
In addition, which OE core should then be worked on.

sumo?

Thud?

Warrior?

In principle, the images of the Xtrend boxes are all flawless to build from every conceivable OE core.
Building a VU + image, on the other hand, looks very different because of the closed source stuff.

But they will continue to be supported?
So it's more a question of what you still feel like doing.

[littlesat]

Zeus!

[WanWizard]

There are two different issues:

1. hardware that is no longer capable of running the image, due to the limited flash size
2. hardware for which BSP updates are needed to get the image running again

This first one is a hard limit, if it doesn't fit, it doesn't fit. We are not going to make different (stripped) images to address this.

 

The second one requires support from the manufacturer.

 

Unlike some other images, we require the manufacturer the maintain the BSP, both because we're not in the business of increasing the profit of the manufacturer, and they are the only party that know the ins- and outs of both hardware and drivers.

 

You could argue that BSP adaptations for OE updates could be done, but we don't have people with the time, the skills and the will to take this on.

[rantanplan]

You cannot accuse a manufacturer like Xtrend of profit addiction.
Rather the other way around and that's why they are now broke.
They did a lot for e2 and have been committed for a long time.
In principle, always provided excellent drivers.
However, the Sec-Board story was uncomfortable.
Keeping the image of such former manufacturers running is somehow a question of style.
At VU + I can't see a good style on the part of the manufacturer.
Dreambox not at all.
But maybe I just see it as 'human'.
An image construction is certainly also possible separately for everyone who deals a little with the construction.

If it gets zeus ...
Let's see what comes.
greetings

[WanWizard]

For my second point it doesn't really matter (from our point of view) whether the manufacturer doesn't want to update the BSP anymore (for example because the box is EOL and no longer generates a profit) or can't (because like Xtrend they no longer exist).

 

Either way, if the image no longer builds, it is end of story.

[rantanplan]

Building an image is always possible, that's for sure.
Except for example at VU + because you then lack the sources that you have locally.
Then the normal user has to trick a bit and unfortunately get by without the source.
But I totally understand the side of you.
Was it indicated that the layer could also be maintained by other users?
This is not uninteresting and would be new.
Then some layers would definitely be added and you would have more to do with the e2.

But as I said...
Wait and be fine
greetings

[WanWizard]

Building an image is always possible, that's for sure

 

Not really, most of the BSP's need modifications to make them compile in Zeus.

 

Was it indicated that the layer could also be maintained by other users?
This is not uninteresting and would be new.
Then some layers would definitely be added and you would have more to do with the e2.

 

It is something we might want to consider, (end)users should not be punished because the manufacturer of their STB can't or won't maintain it anymore.

 

Obviously, there still won't be any manufacturer support for drivers and other manufacturer supplied files (USB devices, HbbTV binaries, etc), so like other EoL images we build, they would come with a limited guarantee...

[boki15]

However, the Sec-Board story was uncomfortable.

I remember hyping this discussion for ET4000, in fact, Xtrend resolved the issue with sec-board for ET4000 if I remember well. I know a lot people using et4000 with openpli and they still use it, provides still good picture. OpenPli provided also updated images for obsolete images in past if time for that was found, like christmas. I update those et's from time to time, it's not best device for streaming, but hey, even dm500s with broken lan and openpli will stream all non HD channels which  are still majority of all available worldwide and they work with old Pli Images too. People should not be scared as long as downloads for older images exist.

[neo]

It this still a thing?

 

I've been offline for quite a while due to poor health, but things seem to be on the up again, and I wouldn't mind picking this up, providing the community is willing to bail this old sod out every now and then, and chip in when needed.

[Erik Slagter]

This is definitely still a thing. We need to have patched BSP's for the next major release (8.0) so it would really help.

 

In the past some people have been very helpful for specific BSP adjustmens that need some level of insight, so I guess (and hope) that will continue 

Edited by Erik Slagter, 2 May 2020 - 16:32.

[neo]

Ok, cool.

 

How do we progress? I see the meta submodules in openpli-oe-core point to repositories of several github users (vendors? maintainers?), and I see a lot of meta-.... repositories under OpenPLi.

 

Do I use those? Do I setup something else? Which ones do I setup? Who needs which rights where?

[WanWizard]

Maybe up front a recap of what is needed, to avoid any misunderstanding:

 

The issue at hand is the lack of maintenance on BSPs from vendors that are out of business, or contain only end-of-life hardware that the vendor isn't intrested in maintaining anymore. For both groups of hardware, we would like to continue building OpenPLi for as long as technically possible, without compromises, for the users that have this hardware and would like to continue using OpenPLi.

 

For hardware newly introduced (to OpenPLi), we still require direct vendor maintenance and vendor support, so we explicitly are not looking to increase the number of BSPs or support additional hardware this way.

 

As to your questions, my personal 2ct's:

 

The meta repo's in the OpenPLi organisation are used by us for development of the next major release, as a place to store WIP in BSPs (we can't use branches, as we have no access to vendor BSPs). We would like to keep those separate from the BSPs we build from.

 

So it is probably the best to create a separate github account for it.

As for its name and description, for me it is ok to show these repo's are meant to be used by OpenPLi, but it must be clear we (as the OpenPLi team) don't maintain them, it is a community effort. So don't call it OpenPLi-BSPs or so...

Note that individual OpenPLi team members, on personal title, are also community members, so obviously they can send in PR's too...

 

Ideally we would you to keep an eye on githubs notifications and check for new PRs. When new ones come in, validate them before you merge them, as errors will cause the develop builds to crash. If possible, do this daily or every other day, so developers don't have to wait for required changes too long... And obviously, use your own skills for maintenance and reported issues, if possible.

 

I personally don't need rights, I prefer sending in PRs, if only because 4 eyes see more than 2.

 

BSPs that need a new home: meta-dream, meta-gi, meta-miraclebox, meta-sab, meta-spycat, meta-xpeedc and meta-xtrend.

 

Anyone else wants to toss their cents on the table?

Edited by WanWizard, 3 May 2020 - 00:05.
added bsp list

[Erik Slagter]

+1 

 

Completely agree.

 

Neo, are you up for it? 

[WanWizard]

Can we stay on topic here please? The OE branch used is not relevant to the issue at hand.

[Frenske]

I have hidden the three replies that are off topic.