-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Raspberry Pi 5] 4KB Page Memory Incompatible with 16KB Page Memory #1288
Comments
The page size is defined here: Line 17 in 1253e11
MacOS on arm64 already uses a 16 KB page size so it should work on Pi5 too. You can force it to 16384 and test if it runs fine. I can add a specific case for Pi5 in this file, similar to what's done for MacOS/arm64, but I don't know what #define(s) I should check to detect the Pi5. Unfortunately PAGE_SIZE is not defined in any standard include file and the correct way is to query it at runtime. But Flycast needs it at compile time. |
I'll test that out and report back this evening. There's a little outlined here about how Mac ARM64 gets around it, apparently OSX has a fix within :- https://github.com/AsahiLinux/docs/wiki/Broken-Software Edit:- I tested this out and it runs perfectly when I force the memory default to 16kb, thanks! |
I have just build the latest Flycast git code on the Pi5 with the aforementioned flycast/core/stdclass.h modification,
The only downside is that the Transparent Sorting setting required for Daytona USA 2001 ("Per Pixel") is too heavy on the machine. |
Can someone post the result of running the following command on a Pi5?
Thanks |
Is it still the case without any upscaling (x1)? |
This is it:
|
Yes, even at 1x it seems WAY too much for the machine. |
Fixes RPi 5 16 KB page size. Will not work if cross-compiling however Issue #1288
I just pushed a fix on master. It should now automatically detect the page size at build time. |
It works great now without touching Line 17 in 1253e11
Thanks!! About Pi5 performance with "per pixel" Transparent Sorting, seems like it's beyond the limits of the GPU, right? I mean, no way around it, correct? |
For a better gaming experience I guess the best SBC currently is RK3588 |
That doesn't support Vulkan, and doesn't even have proper MESA support, only some unsupported fork. No, thanks. |
Thanks for your feedback.
I'm afraid not, at least for now. We can only hope that the GPU driver gets improved in future versions. |
Vulkan support is only in Android, and have a very good performance. |
Ah yes, maybe in the future, Vulkan will get a bit better on the new Video Core! Let's wait and see. |
I won't be caught dead playing any games on that sorry excuse for an OS :P |
It's too bad that these new SoC's with capable GPU's have their vendor prioritize Android over Linux when it comes to drivers. |
Apologies for asking on a closed issue, how can I set the
|
Yes, it should work. This is how it's currently done on linux:
|
Please Note: This form is the minimum required information for submitting bugs.
Removing this form may lead to your issue being closed until it is completed.
Platform / OS / Hardware: Raspberry Pi OS Bookworm 64bit (Desktop and no Desktop)
Github hash:
Hardware: Raspberry pi 5 4GB
Description of the Issue
Flycast Software does not launch due to this bug raspberrypi/bookworm-feedback#107 , in short the pages being 4KB means the 16KB cannot be run on Linux Arm64 for Pi 5. A check for Pi 5 in flycast and then changing the virtual pages to 16KB would perhaps fix this
Debugging Steps Tested
Logs Gathered
Screenshots
The text was updated successfully, but these errors were encountered: