From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] supported ipaq's?
Date: Tue, 25 Jun 2002 10:03:24 +0200 [thread overview]
Message-ID: <d89367637828f1c38e7753b92f6ddcd7@plan9.escet.urjc.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
Which boot loader are you using?
PS: I think we could continue this w/ private mail, and
update the wiki in case we find some problem and the
way to handle it.
[-- Attachment #2: Type: message/rfc822, Size: 2888 bytes --]
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 08:59:07 +0100
Message-ID: <E562FCEE3A42D61192880002A5FB43330A634B@kite.pigroup.co.uk>
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.
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).
this is all with an early 4th edition setup. have things
changed much since then? any suggestions on how to deal
with either of these problems?
thanks,
stephen
--
Stephen Parker. Pi Technology. +44 (0)1223 203438.
> -----Original Message-----
> From: Fco.J.Ballesteros [mailto:nemo@plan9.escet.urjc.es]
> Sent: 25 June 2002 08:45
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] supported ipaq's?
>
>
> I suposse we'll now as soon as any of the 9bitsies are renewed.
> But in any case, since the boot loader boots linux, I think
> you could try and use linux otherwise. It's just that I'd also like
> to know if Plan 9 runs there too, sorry, :-)
>
next reply other threads:[~2002-06-25 8:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 8:03 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 9:09 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:51 Stephen Parker
2002-06-25 15:44 Stephen Parker
2002-06-25 8:26 Sape Mullender
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=d89367637828f1c38e7753b92f6ddcd7@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).