I would not be so quick.
3ds- processor based on an ARM processor and presumably not that different from the GBA and DS before it (one of the many first rules of engineering is do not design anything "new" if you do not have to) so http://nocash.emubase.de/gbatek.htm would be a start or maybe going right to the source (do a search for ARM datasheet). Still assuming that nicety is lacked the following exists
http://www.youtube.com/watch?v=Q9ezff6LIoI
Better yet if it is coming from an exploit all the truly annoying stuff that comes from assembly (memory management is easy enough at first and the real trick is in all the necessary IO routines which have all be taken care of (see how 99% of rom hacking works) or at least available for perusal).
But of course this is "trivial" in the grand scheme of things so some fiddling around to discover the way memory is mapped (again see gbatek for some of the examples and if you want an example of what happens when it goes wrong see some of the threads on GBA and DS rom hacking when people miss something dealing with the graphics memory) and some of the IO (which things are mapped to memory and how the extra hardware works- probably using a variation on the youtube video's methods) will have to be figured out to get far which is tricky and turned into a usable library (this is one of the reasons there is often a fairly large gap between "legit" homebrew and "unlawful" homebrew on the likes of the xbox with the other being the console SDK developers do occasionally create a nice library with formats and such or simply the effective (or simple) use of hardware- see the porting of SDL, if viable to do so, being a fairly key step in the homebrew life of a system).
Unlikely it may be but end users have found things before that became useful at some level- in my own experience I have been playing with video programs written by developers I consider truly good coders that were using full specs and all known bastardisations and I still find video sources that frustrate it. Game/hardware developers are in possibly in a worse position than this.
3ds- processor based on an ARM processor and presumably not that different from the GBA and DS before it (one of the many first rules of engineering is do not design anything "new" if you do not have to) so http://nocash.emubase.de/gbatek.htm would be a start or maybe going right to the source (do a search for ARM datasheet). Still assuming that nicety is lacked the following exists
http://www.youtube.com/watch?v=Q9ezff6LIoI
Better yet if it is coming from an exploit all the truly annoying stuff that comes from assembly (memory management is easy enough at first and the real trick is in all the necessary IO routines which have all be taken care of (see how 99% of rom hacking works) or at least available for perusal).
But of course this is "trivial" in the grand scheme of things so some fiddling around to discover the way memory is mapped (again see gbatek for some of the examples and if you want an example of what happens when it goes wrong see some of the threads on GBA and DS rom hacking when people miss something dealing with the graphics memory) and some of the IO (which things are mapped to memory and how the extra hardware works- probably using a variation on the youtube video's methods) will have to be figured out to get far which is tricky and turned into a usable library (this is one of the reasons there is often a fairly large gap between "legit" homebrew and "unlawful" homebrew on the likes of the xbox with the other being the console SDK developers do occasionally create a nice library with formats and such or simply the effective (or simple) use of hardware- see the porting of SDL, if viable to do so, being a fairly key step in the homebrew life of a system).
Unlikely it may be but end users have found things before that became useful at some level- in my own experience I have been playing with video programs written by developers I consider truly good coders that were using full specs and all known bastardisations and I still find video sources that frustrate it. Game/hardware developers are in possibly in a worse position than this.