486 replies to this topic

[twol]

Glad to see OpenPli now completely support the sf8008 in all  modes..........

 

https://www.world-of...K-UHD-E2-Models

[WanWizard]

Not completely finished though, the multiboot is being reworked so it works the same as for the other HiSil boxes.

[littlesat]

means no sd required for multiboot (and other image builders might remove some code?)

[twol]

means no sd required for multiboot (and other image builders might remove some code?)

.... and you do realise that OE-A images only see upto partition 13 (12 kernel, 13 root) and your new fancy meta wants to use 12/13/14/15  for kernel and 16 for the roots which cannot be seen by OE-A ?? ..... or have you thought of some kluge to get round this??

 

As for SD - USERS have been using this for 18 months - but of course users are not important??

Edited by twol, 26 March 2020 - 10:57.

[littlesat]

.... and you do realise that OE-A images only see upto partition 13 (12 kernel, 13 root) and your new fancy meta wants to use 12/13/14/15  for kernel and 16 for the roots which cannot be seen by OE-A ?? ..... or have you thought of some kluge to get round this??

As for SD - USERS have been using this for 18 months - but of course users are not important??

OpenATV shouldn't accept this mechanism with the SD card in the first place as it is extra complex and not mandatory at all...

 

But hopefully they're willing to adapt as well... Actually when they also go for 'structure' somehow they SHOULD DO IT...

 

For the users it is actually a one time flash with an USB stick as in the early days. Something that could really be avoided when OpenATV (and other OE-A images) did implement it correctly at the first place.

 

We cannot help that we strive to do things better by avoiding stuff like "if box x do something else just to generate more complicate code because manufacturers are not willing to adapt so we fixed it for them by making e2 more complicated..."...

 

We also have a mechanism in preparation that they can keep the 2 slots on the SD (so they go for 5 or 6 slots) - The same can then also be done on ZGemma, mut@nt boxes, and GB... it is just adding more STARTUP_... files for the extra slots and prepare the SD (or USB) by partitioning and reformat (prepare) it... So maybe we think further than just swallow what a manufacturer dictates...

 

I just 'remembered' that openATV also adapts approx. our multiboot/online flash code. We know fully parse the STARTUP_... files in our code to see what multiboot features are possible without any static config anymore in SystemInfo.py. Basically when you add STARTUP_ files to the box and add partitions on weird location and the box boot stuff is capable of starting these slots then at this moment our multiboot implementation is endless (compact and universal)...

Edited by littlesat, 26 March 2020 - 11:17.

[Huevos]

What is the point PLi having multiboot if that multiboot is not compatible with any other image except PLi?

 

Also not right to join the party 18 months late and expect all other images to change their code.

Edited by Huevos, 26 March 2020 - 11:26.

[littlesat]

When other images do not change they are MAD!!!

The mechanism will be the same as H7/GB/Mut@nt... it will be universal...something other images should already strive 18 months ago... Gone with the exceptions here... And someone of us did it that SF8008 changed it also... It proves you can discuss it with the manufacturer to do things right...

Our implementation IS MORE COMPATIBLE... as it is one code for all....

Edited by littlesat, 26 March 2020 - 11:35.

[twol]

When other images do not change they are MAD!!!

The mechanism will be the same as H7/GB/Mut@nt... it will be universal...something other images should already strive 18 months ago... Gone with the exceptions here... And someone of us did it that SF8008 changed it also... It proves you can discuss it with the manufacturer to do things right...

Our implementation IS MORE COMPATIBLE... as it is one code for all....

Its not the same as the h7/hd51 or Giga4k UHD & UE - that an easy implermentation using kernel/root pairs not this ##### #### invented by Zgemma

Also you keep talking about images (there is only about 11 other images and I am sure they will jump to using this meta, because OpenPli have just joined the game and want to change everything) - more importantly what about USER's that have been using the current system for the last 18 months and have to change ....................for OpenPli, when many of them have never used and never want to use OpenPli??

 

As for Octagon - if you haven't noticed he just wants to sell hardware

Edited by twol, 26 March 2020 - 12:21.

[littlesat]

It is not OpenPLi changing this... it were the other oe-a images that accepted 18 months ago the stuff sf8008 did create in the first place. Why was an SD required for Multiboot in the first place?

And already now with a small manual action you simply add the two parts from the SD you have to our current code as we now parse the STARTUP_ files....

When the other images indeed want smooth code without if box than do some other crap inside they should adapt... When they don't it is a big sorry... we strive not to adapt to crap stuff...

 

As for Octagon... since we're working with them they already made some adaptions to their drivers about issues others did not noticed or work-a-round in enigma2. Something that other images did not arrange in those famous 18 months?

Edited by littlesat, 26 March 2020 - 15:46.

[WanWizard]

Very simple: When the SF8008 was released, there was no multiboot support, flash was a single partition with a single rootfs. So OE-A hacked their way around that by using an SD card, since there was only one partition in flash.

 

All OE-A based images inherited the hack, since they are all based on the same OE.

 

Is is only after we have been discussing this with Octagon that they created a BSP with multiboot support, and for that the adopted the gfutures (hd51) method, for compatibility reasons.
 

This is one of the many reasons why we insist on a vendor BSP and direct contact, instead of simply receiving an email with drivers and create the rest ourselfs...

[littlesat]

+100

[Gold_66]

Just to clarify: Can we now install latest version of OpenPLi in flash, and two more images *without* sd card?

If so, it is a revolutionary progress for our devices - thanks and congratulations!

[twol]

Just to clarify: Can we now install latest version of OpenPLi in flash, and two more images *without* sd card?

If so, it is a revolutionary progress for our devices - thanks and congratulations!

No - if the

 

Very simple: When the SF8008 was released, there was no multiboot support, flash was a single partition with a single rootfs. So OE-A hacked their way around that by using an SD card, since there was only one partition in flash.

 

All OE-A based images inherited the hack, since they are all based on the same OE.

 

Is is only after we have been discussing this with Octagon that they created a BSP with multiboot support, and for that the adopted the gfutures (hd51) method, for compatibility reasons.
 

This is one of the many reasons why we insist on a vendor BSP and direct contact, instead of simply receiving an email with drivers and create the rest ourselfs...

@Wanwizard- have you actually looked at the Octagon meta. - it uses zgemma not HD51 format - and I have run the image builds so I know that is accurate it uses partitions 12/13/14/15 for the kernel and 16 for all the roots

Edited by twol, 26 March 2020 - 18:56.

[twol]

Just to clarify: Can we now install latest version of OpenPLi in flash, and two more images *without* sd card?

If so, it is a revolutionary progress for our devices - thanks and congratulations!

With proposed OpenPli new meta you can install OpenPli images - others will not work unless they are on the sd card (but only if you copy the appropiate STARTUP files into the boot partition) - getting back from them is more of an issue

the OE-A images use a different meta

Edited by twol, 26 March 2020 - 18:53.

[littlesat]

Others can be installed... but once executed you get into the if sf8008 then do some other stuff code.. and you cannot switch back... what the other images did was bad from the beginning...!!!!!!!!!

Edited by littlesat, 26 March 2020 - 18:59.

[twol]

Others can be installed... but once executed you get into the if sf8008 then do some other stuff code.. and you cannot switch back... what the other images did was bad from the beginning...!!!!!!!!!

With the current meta you cannot even flash say image slot 2 properly, it flashes but boots into slot 1 - and its nothing to do with what other images did - the metas are totally different - OE-A uses the HD51 format (which with your multiboot chnages works perfectly with the sd card), teh OpenPLi meta uses zgemma

Edited by twol, 26 March 2020 - 18:59.

[littlesat]

Yes right... because the oe-a meta is bad! I still don’t understand why you don’t get it. Our meta is more universal!!!!

Edited by littlesat, 26 March 2020 - 18:59.

[twol]

Yes right... because the oe-a meta is bad! I still don’t understand why you don’t get it. Our meta is more universal!!!!

Of course I get it - if this had been done 18 months ago, I would have been really happy! ..... but expecting everyone to dump everything now and change to the new meta?????

 

Your changes to multiboot - actually make the existing implementation useable and transparent that it is using teh sd card - and with our changes to Harddisk - really transparent

Edited by twol, 26 March 2020 - 19:04.

[Gold_66]

 

Just to clarify: Can we now install latest version of OpenPLi in flash, and two more images *without* sd card?

If so, it is a revolutionary progress for our devices - thanks and congratulations!

With proposed OpenPli new meta you can install OpenPli images - others will not work unless they are on the sd card (but only if you copy the appropiate STARTUP files into the boot partition) - getting back from them is more of an issue

the OE-A images use a different meta

 

Ok, I see. Thanks for the reply - it's better to wait a bit more, since I'd probably mess up with something while trying to do that.

[twol]

 

 

Just to clarify: Can we now install latest version of OpenPLi in flash, and two more images *without* sd card?

If so, it is a revolutionary progress for our devices - thanks and congratulations!

With proposed OpenPli new meta you can install OpenPli images - others will not work unless they are on the sd card (but only if you copy the appropiate STARTUP files into the boot partition) - getting back from them is more of an issue

the OE-A images use a different meta

 

Ok, I see. Thanks for the reply - it's better to wait a bit more, since I'd probably mess up with something while trying to do that.

 

..... but I am talking about the Develop branch and things can change