-
Notifications
You must be signed in to change notification settings - Fork 8
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
merge arm9linuxfw into this repo #18
Comments
We can definitely merge the code tree and use the common routines but not merge them into a single source code, it's too hardcoded to be its own thing, the easiest way to go would be to generate the TCM-specific binary and relocate that from the bootloader |
Recently I've had the idea of just ditching arm9linuxfw as a separate project and instead have a super simple "command processor" that just reads and writes raw data, that way the ARM11 can easily access the ARM9 specific peripherals and interact with them. The NDMA controller would also be accessible, helping us avoid unnecessary and expensive read/write ops. Instead of just doing a raw iowrite* or ioread* from linux you could do a regmap_write or regmap_read and it'd handle these cases transparently. This sounds especially useful to something like the SD controller, where we have duplicated drivers on the ARM11 and ARM9 side. It also reduces the needed ARM9 code to a fairly simple |
That sounds pretty cool. I think it would speed up stuff a lot and reduce the complexity quite a bit. |
I've got a half-working modification to arm9linuxfw stashed somewhere that does something similar, but it's incredibly unstable (lasts maybe 3 or 4 writes before failing.) I'll see if I can dig it back up, as it would probably be best to be able to write drivers on the ARM11 side where possible. |
I don't think there's a need to have two separate code bases for the arm9 code? I guess that would tightly couple the fw to our bootloader, but unless we're planning additional bootloader support, or somehow moving the fw into the Linux kernel I don't see the point of keeping them separate. cc @Wolfvak
The text was updated successfully, but these errors were encountered: