Dolphin on the pi 4?

**JonnyH** · 07-04-2019, 05:59 AM **#71**

According to toms hardware, that firmware update drops the (under cpu load) power usage from 7.9w to 7.6w. That sort of difference will likely be difficult to separate from the noise of a non-synthetic load.

The IR images were taken at idle, so naturally the relative differences look larger, as the USB controller is a much higher proportion of the used power than when the SoC is under load. Aside from IR cameras being a /terrible/ way of measuring heat generation or cooling performance - as it makes small differences look large, well within the range of error due to different air temperatures or airflow or different stages of heat soak.

bomblord · (This post was last modified: 07-04-2019, 06:36 AM by bomblord.)

(07-04-2019, 05:59 AM)JonnyH Wrote: According to toms hardware, that firmware update drops the (under cpu load) power usage from 7.9w to 7.6w. That sort of difference will likely be difficult to separate from the noise of a non-synthetic load.

The IR images were taken at idle, so naturally the relative differences look larger, as the USB controller is a much higher proportion of the used power than when the SoC is under load. Aside from IR cameras being a /terrible/ way of measuring heat generation or cooling performance - as it makes small differences look large, well within the range of error due to different air temperatures or airflow or different stages of heat soak.

Thanks for the information on IR cameras didn't realize they were that inaccurate. Regarding the power usage, I figured a power difference of 7.9w to 7.6w was significant when the overall power draw is that low but I guess not. Even so It also takes nearly 2 additional minutes for an identical CPU load to hit thermal throttling w/o a heatsink on the new firmware so there are definitely some real gains in thermal performance.

**Helios** · 07-08-2019, 05:58 AM **#73**

I like how users are in lala land imagining that the Pi 4 is going to be great for Dolphin and yet nobody has posted anything demonstrating that.

bomblord · (This post was last modified: 07-09-2019, 06:39 AM by bomblord.)

(07-08-2019, 05:58 AM)Helios Wrote: I like how users are in lala land imagining that the Pi 4 is going to be great for Dolphin and yet nobody has posted anything demonstrating that.

I wouldn't put myself in the crowd who is expecting any kind of miracle results at best I'm guessing it may run some low end easy games.

But anyway, the reason I personally haven't posted anything yet is I have yet to receive my Pi 4 to test. I actually have 2 on order (one will probably be a desktop and the other a dedicated retro machine) but one hasn't even shipped yet and the other has shipped but is coming from the UK to the US estimated shipping time it should come in this week possibly today. I've picked up a wii and re-ripped my meager library games for testing so once I get it's just a matter of setting up Raspbian, attempting to compile a Dolphin build, and finding out what the results are (also an aside my local Gamestop does have a copy of New Super Mario Bros Wii so I may pick that up out of my next paycheck to test).

bomblord · (This post was last modified: 07-12-2019, 01:03 AM by bomblord.)

Received my Pi 4 today. Upon attempting to compile dolphin I get the following error when using cmake
ARMv7 is an unsupported platform. Enable generic build if you really want
a JIT-less binary.

I'm sure the solution is relatively straightforward but in this case I don't know what I don't know. I attempted some googling and found a list of cmake commands one of which is ENABLE_GENERIC so I tried cmake ENABLE_GENERIC but that didn't work.

**DJBarry004** · 07-12-2019, 01:05 AM **#76**

... I mean, you should have known by know that Dolphin requires a 64-bit OS installed (including Android). That meant ARM-v7 support had to go (32-bit devices would be far from enough for Dolphin anyway had support continued).

bomblord · 07-12-2019, 01:14 AM **#77**

(07-12-2019, 01:05 AM)DJBarry004 Wrote: ... I mean, you should have known by know that Dolphin requires a 64-bit OS installed (including Android). That meant ARM-v7 support had to go (32-bit devices would be far from enough for Dolphin anyway had support continued).

The processor itself is an A72 64bit arm-v8. But if it won't work it won't work oh well.

**DJBarry004** · 07-12-2019, 01:42 AM **#78**

(07-12-2019, 01:14 AM)bomblord Wrote: The processor itself is an A72 64bit arm-v8. But if it won't work it won't work oh well.

Hm, no idea then. Maybe your Pi shipped with 32-bit OS then?

I don´t really know what compiler are you using, but I remember Visual Studio allows you to change your project´s target OS. You could try something similar on whatever compiler you´re using if it allows that.

bomblord · 07-12-2019, 01:47 AM **#79**

(07-12-2019, 01:42 AM)DJBarry004 Wrote: Hm, no idea then. Maybe your Pi shipped with 32-bit OS then?

I don´t really know what compiler are you using, but I remember Visual Studio allows you to change your project´s target OS. You could try something similar on whatever compiler you´re using if it allows that.

Was using cmake from terminal. It looks like it is indeed a 32 bit OS according to the system information so looks we'll have to wait for some third party OS solution (there were a few 64 bit options on the pi 3) if Dolphin is ever going to run on a pi4.

**Helios** · (This post was last modified: 07-12-2019, 10:27 AM by Helios.)

lmfao they're so terrified of breaking backwards compat they're still shipping 32 bit in 2019

amazing