[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
No Subject
I was browsing around in the docs and thought the below might be nice.
I don't feel competent enough to wade into the 'conflicts!' but pointing
them out, and showing how to call "_IO?", might help someone else fix
them.
Dave.
--- linux/Documentation/ioctl-number.txt.dist Sat Aug 7 18:02:45 1999
+++ linux/Documentation/ioctl-number.txt Sat Aug 7 18:18:18 1999
@@ -6,10 +6,10 @@
If you are adding new ioctl's to the kernel, you should use the _IO
macros defined in <linux/ioctl.h>:
- _IO an ioctl with no parameters
- _IOW an ioctl with write parameters (from user's point of view)
- _IOR an ioctl with read parameters (from user's point of view)
- _IOWR an ioctl with both write and read parameters.
+ _IO(type,nr) an ioctl with no parameters
+ _IOW(type,nr,size) an ioctl with write parameters
+ _IOR(type,nr,size) an ioctl with read parameters
+ _IOWR(type,nr,size) an ioctl with both write and read parameters.
'Write' and 'read' are from the user's point of view. This is like the
system calls 'write' and 'read'. For example, a SET_FOO ioctl would be
@@ -55,7 +55,8 @@
Code Seq# Include File Comments
========================================================
0x00 01-02 linux/fs.h conflict!
-0x00 01-04 scsi/scsi_ioctl.h conflict!
+0x00 01-06 scsi/scsi_ioctl.h conflict!
+0x00 03 drivers/scsi/hosts.h conflict!
0x02 all linux/fd.h
0x03 all linux/hdreg.h
0x04 all linux/umsdos_fs.h
--
Dave Forrest dforrest@virginia.edu
(804)-296-7283 http://www.people.virginia.edu/~drf5n/
--- linux/Documentation/ioctl-number.txt.dist Sat Aug 7 18:02:45 1999
+++ linux/Documentation/ioctl-number.txt Sat Aug 7 18:18:18 1999
@@ -6,10 +6,10 @@
If you are adding new ioctl's to the kernel, you should use the _IO
macros defined in <linux/ioctl.h>:
- _IO an ioctl with no parameters
- _IOW an ioctl with write parameters (from user's point of view)
- _IOR an ioctl with read parameters (from user's point of view)
- _IOWR an ioctl with both write and read parameters.
+ _IO(type,nr) an ioctl with no parameters
+ _IOW(type,nr,size) an ioctl with write parameters
+ _IOR(type,nr,size) an ioctl with read parameters
+ _IOWR(type,nr,size) an ioctl with both write and read parameters.
'Write' and 'read' are from the user's point of view. This is like the
system calls 'write' and 'read'. For example, a SET_FOO ioctl would be
@@ -55,7 +55,8 @@
Code Seq# Include File Comments
========================================================
0x00 01-02 linux/fs.h conflict!
-0x00 01-04 scsi/scsi_ioctl.h conflict!
+0x00 01-06 scsi/scsi_ioctl.h conflict!
+0x00 03 drivers/scsi/hosts.h conflict!
0x02 all linux/fd.h
0x03 all linux/hdreg.h
0x04 all linux/umsdos_fs.h