From: Grant Grundler <grundler@cup.hp.com>
To: Philipp Rumpf <prumpf@jcsbs.lanobis.de>
Cc: Matthew Wilcox <Matthew.Wilcox@genedata.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Hi
Date: Wed, 12 May 1999 13:00:04 -0700 [thread overview]
Message-ID: <199905122000.NAA15037@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Wed, 12 May 1999 19:42:27 PDT." <19990512194227.52770@insula.local>
Philipp Rumpf wrote:
> > I'd just like to introduce myself. I've liberated a 715/33 Apollo from
> > use as a monitor stand and managed to retrieve all the pieces needed to
> > get it as far as a boot prom prompt. It's got 56MB of RAM and a hard disc
> > of some description. I've got it attached to the ethernet, though I have
> > no idea whether this is working right now. I don't however have anything
> > to boot right now - apparently this disc was used for swap when this
> > workstations was running HP-UX in the dim distant past (you should see
> > the dust).
>
> I think you have the choice to either wait til Linux is bootable or get a
> second hard disk and an HP-UX on it. The disks should be narrow SCSI so the
> second disk shouldn't really be much of a problem.
Mathew can also download and try to install the PA-mklinux.
I have this running on a 712/60 now. I suggest this because
I don't know how accessible HP-UX bits are to the general public.
HP-UX is usually distributed on CD-ROM these days.
Since the source is available for mk-linux, that would suppliment
the PA architecture documentation and might provide the kind of
implementation detail someone experienced in assembler could use.
grant
>
> > I have no previous experience of the HP architecture, but I'm a dab hand
> > at ARM assembler and I'm willing to learn. Anyway, here I am with a
> > machine, ready to help.
>
> OK, first I propose you look at www.thepuffingroup.com/parisc and get just
> about everything linked from the Documentation section. What is most importan
> t
> to get a kernel working fast is acd.pdf (ARM), the runtime architecture docum
> ent
> and perhaps pdc and iodc descriptions.
>
> I think it should be theoretically possible to put the disk in a supported
> machine, cross-build a kernel and bootloader (oh yeah, perhaps you should
> fix the problems with that first ;), put it back into the PARISC aso. but
> just getting a version of HP-UX and a second disk seems easier to me.
>
> Philipp Rumpf
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.
>
Grant Grundler
Enterprise Systems Technology Lab
+1.408.447.7253
next prev parent reply other threads:[~1999-05-12 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-12 18:57 [parisc-linux] Hi Matthew Wilcox
1999-05-12 19:42 ` Philipp Rumpf
1999-05-12 20:00 ` Grant Grundler [this message]
1999-05-12 20:07 ` Matthew Wilcox
1999-05-14 7:25 ` Tom Javen
1999-05-14 18:49 ` Hugo van der Kooij
1999-05-12 20:06 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2003-09-18 15:52 alice
2003-12-03 4:33 [parisc-linux] hi Russel Goff
2004-01-20 18:39 [parisc-linux] Hi alty
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=199905122000.NAA15037@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=Matthew.Wilcox@genedata.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=prumpf@jcsbs.lanobis.de \
/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