From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fwd: Building a Raspberry Pi image / Keyboard support
Date: Mon, 7 Jul 2014 07:58:15 -0700 [thread overview]
Message-ID: <F8589047-10C2-4647-893C-FF1C2F4878E0@bitblocks.com> (raw)
In-Reply-To: <CAJSxfmJbGvT4ginpEEEmxVT3wUrRvxtPGKkVhwmKi6oEmiaxNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On one RPi I am using a GPS module. I need to add support for its PPS signal for more accurate time keeping.
> On Jul 7, 2014, at 7:39 AM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>
> there are RTC modules for the pi (talk over i2c, based on DS1307 or DS3231). i use them with linux distro's and they seem to work fine.
>
>
>
>> On Mon, Jul 7, 2014 at 6:59 AM, Richard Miller <9fans@hamnavoe.com> wrote:
>> > By the way, how I can arrage the correct time in this system?
>> > I don't mean the /adm/timezone/local, because
>> > in the usual PC, we can change it at BIOS screen.
>>
>> Unlike a PC, the raspberry pi doesn't have a battery-backed
>> real time clock. If you configure a kernel without the 'fakertc'
>> device, it will prompt you to enter the time and date when you
>> power on. For me this was too annoying, which is why I made the
>> fakertc device. With a network connection, the time should be
>> corrected by aux/timesync soon after booting.
>
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2014-07-07 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6D8D77BA-B884-43B8-B23B-69A1823EA275@hamnavoe.com>
2014-07-07 13:59 ` Richard Miller
2014-07-07 14:39 ` Skip Tavakkolian
2014-07-07 14:58 ` Bakul Shah [this message]
2014-07-07 23:53 ` kokamoto
2014-07-08 0:19 ` Skip Tavakkolian
2014-07-08 0:37 ` erik quanstrom
2014-07-08 16:00 ` Kurt H Maier
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=F8589047-10C2-4647-893C-FF1C2F4878E0@bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/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).