From: Paul Brook <paul@nowt.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [7062] Fix RTC breakage from r7031.
Date: Fri, 10 Apr 2009 02:19:53 +0000 [thread overview]
Message-ID: <E1Ls6LR-0002qx-7b@cvs.savannah.gnu.org> (raw)
Revision: 7062
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=7062
Author: pbrook
Date: 2009-04-10 02:19:52 +0000 (Fri, 10 Apr 2009)
Log Message:
-----------
Fix RTC breakage from r7031.
Signed-off-by: Paul Brook <paul@codesourcery.com>
Modified Paths:
--------------
trunk/hw/mc146818rtc.c
Modified: trunk/hw/mc146818rtc.c
===================================================================
--- trunk/hw/mc146818rtc.c 2009-04-10 01:24:26 UTC (rev 7061)
+++ trunk/hw/mc146818rtc.c 2009-04-10 02:19:52 UTC (rev 7062)
@@ -104,7 +104,7 @@
/* disable periodic timer if hpet is in legacy mode, since interrupts are
* disabled anyway.
*/
- enable_pie = hpet_in_legacy_mode();
+ enable_pie = !hpet_in_legacy_mode();
#else
enable_pie = 1;
#endif
reply other threads:[~2009-04-10 2:19 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=E1Ls6LR-0002qx-7b@cvs.savannah.gnu.org \
--to=paul@nowt.org \
--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).