Line 1:
Line 1:
−
This list is designed to be a updated collection of current DS and DSi [[homebrew]].
+
This '''list''' is designed to be a updated collection of current DSi mode homebrew.
−
−
= DSi-mode homebrew =
+
==Regarding the current state of DSi mode homebrew in general==
There is currently no practical way to run homebrew in DSi-mode. Save game hacks exist, but these have severe limitations:
There is currently no practical way to run homebrew in DSi-mode. Save game hacks exist, but these have severe limitations:
* The SD slot and NAND flash are inaccessible.
* The SD slot and NAND flash are inaccessible.
* The amount of code space is limited to the available space in the game's save file. (A few kilobytes)
* The amount of code space is limited to the available space in the game's save file. (A few kilobytes)
** This restriction can be lifted with external hardware like [[EEPUART]] or [[spime]]. This is how [http://svn.navi.cx/misc/trunk/nds/dsi/cookinject/ larger chunks of code] or [http://www.flickr.com/photos/micahdowty/3794878172/in/set-72157621023570420/ image files] have been loaded by developers so far.
** This restriction can be lifted with external hardware like [[EEPUART]] or [[spime]]. This is how [http://svn.navi.cx/misc/trunk/nds/dsi/cookinject/ larger chunks of code] or [http://www.flickr.com/photos/micahdowty/3794878172/in/set-72157621023570420/ image files] have been loaded by developers so far.
+
+
==Exploits==
+
===The Drunken Coder's savegame exploit===
+
This exploit allows DSi homebrew coders to run unsigned ARM asm code in DSi-mode. The hack can be found [http://drunkencoders.com/2009/08/dsi-hack-update/ here].
+
+
==Homebrew==
+
+
==Computer applications==
+
===pyftdi===
+
svpe's python binding of libftdi. Grab it and read more information [http://svenpeter.blogspot.com/2009/08/pyftdi.html here].