From: Pat.Villani@hp.com (Pat Villani)
Subject: [TUHS] While on the subject of 32V ...
Date: Tue, 21 Oct 2003 10:00:31 -0400 [thread overview]
Message-ID: <3F953BFF.8020700@hp.com> (raw)
In-Reply-To: <200310211350.55658.wes.parish@paradise.net.nz>
Wesley Parish wrote:
> I tried the same with a few of the utilities and a make with the kernel files.
Having come to HP from DEC by way of Compaq, vax isn't that challenging
for me. :)
I did not try compiling the utilities. My interests have always been at
the kernel level. I am encouraged by the fact that you were able to
build the utilities. This should make life a lot easier.
What I've done so far is split the files into vax specific and "somewhat
vax specific" platform neutral files. This is just a first cut, where I
separated out things such as .s files and .c files that are vax
dependent, such as device drivers, from files that should be platform
neutral.
I did not go through the platform neutral files to correct for vax
dependencies, if any. That's my next task.
I'll tar up what I have so far and put it on a web site for folks to
look at.
Pat
next prev parent reply other threads:[~2003-10-21 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 13:35 Pat Villani
2003-10-21 0:50 ` Wesley Parish
2003-10-21 14:00 ` Pat Villani [this message]
2003-10-22 8:10 ` Wesley Parish
2003-10-24 13:41 ` Pat Villani
2003-10-29 9:01 ` Wesley Parish
2003-10-30 12:56 ` 32V update (was Re: [TUHS] While on the subject of 32V ...) Pat Villani
2003-10-31 10:13 ` Wesley Parish
2003-10-31 14:26 ` Pat Villani
2003-11-05 2:22 ` Greg Lehey
2003-11-05 12:53 ` Pat Villani
[not found] ` <200311022346.34747.wes.parish@paradise.net.nz>
[not found] ` <oprx0h6gtdrveh1e@smtp.borf.com>
2003-11-03 10:48 ` Wesley Parish
2003-11-03 15:34 ` Pat Villani
2003-11-04 9:56 ` Wesley Parish
2003-11-04 13:51 ` Pat Villani
[not found] <20031021020017.5B7961F4F@minnie.tuhs.org>
2003-10-21 3:51 ` [TUHS] While on the subject of 32V Phil Garcia
2003-10-21 19:45 Steve Nickolas
2003-10-30 12:57 David Presotto
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=3F953BFF.8020700@hp.com \
--to=pat.villani@hp.com \
/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).