9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@plan9.bell-labs.com
To: 9fans@9fans.net
Subject: [9fans] sheevaplug port available
Date: Tue, 17 Nov 2009 16:37:27 -0500	[thread overview]
Message-ID: <9c855ecc7b4384e9a3ecb9ca2416ecac@plan9.bell-labs.com> (raw)

If you run replica/pull (or have done so recently), you'll find a new
kernel subtree, /sys/src/9/kw, which contains a basic port of Plan 9
to the Sheevaplug, derived from the port of native Inferno.  9plug is
a diskless cpu server supporting a serial console and gigabit
ethernet.  booting(8) and /sys/doc/port.* have been updated to match.
`kw' stands for Kirkwood, the Marvell system-on-a-chip that the
Sheevaplug is based upon.  There are more Kirkwood systems on the way.

What's not yet in this port: access to flash memory, USB devices,
memory cards and possibly more.  The documentation for Kirkwood flash
and USB is some combination of vague, obscure, incomplete,
unavailable, contradictory and tediously voluminous.  If you configure
in the USB drivers, you'll find that there appears to be an
unpopulated root hub, but that may be a figment of the usb driver's
imagination.  The EHCI registers do seem to be present and we probably
just need to tweak some undocumented register to make it all go.

If you only been building 386 binaries to date, you'll want to edit
/sys/src/mkfile.proto to at least include the arm architecture:

	OS=58
	CPUS=arm 386

and make sure all your /386/bin compiler binaries are up to date:

	cd /sys/src/cmd
	for(i in ?c)
		if(! ~ $i cc rc) @{
			cd $i
			mk clean
			objtype=$cputype mk install
			mk clean
		}

and populate your /arm tree:

	cd /sys/src
	objtype=arm mk install

You should then be able to build a sheeva kernel:

	cd /sys/src/9/kw
	mk 'CONF=plug' install	# `mk install' will work too

This should create /arm/9plug; see booting(8) to get started.

Enjoy!



             reply	other threads:[~2009-11-17 21:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 21:37 geoff [this message]
2009-11-17 21:43 ` David Leimbach
2009-11-17 22:04 ` Steve Simon
2009-11-17 23:51   ` Tharaneedharan Vilwanathan
2010-02-24 18:53 ` Jacob Todd
2010-02-24 20:22   ` geoff
2010-02-25  8:58     ` Francisco J Ballesteros
2010-02-28  5:11       ` kazumi iwane
2010-02-28  6:06         ` geoff
2010-02-28  8:02           ` kazumi iwane
2010-03-08 15:42     ` Mechiel Lukkien
2010-03-08 15:45       ` David Leimbach
2010-03-08 16:02         ` erik quanstrom
2010-03-09 15:38       ` Graham Gallagher
2010-03-09 15:57       ` Axel Belinfante
2010-03-09 16:30         ` Graham Gallagher
2010-10-19 19:14 ` James Chapman
2010-10-19 19:21   ` ron minnich
2010-10-19 19:45     ` Lyndon Nerenberg
2010-10-19 19:50       ` ron minnich
2010-10-19 20:00         ` Lyndon Nerenberg
2010-10-19 19:34   ` geoff
2010-10-20 20:11   ` Benjamin Huntsman
2010-10-20 20:22     ` Skip Tavakkolian
2010-10-20 20:29     ` erik quanstrom
2010-10-21  8:23       ` Benjamin Huntsman
2010-10-21  9:10         ` Steve Simon
2010-10-21 16:43           ` ron minnich
2010-10-21 18:09           ` Yaroslav
2010-10-21  9:35         ` Lucio De Re
2010-10-21 11:08         ` erik quanstrom
2010-10-21 16:53           ` Benjamin Huntsman
2010-10-21 17:37             ` Steve Simon
2010-10-21 18:04               ` Benjamin Huntsman
2010-10-21 18:17                 ` Yaroslav
2010-10-21 20:43                 ` Brian L. Stuart
2010-10-21 21:58                   ` Benjamin Huntsman
2010-10-22 17:19                     ` Benjamin Huntsman
2010-10-21 17:52             ` erik quanstrom
2010-10-21 20:40             ` Brian L. Stuart
2010-10-21 20:59               ` erik quanstrom
2010-10-21 15:30         ` ron minnich
     [not found] <<9c855ecc7b4384e9a3ecb9ca2416ecac@plan9.bell-labs.com>
2009-11-18 21:27 ` erik quanstrom
2009-11-18 23:26   ` geoff
2009-11-18 23:32   ` geoff
     [not found] <<3b93ad835e55404cc726f5314ee966fa@plan9.bell-labs.com>
2009-11-19  0:17 ` 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=9c855ecc7b4384e9a3ecb9ca2416ecac@plan9.bell-labs.com \
    --to=geoff@plan9.bell-labs.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).