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
Would it be possible to add support for mounting SD2SP2 to the kernel? That way it could be used as rootfs instead of a SD Gecko.
In the GameCube C libraries of the devkitPro project in which they added support for SD2SP2, it appears that this is a communication interface identical to that of a standard SD Gecko, incorporating some differential features and specifying a different IO address (0x00000080).
I understand that it should be possible to include this support in the gcn-sd driver, which manages the MemoryCard SD devices and allows it to be mounted, however, it does not have the proper support to work with the EXI Serial Port 2, assuming it acts entirely like an SD Gecko (DOL-014).
I don't have the knowledge about GC architecture nor have I ever worked with devkitPro, however I think if someone has more information about this we could add the support.
The text was updated successfully, but these errors were encountered:
Would it be possible to add support for mounting SD2SP2 to the kernel? That way it could be used as
rootfs
instead of a SD Gecko.In the GameCube C libraries of the devkitPro project in which they added support for SD2SP2, it appears that this is a communication interface identical to that of a standard SD Gecko, incorporating some differential features and specifying a different IO address
(0x00000080)
.I understand that it should be possible to include this support in the gcn-sd driver, which manages the MemoryCard SD devices and allows it to be mounted, however, it does not have the proper support to work with the EXI Serial Port 2, assuming it acts entirely like an SD Gecko (DOL-014).
I don't have the knowledge about GC architecture nor have I ever worked with devkitPro, however I think if someone has more information about this we could add the support.
The text was updated successfully, but these errors were encountered: