2006-12-10 10:18:57 +00:00
|
|
|
To decode a hex IOCTL code:
|
|
|
|
|
|
2008-07-26 02:45:33 +00:00
|
|
|
Most architectures use this generic format, but check
|
2006-12-10 10:18:57 +00:00
|
|
|
include/ARCH/ioctl.h for specifics, e.g. powerpc
|
|
|
|
|
uses 3 bits to encode read/write and 13 bits for size.
|
|
|
|
|
|
|
|
|
|
bits meaning
|
|
|
|
|
31-30 00 - no parameters: uses _IO macro
|
|
|
|
|
10 - read: _IOR
|
|
|
|
|
01 - write: _IOW
|
|
|
|
|
11 - read/write: _IOWR
|
|
|
|
|
|
|
|
|
|
29-16 size of arguments
|
|
|
|
|
|
|
|
|
|
15-8 ascii character supposedly
|
|
|
|
|
unique to each driver
|
|
|
|
|
|
|
|
|
|
7-0 function #
|
|
|
|
|
|
|
|
|
|
|
2008-07-26 02:45:33 +00:00
|
|
|
So for example 0x82187201 is a read with arg length of 0x218,
|
2006-12-10 10:18:57 +00:00
|
|
|
character 'r' function 1. Grepping the source reveals this is:
|
|
|
|
|
|
|
|
|
|
#define VFAT_IOCTL_READDIR_BOTH _IOR('r', 1, struct dirent [2])
|
