From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bootalphapc
Date: Thu, 1 Jul 2004 21:29:04 -0700 [thread overview]
Message-ID: <5bb09b1aba0c3cd4348972f59e4a6a08@collyer.net> (raw)
In-Reply-To: <20040701T211505Z_FFB700000000@mail2.cu-portland.edu>
The Plan 9 port for the AlphaPC is only guaranteed to work on AlphaPC
164s. I have a 164LX and Plan 9 worked on that until some months ago,
when interrupts from the PCI bus stopped working. DEC continued its
trajectory from the PDP-11 through the VAX to the Alpha of excluding
more and more of the sorts of things you'd need to get a machine
booted from what it considers to be <sound of trumpets> Architecture
and calls them <sound of razzberry> Implementation-specific. Having
granted themselves licence, they then went hog-wild and build lots of
systems with wildly varying Implementation bits. Andrey made a quick
attempt at getting the AlphaPC port to run on an Alphaserver. It
didn't work, didn't look easy to make work, and he couldn't devote
much time to it.
The Plan 9 alphapc boot code uses the SRM firmware for the actual I/O,
which may be why it's so slow. If you're willing to write the code,
it ought to be possible to boot from other devices. Getting
documentation on the firmware is likely to be the tricky part.
next prev parent reply other threads:[~2004-07-02 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 4:15 Ben Huntsman
2004-07-02 4:29 ` Geoff Collyer [this message]
2004-07-02 4:36 ` George Michaelson
2004-07-02 4:57 Ben Huntsman
2004-07-02 5:08 ` andrey mirtchovski
2004-07-02 15:40 ` jmk
2004-07-06 16:13 ` andrey mirtchovski
2004-07-02 5:19 Ben Huntsman
2004-07-02 14:59 ` andrey mirtchovski
2004-07-06 16:32 Ben Huntsman
2004-07-06 19:54 ` andrey mirtchovski
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=5bb09b1aba0c3cd4348972f59e4a6a08@collyer.net \
--to=geoff@collyer.net \
--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).