Skip to content
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

Hekate far less responsive on Mariko units #1050

Open
souldbminersmwc opened this issue Dec 19, 2024 · 3 comments
Open

Hekate far less responsive on Mariko units #1050

souldbminersmwc opened this issue Dec 19, 2024 · 3 comments

Comments

@souldbminersmwc
Copy link

Hello!
Hekate on mariko units is noticabily slower than on Erista units. Comparing Erista vs Mariko, Erista is faster and more responsive. My Mariko (OLED) is modded with a picofly.

@masagrator
Copy link

This is not a bug. This is a result of not implementing ram training for Mariko units. Dev is fully aware of this.

@coolaj86
Copy link

coolaj86 commented Jan 28, 2025

I've been looking around trying to understand what "Memory training" is and I'm not understanding what I'm reading 1 2 3.

I think what this is saying is that some sort of profiling occurs that tries a few different clock speeds and voltages at different temperatures, saves the result somewhere so that it doesn't have to be done again, and then sets the RAM to operate at the highest speed and lowest voltage that pass all of the tests for a given temperature.

Can you explain what it means in the context of the Switch and/or CFW?

Is the issue that nVidia or Nintendo or the CFW is not implementing the RAM training?

@Masamune3210
Copy link

That's basically what memory training is, its training on what is the best way to set the ram up. Since its part of very early init, I would imagine it's Hekate's job to handle it and it just isn't currently. There are only so many hours in the day and not all of that can be spent on dev work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants