Dolphin, the GameCube and Wii emulator - Forums

(10-18-2018, 04:34 AM)JosJuice Wrote: [ -> ]Making a 32-bit build without any JIT is easy. You just have to edit these two lines and then build as usual: https://github.com/dolphin-emu/dolphin/blob/cb576bf3820da934b09bb81bee445721e1cdb39e/Source/Android/app/build.gradle#L71-L72

But of course, this is going to run very slowly.

Not that easy. Last time I tried to compile a generic build it wouldn't finish as it always ended with compiling errors in NDK sources related to filesystem functions. I don't fully remember the details but there's some behavior change in the NDK and you need to bump minAPI to 24 to be able to successfully compile a generic Android build of Dolphin...

(10-18-2018, 07:24 AM)stizzo Wrote: [ -> ]Yep!

Mediatek, are also very used by crackers, to create malware to pre-install or to infect the kernel that the mediatek created and closed.

This on every mediatek machine.

PS: from my point of view, the best SoC to work on is Qualcomm Snapdragon, followed by Exynos and Kirin.

The rest is rubbish.

I hear the MTK Helio x30 is quite good. Dual A73, PowerVR Rogue graphics, all API’s and 64bit supported. Last time it came up I believe it was mentioned the PowerVR drivers are actually in quite a good state. Not to mention my K8 Note with a Helio X23 is quite usable in dolphin. Not defending MediaTek, they are the ones shipping 32bit chipsets by the barrel in 2018. Not to mention they have a great way of making OEM’s avoid updating their devices lmao.

(10-18-2018, 10:56 AM)Nintonito Wrote: [ -> ]I hear the MTK Helio x30 is quite good. Dual A73, PowerVR Rogue graphics, all API’s and 64bit supported. Last time it came up I believe it was mentioned the PowerVR drivers are actually in quite a good state. Not to mention my K8 Note with a Helio X23 is quite usable in dolphin. Not defending MediaTek, they are the ones shipping 32bit chipsets by the barrel in 2018. Not to mention they have a great way of making OEM’s avoid updating their devices lmao.

Of course, I agree with you, regarding 32Bit and how Mediatek treats OEMs, charging for the release of a free license kernel (a Linux Kernel) and closing all source codes.

This company, for the way it behaves with the rules of a GPL and with the Ethics of the programmers and developers, in my opinion should fail instantly.

It should only sell SoC, nothing else.

Instead, in addition to the SoC, Mediatek is also paid salty for the release of a source code, a license that should, I repeat, be all free; a Linux Kernel.

As I think it, this company only thinks about its profits and this only makes me angry.

The Helio, are good SoC (P60 with Mali G72MP3, Oppo A3 for example), the PowerVR, despite a Mediatek, stubbornly implement them in clusters of a few cores (low performance, when compared with those of the competitors), are mature.

But removed this family, the rest makes throw up.

The problem, however, is not the performance, but the large fragmentation that has come to create because of a Mediatek, which I repeat, it makes you pay to leave a license of a source code, which should in theory be open to anyone.

The fault is not the OEMs in this matter, Mediatek have the main fault.

Serious OEMs exist, but they are few and have a lot of money. (and update their terminals)

In the end, there are the tons of criminals "OEMs", who sell their products at low cost and the unwitting citizen buys them and without his knowledge, with dozens of malware pre-installed on the terminal.

Other thing, the support that can provide a Qualcomm, with the Mediatek you can forget it.

PS: In all those Asian and non-Asian countries, Kirin is the way, for those who want to spend a little money and have good performance and good support. (Kirin 710)

Or in alternative, Qualcomm Snapdragon 636/660/710/835/845 (Xiaomi!)

I apologize for any translation errors.

(10-18-2018, 12:28 PM)stizzo Wrote: [ -> ]Of course, I agree with you, regarding 32Bit and how Mediatek treats OEMs, charging for the release of a free license kernel (a Linux Kernel) and closing all source codes.

This company, for the way it behaves with the rules of a GPL and with the Ethics of the programmers and developers, in my opinion should fail instantly.

It should only sell SoC, nothing else.

Instead, in addition to the SoC, Mediatek is also paid salty for the release of a source code, a license that should, I repeat, be all free; a Linux Kernel.

As I think it, this company only thinks about its profits and this only makes me angry.

The Helio, are good SoC (P60 with Mali G72MP3, Oppo A3 for example), the PowerVR, despite a Mediatek, stubbornly implement them in clusters of a few cores (low performance, when compared with those of the competitors), are mature.

But removed this family, the rest makes throw up.

The problem, however, is not the performance, but the large fragmentation that has come to create because of a Mediatek, which I repeat, it makes you pay to leave a license of a source code, which should in theory be open to anyone.

The fault is not the OEMs in this matter, Mediatek have the main fault.

Serious OEMs exist, but they are few and have a lot of money. (and update their terminals)

In the end, there are the tons of criminals "OEMs", who sell their products at low cost and the unwitting citizen buys them and without his knowledge, with dozens of malware pre-installed on the terminal.

Other thing, the support that can provide a Qualcomm, with the Mediatek you can forget it.

PS: In all those Asian and non-Asian countries, Kirin is the way. (Kirin 710)

Honestly, none of this matches my experience - unless everything has changed in ~9 months or so.

Mediatek aren't really involved in the 32/64bit choice - they supply both BSPs to their customers, and they decide if the 64bit support is worth the extra flash space and memory usage. Naturally, as they're not really going for the high-end, and every penny counts there, they often don't bother. Especially as 64bit support doesn't seem well marketed in the chinese markets.

When I worked with mediatek parts, we just used the upstream android and chromeos kernels (like this: https://chromium.googlesource.com/chromiumos/third_party/kernel/). They seemed to boot fine for us, some userspace HALs were binary blobs, so were a pain to use (or you just lived without those features, as when doing graphics development you rarely care about the compass or gps or similar . One problem mediatek (and most east asian SoC manufacturers) had is they had a "just get it working now" mentality to software - so it integrated badly with the upstream ways of doing things, and caused painful integrations when trying to move other parts of the software stack forwards. Let alone the pain of trying to read and understand (and fix) their code. But they were getting better, some of which was due to the ChromeOS team putting their foot down and demanding linux upstream-quality code integrating with linux-upstream interfaces and methods.

Similarly, powervr aren't forcing anyone to use the small, low cost (in terms of the price powervr charge for the design and the silicon area increasing production costs) GPUs. See the above comment about costs.

As for your last statement - I've had more issues as an end user with the mali GPU driver than PowerVR's (but half of that may be due to me fixing the issues I happened to stumble into , and unless the G51 in the kirin 710 magically punches above the weight of the "higher end" cores in the same family, I'd be surprised if it could reliably run something as demanding as dolphin on even relatively light games.

Imagination Technologies does not hit anything with the Linux Kernel, which I know has open source code.

If in recent months, the Mediatek policy has changed, it's a good sign, but I remember this:

MediaTek, it seems, modifies the Linux kernel instead of changing the license (more or less as if BMW bought Ferrari and remitted them without precise agreements in this regard). The few leaked sources, in fact, show that various parts of the Linux kernel have been changed by changing the existing GPL license and inserting Apache, BSD or proprietary licenses. All of this is, of course, illegal.

As if this were not enough (and perhaps because of this), MediaTek requires that anyone who wants to access the sources sign a non-disclosure contract and pay a considerable sum that also includes the technical documentation of the chips. The only companies able to sign the contract and to afford the payment of the license are the big companies.

This is in direct violation of point 3, paragraph b of the GPLv2.

The Mali G51 is a good gpu:



In my previous PS, exists Snapdragon 636/660/710/835/845 Xiaomi OEM with Qualcomm Partnership.

Hey guys I do not want to be bad but the conversation is getting out of the main topic.

Sorry, you're right :-)

(10-18-2018, 01:05 PM)stizzo Wrote: [ -> ]Imagination Technologies does not hit anything with the Linux Kernel, which I know has open source code.
...

If you repeat things enough times it becomes true (/s)

PowerVR distribute their kernel package to their customers. It's up to them to distribute it to their customers (the device manufacturers), and then to the customers. This is somewhat by design (due to each SoC vendor having to tweak the code to work in their system, as stuff like their integration into the busses on their specific SoC will need to be done - meaning you can't just drop another SoC's version of the driver in and expect it to work - but you could do the equivalent of those modifications yourself (they're pretty trivial and abstracted out - see here https://android.googlesource.com/kernel/mediatek/+/android-mtk-3.18/drivers/staging/imgtec/mt8173/ for the mt8173 versions, for example). And this is what the GPL requires. If you actually read the sections you've quoted, it requires distribution of the source (under the same license) with the product. Not to anyone - otherwise I'd be breaking the GPL for little local modifications that I don't instantly upload publicly.

Like Cubieboard do for the Allwinner a80 here: https://github.com/cubieboard/CC-A80-kernel-source/tree/master/modules/rogue_km

Or TI do for their omap chips here: https://git.ti.com/graphics/omap5-sgx-ddk-linux/trees/master/eurasia_km

Or Mediatek do here https://android.googlesource.com/kernel/mediatek/+/android-mtk-3.18/drivers/staging/imgtec/rogue/

It'll never be merged upstream, as it doesn't fit kernel coding style and has a huge amount of not-invented-here wrappers and helpers and interfaces and tools that don't integrate well with the upstream linux codebase.

Not because the code isn't available.

Of course, much of the "interesting" part of the driver (shader compiler, state tracking, command buffer creation) is done in userspace. Which *is* closed, and not open source. Exactly as the linux license allows.

EDIT: you're right nonexist - this isn't the right place. I'll leave the links above in case anyone wants to actually look at them though

My smile is not for you and does not make fun of or jokes with people.

The problem of the different implementations of the drivers with the different SoCs, does not hit anything with the release of source code and the sale of licenses.

And Mediatek, as far as I'm concerned, goes against the GPL.

Hi, forum staff here, remember when this was a thread about weihuoya's custom android build? Because the majority of the posts here are totally unrelated! So I'm just going to get my magic moderator wand aaand



There we go! Now we don't need to worry about crowding weihuoya's thread! Anyway, this is delfino plaza now so feel free to continue.

To anyone who wants to see the original thread, here's a link to it. Only post about weihuoya's personal build there please. - https://forums.dolphin-emu.org/Thread-share-my-personal-build-for-android