From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <57ece7d1ad48bf86341bfc4b533fea30@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Sat, 17 Aug 2013 14:30:14 +0100
In-Reply-To: <520F6787.1090705@ruhr-uni-bochum.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Realtime clock on the Raspberry Pi
Topicbox-Message-UUID: 719f8682-ead8-11e9-9d60-3106f5b1d025

> In order to use, I put the following line into my profile:
>
> bind -a '#r' /dev
>
> The realtime-clock seems to be successfully recognized
> by the system as device /dev/rtc. However, Plan 9 does
> not seem to use it; after every reboot the date and
> time is reset.

The '#r' device for the raspberry pi (/sys/src/9/bcm/devfakertc.c)
is not an actual clock driver, just a hack to prevent annoying prompts
for date and time when booting by using the kernel build time as an
initial guess.  It probably wasn't a good idea, because if you aren't
connected to a network to get the time corrected by aux/timesync,
your clock will go backwards every time you boot.  This confuses things
like "mk".

If you want to use the RasClock (looks like a useful device), you
(or somebody) will need to write a driver for it.

And if anyone wants to stop being misled by the fakertc device, just
comment it out in /sys/src/9/bcm/pi and build a new kernel...