Re: [9fans] raspberry pi kernel update

2018-06-14 Thread Richard Miller 
Sorry for posting twice, but the first attempt seems to have sat
on some server for a week:

> Received: from 002.las.mailroute.net ([199.89.4.5]
>   helo=relaycust-002.las.mailroute.net)
>   by mail.9fans.net with esmtp (Exim 4.71)
>   (envelope-from <...>) id 1fTGHE-j9-F9
>   for 9fans@9fans.net; Thu, 14 Jun 2018 00:38:12 +
> Received: from in-002.las.mailroute.net (002.las.mailroute.net [199.89.4.5])
>   (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
>   (No client certificate requested)
>   by relaycust-002.las.mailroute.net (Postfix) with ESMTPS id
>   4118xK05gNzLlhZ
>   for <9fans@9fans.net>; Wed,  6 Jun 2018 13:42:29 + (UTC)

[9fans] raspberry pi kernel update

2018-06-13 Thread Richard Miller 
I've made an update to the rpi 2 & 3 kernel source (armv7.s and rebootcode.s)
which fixes a couple of long-standing flaws in the multicore startup:

- dependency on the order of object files for the 5l command in the mkfile,
  resulting in "lock loop" or "only 1 cpu started" error for some configurations
- flakiness in /dev/reboot, making it unreliable except with *ncpu=1

It should now be possible consistently to reboot a pi in multicore mode from
a named file using the 'reboot' or 'fshalt -r' command.  This extends the
possibilities for using the Plan 9 kernel itself as a boot loader (with an rc
script as /boot/boot), eg to boot from an AoE server or over a wifi connection.

[9fans] raspberry pi kernel update

2018-06-13 Thread Richard Miller 
I've made an update to the rpi 2 & 3 kernel source (armv7.s and rebootcode.s
in /n/sources/contrib/miller/9/bcm) to correct a couple of long-standing
flaws in the multicore startup:

- dependency on the order of object files for the 5l command in the mkfile,
  resulting in "lock loop" or "only 1 cpu started" error for some configurations
- flakiness in /dev/reboot, making it unreliable except with *ncpu=1

It should now be possible consistently to reboot a pi in multicore mode from
a named file using the 'reboot' or 'fshalt -r' command.  This extends the
possibilities for using the Plan 9 kernel itself as a boot loader (with an rc
script as /boot/boot), eg to load a kernel from an AoE server or over wifi.