| To: | Atsushi Nemoto <anemo@mba.ocn.ne.jp> |
|---|---|
| Subject: | Re: [PATCH 4/4] MIPS: Remove the legacy RTC codes of MIPS sibyte boards |
| From: | "Maciej W. Rozycki" <macro@linux-mips.org> |
| Date: | Mon, 1 Oct 2007 20:08:55 +0100 (BST) |
| Cc: | rongkai.zhan@windriver.com, i2c@lm-sensors.org, linux-mips@linux-mips.org, rtc-linux@googlegroups.com, ralf@linux-mips.org, a.zummo@towertech.it |
| In-reply-to: | <20071002.003020.21363605.anemo@mba.ocn.ne.jp> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <46FF7283.7050702@windriver.com> <Pine.LNX.4.64N.0710011608130.27280@blysk.ds.pg.gda.pl> <20071002.003020.21363605.anemo@mba.ocn.ne.jp> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Tue, 2 Oct 2007, Atsushi Nemoto 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? Maciej |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: linux cache routines for Write-back cache policy on MIPS24KE, veerasena reddy |
|---|---|
| Next by Date: | Re: linux cache routines for Write-back cache policy on MIPS24KE, veerasena reddy |
| Previous by Thread: | Re: [PATCH 4/4] MIPS: Remove the legacy RTC codes of MIPS sibyte boards, Atsushi Nemoto |
| Next by Thread: | Re: [rtc-linux] Re: [PATCH 4/4] MIPS: Remove the legacy RTC codes of MIPS sibyte boards, Alessandro Zummo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |