From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: rtc-linux@googlegroups.com
Cc: macro@linux-mips.org, Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
rongkai.zhan@windriver.com, i2c@lm-sensors.org,
linux-mips@linux-mips.org, ralf@linux-mips.org,
a.zummo@towertech.it
Subject: Re: [rtc-linux] Re: [PATCH 4/4] MIPS: Remove the legacy RTC codes of MIPS sibyte boards
Date: Tue, 2 Oct 2007 15:14:15 +0200 [thread overview]
Message-ID: <20071002151415.672d0a1e@i1501.lan.towertech.it> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710012001300.27280@blysk.ds.pg.gda.pl>
On Mon, 1 Oct 2007 20:08:55 +0100 (BST)
"Maciej W. Rozycki" <macro@linux-mips.org> wrote:
> > > Is the system time still set correctly from the RTC chip upon bootstrap
> > > with your changes? I cannot immediately infer it from the patches and my
> > > suspicion is it may not anymore.
> >
> > CONFIG_RTC_HCTOSYS=y can do it, isn't it?
>
> Hmm, I wonder whether this shouldn't be enabled via a reverse dependency.
> Or even unconditionally perhaps -- if the initial system time gets set
> from incorrect RTC time (e.g. because it is not battery-backed) it does
> not get less correct than it would be otherwise, does it?
>
> Any reason for not doing either of these?
CONFIG_RTC_HCTOSYS defaults to YES, it should be enough...?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2007-10-02 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 9:55 [PATCH 4/4] MIPS: Remove the legacy RTC codes of MIPS sibyte boards Mark Zhan
2007-10-01 4:22 ` Ralf Baechle
2007-10-01 15:10 ` Maciej W. Rozycki
2007-10-01 15:30 ` Atsushi Nemoto
2007-10-01 19:08 ` Maciej W. Rozycki
2007-10-02 13:14 ` Alessandro Zummo [this message]
2007-10-03 13:55 ` [rtc-linux] " Maciej W. Rozycki
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=20071002151415.672d0a1e@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=a.zummo@towertech.it \
--cc=anemo@mba.ocn.ne.jp \
--cc=i2c@lm-sensors.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rongkai.zhan@windriver.com \
--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