You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I've been looking around trying to understand what "Memory training" is and I'm not understanding what I'm reading 123.
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?
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.
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.
The text was updated successfully, but these errors were encountered: