devkitPro

Not exactly. It's more like it prefetches an extra cache line (the cache lines are always stored in pairs, so it's not causing any extra evictions)... which would be a wasted fetch if the program didn't use that memory. But in almost all cases it's beneficial.

Can you explain more what it does and how can I use it ? I see a "L2Enhance()" function in cache.c, do I need to call it on Init ? Does it only optimize 64-bit words (u64) read from memory ? Does it work with Gekko CPU as well ? It should be called as early as possible since it invalidate...

It works fine when outputting to a file and there's no rules defining how a standard output device has to behave - if you haven't set up a console it throws away everything , are you going to call that a bug too? Newsflash: undefined operations may produce different results on different systems. Doe...

It's not a bug, it's perfectly valid C behaviour - '\0' signifies the end of a string.

/dev/usb/ven and /dev/usb/hid don't work like that; devices are accessed through them using ioctls. Given that all the failing devices are HIDs, it sounds like you're using one of the unsupported IOSes as mentioned in the comment at the top of usb.c. These IOSes implement an older version of /dev/us...

I said uninitialized(random). Finding an uninitialized value set to 0 is not very rare. Something tells me your identify/setuid tests didn't work (which isn't surprising, ES_Identify has been fixed for ages and setuid doesn't work unless you're already identified as the system menu). Why not find ou...

Apps loaded from HBC will only be identified as HBC if they use no_ios_reload, otherwise a new IOS is loaded and the owner/group will be uninitialized. As for what you should do, maybe rethink whatever you're attempting? The reason owner/group permissions exist is to prevent apps accessing files tha...

Unless you've identified as a specific title after IOS is loaded (or the current IOS was loaded during an ES_LAUNCHTITLE call), the owner and group used to access/create new files will be uninitialized (random). Not sure why libogc has parameters to specify the owner and group as they will be ignore...

Wii, but I use my own code for USB storage which expects data buffers allocated from MEM2.

fatGetVolumeLabel in libfat.c is using regular C memory allocation routines (malloc/free) instead of the appropriate libfat wrappers (_FAT_mem_allocate/_FAT_mem_free), which breaks compiling when those functions aren't available.