From: Igor Plyatov <plyatov@gmail.com>
To: Karel Zak <kzak@redhat.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: linux-kernel@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
rtc-linux@googlegroups.com, util-linux@vger.kernel.org,
J William Piggott <elseifthen@gmx.com>
Subject: Re: 500 ms delay in time saved into RTC
Date: Mon, 19 Feb 2018 14:31:23 +0300 [thread overview]
Message-ID: <0ce68f3f-fec7-1f1c-e70b-331c0752f6d6@gmail.com> (raw)
In-Reply-To: <20180219110328.n7yjorinjm3xxckr@ws.net.home>
Dear Karel,
> Would be possible to somehow detect what is the right default setting for
> --delay? I mean for example detect architecture / clock HW, etc.
>
> I have no problem with --delay, but it's tuning for advanced users and
> HW specific stuff. It would be nice to have something more portable.
>
> Karel
>
As I understood, issue exists only at x86 platform, where
MC146818-compatible RTC used.
But even if you will correctly detect platform, there is no guaranty to
get exactly MC146818 RTC. RTC can be other type. It even can be not
single in the system.
What is more or less usable is "/sys/class/rtc/rtcX/name" file, which
contains driver name.
For x86 and MC146818-compatible RTC its name is "rtc_cmos". And it can
be used to distinguish RTC type by hwclock utility.
Best wishes.
--
Igor Plyatov
next prev parent reply other threads:[~2018-02-19 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 6:40 500 ms delay in time saved into RTC Igor Plyatov
2018-02-19 7:11 ` Rasmus Villemoes
2018-02-19 9:16 ` Igor Plyatov
2018-02-19 10:07 ` Alexandre Belloni
2018-02-19 10:37 ` Rasmus Villemoes
2018-02-19 11:03 ` Karel Zak
2018-02-19 11:31 ` Igor Plyatov [this message]
2018-02-25 0:34 ` Alexandre Belloni
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=0ce68f3f-fec7-1f1c-e70b-331c0752f6d6@gmail.com \
--to=plyatov@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=elseifthen@gmx.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=rtc-linux@googlegroups.com \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).