From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: david-b@pacbell.net
Subject: RTC_DRV_CMOS can break userspace interface
Date: Sun, 27 May 2007 20:03:51 +0100 [thread overview]
Message-ID: <20070527190351.GA21387@srcf.ucam.org> (raw)
f5f72b46c349fefcfd4421b2213c6ffb324c5e56 appears to break the userspace
interface to the CMOS alarm. This could previously be accessed via
/proc/acpi/alarm, but if RTC_DRV_CMOS is enabled that vanishes. The help
text for the module doesn't mention this, which makes tracking it down a
touch irritating.
I'm not actually sure why this is the case. It doesn't look like the two
interfaces are fundamentally incompatible. I agree that removing the
proc code is a good long-term aim, but it'd be nice to be able to test
the new RTC code without removing existing functionality.
(It doesn't really help that rtc-cmos doesn't load on this machine, but
I'll try to track that down later - right now I suspect some sort of PNP
issue)
--
Matthew Garrett | mjg59@srcf.ucam.org
next reply other threads:[~2007-05-27 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 19:03 Matthew Garrett [this message]
2007-05-27 23:39 ` RTC_DRV_CMOS can break userspace interface Matthew Garrett
2007-05-28 0:38 ` Matthew Garrett
2007-05-28 1:44 ` David Brownell
2007-05-28 2:16 ` Matthew Garrett
2007-05-28 7:45 ` Matthieu CASTET
2007-05-28 19:16 ` Matthew Garrett
2007-05-28 17:24 ` [PATCH] RTC: Use fallback IRQ if PNP tables don't provide one Matthew Garrett
2007-05-28 18:50 ` Matthieu CASTET
2007-05-30 0:30 ` Andrew Morton
2007-05-30 1:02 ` Matthew Garrett
2007-05-28 21:06 ` David Brownell
2007-05-28 1:36 ` RTC_DRV_CMOS can break userspace interface David Brownell
[not found] <8pwhX-46n-3@gated-at.bofh.it>
[not found] ` <8pCQo-5QL-7@gated-at.bofh.it>
[not found] ` <87abvogbdp.fsf@buer.dfakt.de>
2007-05-28 21:06 ` David Brownell
2007-05-31 4:32 ` Tino Keitel
2007-05-31 10:26 ` Matthew Garrett
2007-06-01 7:46 ` Tino Keitel
2007-06-01 12:54 ` Matthew Garrett
2007-06-01 17:11 ` David Brownell
2007-06-04 9:35 ` Tino Keitel
2007-06-04 12:14 ` Matthew Garrett
2007-06-12 18:17 ` Tino Keitel
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=20070527190351.GA21387@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=david-b@pacbell.net \
--cc=linux-acpi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.