Post
by ritz » Wed Feb 02, 2011 4:51 pm
This looks to be great step forward for the DSi. Thanks to all involved for the work they've done.
I have some questions if anyone is willing to help me understand. Being a little naive on the subject of devices/cards/interfaces, I tried to figure out why I couldn't get a nitro homebrew to work with this new code. Perhaps it isn't ready yet and I'm not aware.
I rebuilt libnds-master at home yesterday and then my little demo against it. Using sudohax I successfully started up a yesterday's-build of hbmenu renamed as /boot.nds. When I chose my demo from the menu, all I received was a white screen and hangs. My demo code calls nitroFSinit() and reads files from there.
Poking around in the new svn code, I understand things in theory as:
1. Inside nitroFSinit(), fatInitDefault() is called, which mounts the new/first-in-the-list-to-try SD:/ interface (which becomes the default, if successful).
2. nitroFSinit() returns after chdir(nitro:/)
3. Homebrew continues on...
- However, inside nitroFSinit(), there's a check for "fat:/" in ARGV. I know hbmenu provides ARGV, but is hbmenu sending along "fat:/myrom.nds" or "sd:/myrom.nds"?
- does chdir(sd:/) even work? I mean, to me it seems the "fat" layer would need to be on top of that to work.
- So, for future, would the proposed way to access files be:
a) nitro FS -> nitroFSinit(); chdir("nitro:/"); fopen("/my-nitro-file-in-the-rom");
b) fat16/32 FS -> fatInitDefault(); chdir("fat:/"); fopen("/my-file-on-fat-filesystem-on-the-sd-card");
Like I said, naive.
P.S. I have a white DSi (Nintendo's 2nd hardware rev) with a non-SDHC card inserted
P.P.S. I have to run here, didn't proof read my post yet
