-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add support for MultiPlay communcation #165
Comments
I would be happy to have it as part of the crate. Unfortunately the crate has gotten into a bit of a stuck state where further progress would require breaking changes to the assembly runtime stuff to get up to date with global_asm and such, so the crate hasn't seen anything new in a while. However, that shouldn't prevent examples from being added. And then when some day a 0.6 version is completed, the examples can have whatever small adjustments applied. And even before them, people can use them as reference code. |
Cool cool. Do we have the required breaking changes documented? I'd be happy to help with them. |
There's not a specific list... I've started an attempt at a redo more than once but gotten distracted each time. I've got nothing else pressing, I'll try to give |
I'm still around and interested in the project, if I can be of any help. |
Alright sure, if there's interested folks I'll try to start at least something later today. |
I'm also still here, and while I may not be able to contribute that much, I'm definitely still interested in the project and would love to play around with it a bit when it gets more stable. |
I'm still a bit new to Rust but I'd be interested in helping out |
I recently did an experiment/proof-of-concept where I send multiboot payloads from a host GBA to clients using the MultiPlay transfer protocol: https://github.com/TheHans255/rust-gba-multiboot-test. I'd like to add the necessary changes for supporting MultiPlay communication to this crate.
This would amount to:
SIOMLT_SEND
andSIOMULTI0
thruSIOMULTI3
registers.The text was updated successfully, but these errors were encountered: