53
edits
Changes
no edit summary
Line 28:
Line 28:
:That format looks nice! For what it's worth, I would just go for replacing the current list format with an elaborate function documentation like this for each list entry. The raw list on its own isn't particularly useful for anything unless one needs to work with the raw ioctl interfaces, which hopefully will be obsolete when someone writes a library for this stuff. [[User:Neobrain|Neobrain]] ([[User talk:Neobrain|talk]]) 12:07, 22 May 2016 (CEST)
:That format looks nice! For what it's worth, I would just go for replacing the current list format with an elaborate function documentation like this for each list entry. The raw list on its own isn't particularly useful for anything unless one needs to work with the raw ioctl interfaces, which hopefully will be obsolete when someone writes a library for this stuff. [[User:Neobrain|Neobrain]] ([[User talk:Neobrain|talk]]) 12:07, 22 May 2016 (CEST)
+
+::I'm thinking I'll go ahead and map all of the Ioctl commands to their type in a simple table (ioctl/ioctlv/ioctlAsync/ioctlvAsync), then below that, give a detailed explanation for the parameters and return values for each one.
+::My reason is, a quick table makes it easy to see if there's an Async you can call from PPC using an IPC. [[User:Datalogger|Datalogger]] ([[User talk:Datalogger|talk]]) 12:21, 23 May 2016 (CEST)