9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] German USB keyboard on Raspberry Pi
Date: Sun, 28 Apr 2013 22:14:10 +0100	[thread overview]
Message-ID: <486dbd2da9792666cb3badedaa39eaf7@hamnavoe.com> (raw)
In-Reply-To: <517D800D.6040507@ruhr-uni-bochum.de>

> #include "../omap/random.c"
>
> which should be
>
> #include "../port/random.c"
>
> Although it was easy to fix, I wonder where this inconsistency
> in the source tree came from. Did I miss an update or something?

I think you did.  /sys/src/9/bcm/random.c should have been deleted.

> Furthermore, I noticed that the build system would build _all_
> of the kernel each time I invoke 'mk', even though only little
> or nothing has changed. Is this the way it is intended to be?

Is your pi connected to the internet?  If not, its time will be
reset to the kernel build time each time you reboot (a function
of the "fakertc" device, which was probably not a very good idea).
When time goes backwards, 'mk' isn't able to do the right thing.

You could build a kernel without the fakertc device; then you'll
be prompted for date and time when you reboot.  Or connect to
the internet so the date can be set from ntp.




  parent reply	other threads:[~2013-04-28 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 16:31 Holger Sebert
2013-04-20 19:14 ` Bakul Shah
2013-04-20 20:08   ` Holger Sebert
2013-04-20 23:18     ` Bakul Shah
2013-04-24 19:25       ` Holger Sebert
2013-04-24 20:56         ` Bakul Shah
2013-04-25 20:38           ` Holger Sebert
2013-04-25 20:41             ` erik quanstrom
2013-04-28 20:01               ` Holger Sebert
2013-04-28 21:07                 ` Bakul Shah
2013-04-30 12:59                   ` Holger Sebert
2013-04-28 21:14                 ` Richard Miller [this message]
2013-04-30 13:05                   ` Holger Sebert
2013-04-30 14:16                     ` Richard Miller
2013-05-03 12:30                 ` arisawa
2013-04-26  7:07             ` Yaroslav
2013-04-26 12:02               ` erik quanstrom
2013-04-26 12:34                 ` Richard Miller
2013-04-26 12:36                   ` erik quanstrom

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=486dbd2da9792666cb3badedaa39eaf7@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).