Hello, here I saw a website, who can explain what it is if you can trust them ?
Edited by fox71, 27 December 2016 - 15:11.
Posted 27 December 2016 - 15:09
Hello, here I saw a website, who can explain what it is if you can trust them ?
Edited by fox71, 27 December 2016 - 15:11.
Posted 27 December 2016 - 15:15
No clue what it is, we've tried to contact them because of misuse of the OpenPLi name and trademark, but no response.
It has nothing to do with us, and therefor it isn't a genuine OpenPLi image.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 29 December 2016 - 16:43
Already done some time ago. As usual with OVH, not even a response.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2017 - 22:36
Posted 2 January 2017 - 22:54
Edited by athoik, 2 January 2017 - 22:58.
Posted 2 January 2017 - 23:29
Edited by athoik, 2 January 2017 - 23:30.
Posted 2 January 2017 - 23:34
It is not about being able. Off course we are able.
The issue is that DMM does it's very best to hide the working of their drivers in closed source code, so it can't be reverse engineered. They also do their very best implement everything different from the standard, to avoid stuff they made works on hardware from other manufacturers.
The first thing makes it a very time consuming operation, the second means the code will become an unreadable spaghetti because you have to make exclusions and special code for a specific vendor. And with a dozen or so vendors to support, and a lot of different models, that makes it a nightmare we simply don't want.
To make sure vendors that do this should solve these issue's themselfs, we use BSP's, hardware abstraction layers maintained by the vendor themselfs. And DMM doesn't provide us with one. As soon as they do, and they are willing to cooperate again, we can talk.
People cloning our source code don't have to spend any effort in maintaining an image, they just take our code. And then they put the minimum effort in to hack the DMM drivers into that code. And then they publish the image, without any source, and without any point of contact so people come here for support.
I'm pretty sure DMM specific features don't work in such images. And if they do, the people that made them must have had access to DMM's source code, which is no longer public.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2017 - 23:36
Posted 2 January 2017 - 23:47
Posted 3 January 2017 - 00:25
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
0 members, 7 guests, 0 anonymous users