From: Doug Maxey <dwm@austin.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: ppc64 HDIO_TASK_* ioctls 2.4, 2.6
Date: Wed, 12 May 2004 17:09:57 -0500 [thread overview]
Message-ID: <200405122209.i4CM9vqS013716@falcon10.austin.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 237 bytes --]
Howdy,
I need a some guidance on enabling the ioctls on ppc64 to allow
the smartmontools to run the appropriate set of commands.
Does this look ok?
Have sniff tested, and the smart tools do run without ioctl errors.
++doug
[-- Attachment #2: ppc64-26-hdio-ioctls.diff --]
[-- Type: application/octet-stream , Size: 773 bytes --]
Index: arch/ppc64/kernel/ioctl32.c
===================================================================
RCS file: /cvs/linuxppc64/sles-9-7/arch/ppc64/kernel/ioctl32.c,v
retrieving revision 1.1.1.1
diff -w -p -u -r1.1.1.1 ioctl32.c
--- arch/ppc64/kernel/ioctl32.c 4 May 2004 16:43:27 -0000 1.1.1.1
+++ arch/ppc64/kernel/ioctl32.c 10 May 2004 14:46:20 -0000
@@ -349,6 +349,11 @@ COMPATIBLE_IOCTL(TIOCSLTC)
/* Little p (/dev/rtc, /dev/envctrl, etc.) */
COMPATIBLE_IOCTL(_IOR('p', 20, int[7])) /* RTCGET */
COMPATIBLE_IOCTL(_IOW('p', 21, int[7])) /* RTCSET */
+COMPATIBLE_IOCTL(HDIO_DRIVE_CMD)
+#ifdef CONFIG_IDE_TASK_IOCTL
+COMPATIBLE_IOCTL(HDIO_DRIVE_TASKFILE),
+COMPATIBLE_IOCTL(HDIO_DRIVE_TASK),
+#endif CONFIG_IDE_TASK_IOCTL
/* And these ioctls need translation */
[-- Attachment #3: ppc64-24-hdio-ioctls.diff --]
[-- Type: application/octet-stream , Size: 822 bytes --]
Index: arch/ppc64/kernel/ioctl32.c
===================================================================
RCS file: /cvs/linuxppc64/sles8-sp3aa/arch/ppc64/kernel/ioctl32.c,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.2.3
diff -w -p -u -r1.1.1.1 -r1.1.1.1.2.3
--- arch/ppc64/kernel/ioctl32.c 23 Apr 2004 15:59:34 -0000 1.1.1.1
+++ arch/ppc64/kernel/ioctl32.c 6 May 2004 00:31:17 -0000 1.1.1.1.2.3
@@ -3846,6 +3846,10 @@ COMPATIBLE_IOCTL(HDIO_SET_UNMASKINTR),
COMPATIBLE_IOCTL(HDIO_SET_NOWERR),
COMPATIBLE_IOCTL(HDIO_SET_32BIT),
COMPATIBLE_IOCTL(HDIO_SET_MULTCOUNT),
+#ifdef CONFIG_IDE_TASK_IOCTL
+COMPATIBLE_IOCTL(HDIO_DRIVE_TASKFILE),
+COMPATIBLE_IOCTL(HDIO_DRIVE_TASK),
+#endif CONFIG_IDE_TASK_IOCTL
COMPATIBLE_IOCTL(HDIO_DRIVE_CMD),
COMPATIBLE_IOCTL(HDIO_SET_PIO_MODE),
COMPATIBLE_IOCTL(HDIO_SCAN_HWIF),
next reply other threads:[~2004-05-12 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:09 Doug Maxey [this message]
2004-05-12 22:47 ` Bartlomiej Zolnierkiewicz
2004-05-13 7:30 ` Bruce Allen
2004-05-12 22:53 Doug Maxey
2004-05-12 23:03 ` Bartlomiej Zolnierkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200405122209.i4CM9vqS013716@falcon10.austin.ibm.com \
--to=dwm@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®