From: "Kolbjørn Barmen" <linux-m68k@kolla.no>
To: Riccardo <riccardo@kaffe.org>
Cc: Brad Boyer <flar@allandria.com>,
Finn Thain <fthain@telegraphics.com.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] reinstate mac rtc
Date: Sat, 18 Oct 2008 19:39:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.0810181928560.1848@firda.kolla.no> (raw)
In-Reply-To: <A4BCBF08-9D05-11DD-9A2B-00050249ADE1@kaffe.org>
On Sat, 18 Oct 2008, Riccardo wrote:
> I don't know "how", but with 2.2 kernels I always had a correct date at
> boot without any tricks. It is true though that with high CPU load we
> had clockskew and that we didn't save back the date and hourtime to the
> clock, thus any clock setting needed to be done from the mac side. A
> compromoise, but better than the current situation.
The clockproblem is something I stumble upon every now and then on
various machinees - I really wish there was a kernel parameter where one
could set a date string, then the bootloader could pass it on.
Currently i use a /.timestamp file that I read from init=/sbin/init.noclock;
---
firda ~ # cat /sbin/init.noclock
#! /bin/bash
if test $(/bin/date +%Y) -lt 2008 ; then
/bin/date -s "1970-01-01 + $(($(/bin/stat -c %X /.timestamp) +3600)) seconds"
fi
exec /sbin/init
---
I make sure the .timestamp is touched regularly and on shutdown.
This trick I now use on quadra910, an old acer laptop, gumstix ... :P
-- kolla
next prev parent reply other threads:[~2008-10-18 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0810061855300.28882@loopy.telegraphics.com.au>
2008-10-13 19:21 ` [PATCH] reinstate mac rtc Geert Uytterhoeven
2008-10-14 2:16 ` Finn Thain
2008-10-14 7:30 ` Geert Uytterhoeven
2008-10-15 21:41 ` Riccardo
2008-10-16 1:02 ` Finn Thain
2008-10-16 6:49 ` Brad Boyer
2008-10-18 11:12 ` Riccardo
2008-10-18 17:39 ` Kolbjørn Barmen [this message]
2008-10-19 2:53 ` Finn Thain
2008-10-19 16:37 ` Kolbjørn Barmen
2008-10-20 2:03 ` Finn Thain
2008-10-20 2:05 ` Michael Schmitz
2008-10-20 19:13 ` Laurent Vivier
2008-10-22 7:19 ` Michael Schmitz
2008-10-22 11:09 ` Kolbjørn Barmen
2008-10-22 22:14 ` Laurent Vivier
2008-10-23 3:56 ` Michael Schmitz
2008-10-23 7:28 ` Geert Uytterhoeven
2008-10-23 7:39 ` Geert Uytterhoeven
2008-10-24 2:49 ` Michael Schmitz
2008-10-25 4:24 ` Michael Schmitz
2008-10-25 5:10 ` Finn Thain
2008-10-25 7:08 ` Finn Thain
2008-10-26 3:04 ` Michael Schmitz
2008-10-26 3:24 ` Finn Thain
2008-10-19 11:52 ` Finn Thain
2008-10-18 16:17 ` Riccardo
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=alpine.LNX.2.00.0810181928560.1848@firda.kolla.no \
--to=linux-m68k@kolla.no \
--cc=flar@allandria.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=riccardo@kaffe.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