From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <52e48b688f49ed8ed3c34b0a60217c7e@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] supported ipaq's?
From: Sape Mullender <sape@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 25 Jun 2002 10:26:27 +0200
Topicbox-Message-UUID: b79df2bc-eaca-11e9-9e20-41e7f4b1d025

> i've been trying to get plan9 working on an ipaq (well i spent
> some of last night doing it).  i had some successes and some
> failures.
>
> i can't get the latest bootldr to boot 9 from flash.  it looks
> to me like the boot formats must have changed.  i can boot a
> kernel from ram (using "load ram", "call 0xc....") and it runs
> but the kernel is in an unrecognised format if it tries to
> boot automatically.

One change I discovered is that the Linux boot loader for the bitsy
now recognizes more than one boot format.  If you create the
partitions and load a kernel and paqdisk, you should give the
command `boot flash' to boot Plan 9.

You can set the boot parameter to `flash'
	set boottype flash
if memory serves me (maybe it's boot_type) and
	save params
to make that permanent.

> it looks like the paqdisk that i've generated is broken.  the
> ipaq tries to boot off it but can't find /bin/rc.  if i
> mount the paqdisk locally (paqfs paqdisk) i get a broken
> process whenever i try to access anything other than the
> root directory).

When the kernel starts up, the first thing it should print is a
fingerprint of the paqdisk.  If that succeeds, the paqdisk format
is correct.  If /bin/rc still can't be found, check that you've installed
arm binaries before making a paqdisk.  `mk paqdisk' will take many files
from /arm but will not install them there if they don't exist.
However, mkfs will complain about missing files.

Let me know how you fare.

	Sape