From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] "gpio device" for Plan 9
Date: Wed, 1 Jan 2014 11:38:07 +0000 [thread overview]
Message-ID: <3d691e0d0512e64e471282024a0b4589@hamnavoe.com> (raw)
In-Reply-To: <4657D0DD-A119-4E19-B50D-EBCE5861F9F8@gmail.com>
> I tried to look at 9front BCM tree, it seems to be a bit different (no fakertc device for example) from the one at Bell Labs, is it by purpose or just trees are not synched? I'm asking because i have 9front on my laptop and i'd like to build BCM kernel there, and so i thought maybe i could use 9pi from 9front image instead, but i'd like to know what is the status.
If you want your work to be useful to the Plan 9 community (and I hope you do), please
stay with us and improve the real Plan 9.
You can safely leave out the fakertc driver when building a bcm kernel. The
only consequence is that you'll be prompted for date and time when booting with
root filesystem on the local SD card (because the Pi doesn't have a rtc). If
your root fs comes from another server (which I recommend), fakertc isn't used.
next prev parent reply other threads:[~2014-01-01 11:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 22:04 Krystian Lewandowski
2013-12-29 22:34 ` erik quanstrom
2013-12-30 7:32 ` Skip Tavakkolian
2013-12-30 22:38 ` Shane Morris
[not found] ` <35A33F66-EF03-4659-ABA1-F25082DBFE41@gmail.com>
2013-12-31 17:46 ` Krystian Lewandowski
2013-12-31 19:18 ` erik quanstrom
2013-12-31 19:37 ` Shane Morris
2013-12-31 19:48 ` Skip Tavakkolian
2013-12-31 19:50 ` erik quanstrom
2013-12-31 20:45 ` Shane Morris
2013-12-31 22:03 ` erik quanstrom
2013-12-31 22:17 ` Shane Morris
2013-12-31 22:52 ` erik quanstrom
2013-12-31 22:57 ` Krystian Lewandowski
2013-12-31 23:16 ` Shane Morris
2013-12-31 23:35 ` Shane Morris
2014-01-01 0:04 ` Krystian Lewandowski
2014-01-01 0:12 ` Shane Morris
2014-01-01 1:12 ` Matthew Veety
2014-01-01 11:38 ` Richard Miller [this message]
2014-01-01 22:16 ` erik quanstrom
2014-02-28 23:30 ` Krystian Lewandowski
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=3d691e0d0512e64e471282024a0b4589@hamnavoe.com \
--to=9fans@hamnavoe.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).