From: Alex deVries <adevries@thepuffingroup.com>
To: Simen Thoresen <simen-tt@online.no>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] compiling on a 735?
Date: Mon, 27 Sep 1999 16:22:06 -0400 [thread overview]
Message-ID: <37EFD1EE.6DB82C13@thepuffingroup.com> (raw)
In-Reply-To: 199909271923.VAA29471@online.no
Simen Thoresen wrote:
> 1. has anybody compiled ncurses, so that make menuconfig works? I'll give
> it a try soon.
I don't think so, but we would like that. I just use 'make config' in
the meantime.
> 2. Is my 735 a 712 or 715? Does it matter at this stage?
No, your 735 is a 735, but no, it doesn't matter.
> 3. Is my 735 a A class or D class? Does it matter?
It's really neither, and no, it doesn't matter yet either. We just
don't have enough IO support yet for it to matter.
> 4. The HCL notes that the 735 has a 7100, so that part is ok.
Yuppers.
> 5. Gecko or Dino? I don't have one pci-slots, so I guess it's no Dino, right?
If it has EISA slots, it probably has WAX, for which we have no docs.
It likely has Lasi, but I'm not sure and I'd need an HP person to tell
me.
> make[1]: *** No rule to make target `../../../ramdisk.bin', needed by
> `ramdisk.c
> '. Stop.
> make[1]: Leaving directory `/usr/local/linux/arch/parisc/boot'
> make: *** [ramdisk.o] Error 2
You should grab ramdisk.bin from
ftp://puffin.external.hp.com/pub/parisc/binaries/ramdisks or similiar.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-09-27 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 19:29 [parisc-linux] compiling on a 735? Simen Thoresen
1999-09-27 19:55 ` Grant Grundler
1999-09-27 20:22 ` Alex deVries [this message]
1999-10-08 13:31 ` Steven Pritchard
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=37EFD1EE.6DB82C13@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=simen-tt@online.no \
/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