From: Ingo Molnar <mingo@elte.hu>
To: David Brownell <david-b@pacbell.net>
Cc: rtc-linux@googlegroups.com,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.24-rc3] rtc-cmos alarm acts as oneshot
Date: Sat, 1 Dec 2007 08:44:00 +0100 [thread overview]
Message-ID: <20071201074400.GA14709@elte.hu> (raw)
In-Reply-To: <200711301418.24033.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> wrote:
> Start making the rtc-cmos alarm act more like a oneshot alarm by
> disabling that alarm after its IRQ fires. (ACPI hooks are also
> needed.)
>
> The Linux RTC framework has previously been a bit vague in this area,
> but any other behavior is problematic and not very portable. RTCs
> with full YYYY-MM-DD HH:MM[:SS] alarms won't have a problem here.
> Only ones with partial match criteria, with the most visible example
> being the PC RTC, get confused. (Because the criteria will match
> repeatedly.)
>
> Update comments relating to that oneshot behavior and timezone
> handling. (Timezones are another issue that's mostly visible with
> rtc-cmos. That's because PCs often dual-boot MS-Windows, which likes
> its RTC to match local wall-clock time instead of UTC.)
Cool. I'm still wondering about:
http://bugzilla.kernel.org/show_bug.cgi?id=7014
basically, we had universally working /dev/rtc before, now it appears we
dont have it anymore. Or were the problems in this bugzilla present with
the old code too?
Ingo
next prev parent reply other threads:[~2007-12-01 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 22:18 [patch 2.6.24-rc3] rtc-cmos alarm acts as oneshot David Brownell
2007-12-01 7:44 ` Ingo Molnar [this message]
2007-12-01 8:20 ` David Brownell
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=20071201074400.GA14709@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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).