linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: a.zummo@towertech.it, rtc-linux@googlegroups.com,
	kernel list <linux-kernel@vger.kernel.org>,
	dbrownell@users.sourceforge.net
Subject: Re: RTC wakealarm write-only, still has 644 permissions
Date: Thu, 20 Sep 2007 12:50:02 +0200	[thread overview]
Message-ID: <20070920105002.GA4611@elf.ucw.cz> (raw)
In-Reply-To: <20070920103225.GA4410@elf.ucw.cz>

Hi!

> ...should they be changed to 200? Or perhaps file should be readable?
> 
> root@amd:/sys/class/rtc/rtc0# cat wakealarm 
> root@amd:/sys/class/rtc/rtc0# echo 132719 > wakealarm 
> root@amd:/sys/class/rtc/rtc0# ls -al wakealarm 
> -rw-r--r-- 1 root root 0 Sep 20 12:30 wakealarm
> root@amd:/sys/class/rtc/rtc0# cat wakealarm 
> root@amd:/sys/class/rtc/rtc0# cat wakealarm 
> root@amd:/sys/class/rtc/rtc0# 
> 
> 
> ...standard PC with reasonably recent kernel...

Hmm, something is definitely wrong in here. I sometimes _do_ get
something back.

root@amd:~# s2ram
Switching from vt9 to vt1


switching back to vt9
root@amd:~# 
root@amd:~# 
root@amd:~# cd /sys/class/rtc/rtc0
root@amd:/sys/class/rtc/rtc0# ls
date  dev  device@  name  power/  since_epoch  subsystem@  time
uevent  wakealarm
root@amd:/sys/class/rtc/rtc0# cat wakealarm 
2051629528
root@amd:/sys/class/rtc/rtc0# cat power/wakeup 

root@amd:/sys/class/rtc/rtc0# cat wakealarm 
2051629528
root@amd:/sys/class/rtc/rtc0# date +%s
1190285030
root@amd:/sys/class/rtc/rtc0# echo 1190285050 > wakealarm 
root@amd:/sys/class/rtc/rtc0# s2ram
Switching from vt9 to vt1


switching back to vt9
root@amd:/sys/class/rtc/rtc0# 
root@amd:/sys/class/rtc/rtc0# 
root@amd:/sys/class/rtc/rtc0# cat wakealarm 
root@amd:/sys/class/rtc/rtc0# cat wakealarm 
root@amd:/sys/class/rtc/rtc0# date +%s
1190285229
root@amd:/sys/class/rtc/rtc0# cat wakealarm 
root@amd:/sys/class/rtc/rtc0# 

Also, is there some documentation for wakealarm?

sh-3.1$ cd Documentation/
sh-3.1$ grep -ri wakealarm .

...is it time in seconds? In UTC? In whatever timezone rtc clocks are
using? It does not seem to work for me :-(.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-09-20 10:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20 10:32 RTC wakealarm write-only, still has 644 permissions Pavel Machek
2007-09-20 10:50 ` Pavel Machek [this message]
2007-09-22  5:38   ` David Brownell
2007-10-02  9:36     ` Pavel Machek
2007-10-03  2:15       ` David Brownell
2007-11-28 23:26     ` Pavel Machek
2007-11-29  8:02       ` Tino Keitel
2007-11-29 18:10       ` David Brownell
2007-11-29 18:14         ` Alessandro Zummo
2007-11-30 20:35         ` Pavel Machek
2007-11-30 21:10           ` David Brownell
2007-11-30 21:20             ` Mark Lord
2007-11-30 21:27               ` Pavel Machek
2007-12-02 11:36             ` Pavel Machek
2007-12-02 16:03               ` David Brownell
     [not found]     ` <20071128230451.GA1547@elf.ucw.cz>
2007-11-28 23:26       ` Pavel Machek

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=20070920105002.GA4611@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=a.zummo@towertech.it \
    --cc=dbrownell@users.sourceforge.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).