From: John Stultz <john.stultz@linaro.org>
To: Kay Sievers <kay@vrfy.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes?
Date: Wed, 24 Apr 2013 09:33:58 -0700 [thread overview]
Message-ID: <51780976.8020608@linaro.org> (raw)
In-Reply-To: <CAPXgP10R0HSqOmq6LEW-Wqki1c7TyiemGwtUBEOopgZjWBNoOA@mail.gmail.com>
On 04/23/2013 08:51 PM, Kay Sievers wrote:
> On Wed, Apr 24, 2013 at 5:33 AM, Kay Sievers <kay@vrfy.org> wrote:
>
>> Also:
>> $ cat /sys/class/rtc/rtc0/hctosys
>> 0
>> always carried "1", and this now breaks setups which expect an
>> automatically created symlink /dev/rtc to the actual "system rtc".
> We used to do this in upstream standard udev rules:
> SUBSYSTEM=="rtc", ATTR{hctosys}=="1", MODE="0644"
> http://cgit.freedesktop.org/systemd/systemd/tree/rules/50-udev-default.rules#n18
>
> If that information is expected to be gone now, we need to update some
> tools. Whats' the proper way now to find the "system rtc" to use?
No we'll revert. Can't break userland.
But as to your question, if there's only one rtc, I'd consider it the
"system rtc", only adjusting the link if a second RTC appears and has
the hctosys flag set.
thanks
-john
next prev parent reply other threads:[~2013-04-24 16:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 1:34 CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes? Kay Sievers
2013-04-24 2:43 ` John Stultz
2013-04-24 3:05 ` Kay Sievers
2013-04-24 3:19 ` John Stultz
2013-04-24 3:33 ` Kay Sievers
2013-04-24 3:51 ` Kay Sievers
2013-04-24 16:33 ` John Stultz [this message]
2013-04-24 16:30 ` John Stultz
2013-04-24 16:51 ` Kay Sievers
2013-04-24 5:12 ` Alexander Holler
2013-04-24 16:07 ` John Stultz
2013-04-24 16:32 ` Kay Sievers
2013-04-24 16:42 ` John Stultz
2013-04-25 7:11 ` Alexander Holler
2013-04-25 16:01 ` Kay Sievers
2013-04-25 16:13 ` John Stultz
2013-04-25 18:33 ` Jason Gunthorpe
2013-04-25 19:45 ` Kay Sievers
2013-04-25 19:54 ` John Stultz
2013-04-25 20:35 ` Jason Gunthorpe
2013-04-25 20:03 ` John Stultz
2013-04-25 21:02 ` Jason Gunthorpe
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=51780976.8020608@linaro.org \
--to=john.stultz@linaro.org \
--cc=kay@vrfy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox