53
edits
Changes
Jump to navigation
Jump to search
Created page with "I'm planning on finishing up this page and adding in all of the FS/FSA commands. I've already mapped most of them to their Ioctl/Ioctlv commands (51 commands so far, in all in..."
I'm planning on finishing up this page and adding in all of the FS/FSA commands.
I've already mapped most of them to their Ioctl/Ioctlv commands (51 commands so far, in all including 2 that I have yet to figure out their function but know they are valid commands at least in Debug mode)
Question is, which format to use.
The /dev/mcp format doesn't explain the parameters for the functions like /dev/crypto does, and these have much more detail. I'm thinking of either going to a new format, or putting this all on a different page more aimed at the functions than the ioctals.
Function Name Command Ioctl Ioctlv Async Version FSA* Function
FSMount 0x1 N Y Y Y
FSStatus FSMount( FSClient*client, FSCmdBlock*block, FSMountSource *source, char*target, u32 bytes, FSRetFlag errHandling );
Mount a volume.
Results -> FS_STATUS_OK = Successfully completed.
FS_STATUS_CANCELED = The command was canceled.
FS_STATUS_NOT_FOUND = Target not found.
FS_STATUS_EXISTS = Specified device file is already mounted, or specified target path is in use with another volume.
FS_STATUS_UNSUPPORTED_CMD = Target has been formatted to unsupported file system.
FS_STATUS_PERMISSION_ERROR = The caller does not have correct access permission.
FS_STATUS_MEDIA_ERROR = Media is in some inaccessible condition.
Parameters:
client = Pointer to the client buffer.
block = Command block.
source = Pointer of mount source.
target = Buffer for target mount point path.
bytes = Length of the target. This must be greater than or equal to FS_MAX_MOUNTPATH_SIZE.
errHandling = Auto error handling flag. Only indicated errors are returned. (See -> responses above)
Or just parse it down to minimum info -or- maybe this should all go an a different page... [[User:Datalogger|Datalogger]] ([[User talk:Datalogger|talk]]) 10:52, 12 May 2016 (CEST)
I've already mapped most of them to their Ioctl/Ioctlv commands (51 commands so far, in all including 2 that I have yet to figure out their function but know they are valid commands at least in Debug mode)
Question is, which format to use.
The /dev/mcp format doesn't explain the parameters for the functions like /dev/crypto does, and these have much more detail. I'm thinking of either going to a new format, or putting this all on a different page more aimed at the functions than the ioctals.
Function Name Command Ioctl Ioctlv Async Version FSA* Function
FSMount 0x1 N Y Y Y
FSStatus FSMount( FSClient*client, FSCmdBlock*block, FSMountSource *source, char*target, u32 bytes, FSRetFlag errHandling );
Mount a volume.
Results -> FS_STATUS_OK = Successfully completed.
FS_STATUS_CANCELED = The command was canceled.
FS_STATUS_NOT_FOUND = Target not found.
FS_STATUS_EXISTS = Specified device file is already mounted, or specified target path is in use with another volume.
FS_STATUS_UNSUPPORTED_CMD = Target has been formatted to unsupported file system.
FS_STATUS_PERMISSION_ERROR = The caller does not have correct access permission.
FS_STATUS_MEDIA_ERROR = Media is in some inaccessible condition.
Parameters:
client = Pointer to the client buffer.
block = Command block.
source = Pointer of mount source.
target = Buffer for target mount point path.
bytes = Length of the target. This must be greater than or equal to FS_MAX_MOUNTPATH_SIZE.
errHandling = Auto error handling flag. Only indicated errors are returned. (See -> responses above)
Or just parse it down to minimum info -or- maybe this should all go an a different page... [[User:Datalogger|Datalogger]] ([[User talk:Datalogger|talk]]) 10:52, 12 May 2016 (CEST)