From: Magnus Damm <damm@opensource.se>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] hw/ide.c and WIN_STANDBYNOW1
Date: Thu, 22 Jul 2004 00:59:45 +0200 [thread overview]
Message-ID: <1090450785.14764.13.camel@kubu.opensource.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
Hi,
This stupid little fix adds dummy support for WIN_STANDBYNOW1.
It is probably not the right way to do it, though.
I'm happy with it because it makes my linux-2.6 kernel shut up.
Thanks.
/ magnus - not subscribed, please cc
Here's output from linux-2.6.8-rc2 with/without the patch:
with patch:
/ # poweroff
The system is going down NOW !!
Sending SIGTERM to all processes.
Sending SIGKILL to all processes.
Shutdown: hda
Power down.
without patch:
/ # poweroff
The system is going down NOW !!
Sending SIGTERM to all processes.
Sending SIGKILL to all processes.
Shutdown: hda
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
Power down.
[-- Attachment #2: qemu-20040722-ide_WIN_STANDBYNOW.patch --]
[-- Type: text/x-patch, Size: 544 bytes --]
Index: hw/ide.c
===================================================================
RCS file: /cvsroot/qemu/qemu/hw/ide.c,v
retrieving revision 1.26
diff -u -r1.26 ide.c
--- hw/ide.c 25 Jun 2004 14:54:19 -0000 1.26
+++ hw/ide.c 21 Jul 2004 22:51:07 -0000
@@ -1567,6 +1567,10 @@
goto abort_cmd;
}
break;
+ case WIN_STANDBYNOW1:
+ s->status = READY_STAT;
+ ide_set_irq(s);
+ break;
/* ATAPI commands */
case WIN_PIDENTIFY:
if (s->is_cdrom) {
reply other threads:[~2004-07-21 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1090450785.14764.13.camel@kubu.opensource.se \
--to=damm@opensource.se \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).