The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Pat.Villani@hp.com (Pat Villani)
Subject: 32V update (was Re: [TUHS] While on the subject of 32V ...)
Date: Fri, 31 Oct 2003 09:26:33 -0500	[thread overview]
Message-ID: <3FA27119.9050704@hp.com> (raw)
In-Reply-To: <200310312313.03329.wes.parish@paradise.net.nz>

Silly lawyers :-)  I know I'm good, but building in all the HP-UX 
features in a few months?  Not that good (or modest for that matter).

Hm, 32V-x86 huh?  Maybe, but I'd like to make it fairly portable and 
have a number of targets built from the same source tree.  I don't know 
if that will ever happen, but I don't want to design it out either by 
name or file partitioning.  Maybe we can address the project name at a 
later date.

I'll keep the VAX port alive throughout the project by making sure I can 
cross compile a clean VAX kernel at every milestone.  There may still be 
a VAX in the building somewhere.  Even if one was around, I won't be 
testing the VAX port thanks to HP legal.  We're now cleaning house of 
alpha systems, so a VAX is almost impossible to locate.  Darn mergers 
keeps wiping them out, like that asteroid and dinosaurs years ago ;-)

Progress: I'm working on the make file.  I'm trying to get a clean build 
by substituting stubs for the VAX code I ripped out.  Once done, I can 
concentrate on x86 equivalents.

Device drivers: I have keyboard and character cell VGA code I can use. 
I had been planning on adapting the Hale Landis ATA code from 
http://www.ata-atapi.com/, and the Thix floppy driver from 
http://www.hulubei.net/tudor/thix/ is probably a good piece of code to 
model the 32V driver on.

Pat

Wesley Parish wrote:

> It's downloaded.
> 
> I would suggest renaming it to something like 32V-x86, though - makes it 
> easier to remember it's not going to be precisely the same as 32V for VAX.
> 
> In relation to corporate caveats, the only way you could actually compete with 
> HP is if somehow, in a matter of months, you redid the entire development of 
> BSD and SVRx, up to the stage HP-UX currently is at.
> 
> Oh well, time for me to brush off my Pajari book on Unix device drivers and 
> see if I can make the grade! ;)
> 
> Wesley Parish





  reply	other threads:[~2003-10-31 14:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 13:35 [TUHS] While on the subject of 32V Pat Villani
2003-10-21  0:50 ` Wesley Parish
2003-10-21 14:00   ` Pat Villani
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 [this message]
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
2003-10-31 22:37 Robertdkeys
2003-10-31 23:53 ` Gregg C Levine
2003-11-04 18:18 macbiesz
2003-11-05 10:23 ` Wesley Parish

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=3FA27119.9050704@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).