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.

Sign up for GitHub

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

Jump to bottom

Use GDMA for tile transfers #639

Open
FredrIQ opened this issue May 28, 2021 · 3 comments
Open

Use GDMA for tile transfers #639

FredrIQ opened this issue May 28, 2021 · 3 comments
Labels
optimizations refactoring

Comments

@FredrIQ
Copy link
Collaborator

FredrIQ commented May 28, 2021 •
edited
Loading

Consider using GDMA transfers (rHDMA1-5 registers) for tile copying to VRAM, if applicable. It's roughly 2-10 times faster compared to the Prism routine (worst vs best case improvement), generally around 4 times faster with LCD enabled and 10 times with it disabled.

There appears to be a brand new discovery of GDMA limitations in LCD mode 2 that isn't yet fully understood, so I'm filing this issue for revisiting later when more details are known.
@FredrIQ
Copy link
Collaborator Author

FredrIQ commented May 29, 2021

For reference about mode2 issues: gbdev/pandocs#299

@FredrIQ
Copy link
Collaborator Author

FredrIQ commented Aug 4, 2022

This issue has been resolved on pandocs. GDMA is safe in Mode 2. So replacing Prism routines with GDMA when applicable should work perfectly.

@FredrIQ FredrIQ closed this as completed Aug 4, 2022
@FredrIQ
Copy link
Collaborator Author

FredrIQ commented Aug 4, 2022

This resolves the caveat blocking the issue, meaning this is a feature I can adapt. Reopening the issue to clarify this

@FredrIQ FredrIQ reopened this Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimizations refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FredrIQ