9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Stephen Parker <stephen.parker@pitechnology.com>
To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu>
Subject: RE: [9fans] supported ipaq's?
Date: Tue, 25 Jun 2002 16:51:26 +0100	[thread overview]
Message-ID: <E562FCEE3A42D61192880002A5FB43330A6350@kite.pigroup.co.uk> (raw)

> 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.

i've tried this.  i seem to recall that i got an "unreckognised
magic number in kernel" type of message.  certainly looking
through the boot loader code it looks as if its looking for
stuff in the kernel image that's not there in the 9 kernel.
i guess i'll probably end up going back to an earlier bootloader
but i'm trying to avoid messing with the boot sector too
much (i wouldn't be surprised if we've got the jtag gear here
but i don't really want to have to try it).

> 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.

the thing that bothers me most is that the paqdisk doesn't seem
to be acceptable to my local (386 binary) paqfs.  when i run
paqfs i get the fingerprint printed out ok but as soon as
i try to access anything other than the root of /n/paq the
process breaks.  i've some changes to paqfs
from nemo@plan9.escet.urjc.es that i'll try tonight.  the
arm binaries are in place and mkfs seems happy (it does
grumble about a few things but nothing that looks like it
should prevent booting).

i'll do some further investigations and see what turns up.

thanks,
stephen
--
Stephen Parker.  Pi Technology.  +44 (0)1223 203438.



             reply	other threads:[~2002-06-25 15:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 15:51 Stephen Parker [this message]
2002-06-25 17:49 ` [9fans] [OT] bitsy cost Vladimir G. Ivanovic
  -- strict thread matches above, loose matches on Subject: below --
2002-06-26  9:09 [9fans] supported ipaq's? Stephen Parker
2002-06-26  9:08 Sape Mullender
2002-06-26  9:03 Sape Mullender
2002-06-26  9:03 Sape Mullender
2002-06-26  7:35 Stephen Parker
2002-06-26  7:29 Fco.J.Ballesteros
2002-06-26  7:28 Stephen Parker
2002-06-25 16:46 Fco.J.Ballesteros
2002-06-25 16:39 Fco.J.Ballesteros
2002-06-25 15:56 rob pike, esq.
2002-06-25 15:56 Stephen Parker
2002-06-25 15:54 Sape Mullender
2002-06-25 15:53 Fco.J.Ballesteros
2002-06-25 16:10 ` Axel Belinfante
2002-06-25 15:44 Stephen Parker
2002-06-25  8:26 Sape Mullender
2002-06-25  8:03 Fco.J.Ballesteros
2002-06-25  7:59 Stephen Parker
2002-06-25  7:45 Fco.J.Ballesteros
2002-06-24 19:00 Sape Mullender
2002-06-24 16:42 presotto
2002-06-24 16:38 Axel Belinfante
2002-06-27 22:55 ` Latchesar Ionkov

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=E562FCEE3A42D61192880002A5FB43330A6350@kite.pigroup.co.uk \
    --to=stephen.parker@pitechnology.com \
    --cc=9fans@cse.psu.edu \
    /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).