From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: rtc-linux@googlegroups.com,
Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
linux-kernel@vger.kernel.org,
David Brownell <david-b@pacbell.net>
Subject: Re: [rtc-linux] Re: rtc_cmos: error after first write to wakealarm
Date: Fri, 22 Jun 2007 19:34:31 +0200 [thread overview]
Message-ID: <20070622193431.71bed8b5@inspiron> (raw)
In-Reply-To: <20070619172429.GA30990@dose.home.local>
On Tue, 19 Jun 2007 19:24:29 +0200
Tino Keitel <tino.keitel@gmx.de> wrote:
> > > Where is the documentation that describes that I have to disable it
> > > first, and how to do this? A migration document for
> > > /proc/acpi/alarm users would be nice, too.
> >
> > Well, I guess there is no documentation. Maybe we could add
> > a dev_warn with an explicit message.
>
> Isn't it somewhat ridiculous to plan the removal of a feature for
> several months, and then replace it with something that behaves
> differently without any documentation?
>
> I still wonder how 'cat /sys/class/rtc/rtcX/wakealarm' is expected to
> behave. With 2.6.22-rc5, I get this:
>
> $ echo 1182351177 > /sys/class/rtc/rtc0/wakealarm
> $ cat /sys/class/rtc/rtc0/wakealarm
> 2051644873
>
> There seems to be a constant difference of 869984896 seconds. Is this a
> bug?
I'll have to check that. Sorry for the delay, i've been a bit busy.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2007-06-22 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 6:33 rtc_cmos: error after first write to wakealarm Tino Keitel
2007-06-15 6:59 ` Yoichi Yuasa
2007-06-15 7:03 ` Tino Keitel
2007-06-19 12:24 ` [rtc-linux] " Alessandro Zummo
2007-06-19 17:24 ` Tino Keitel
2007-06-22 17:34 ` Alessandro Zummo [this message]
2007-06-22 18:45 ` David Brownell
2007-06-22 19:44 ` Tino Keitel
2007-06-23 3:18 ` 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=20070622193431.71bed8b5@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tino.keitel@gmx.de \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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