<> Next Previous Contents

2. General Info about the port

2.1 What is the current status?

Kernel

The kernel boots and works, in a somewhat basic fashion, on a subset of VAX systems.

We currently know that we boot to shell on the following VAXen:

We have, in the past, at least partially booted on the following:

We have drivers for the console, ethernet and SCSI on the;

and works in progress for the SCSI and ethernet on the

So at present, if you want the most complete Linux/VAX experience, get hold of a VAXStation 3100m30/38 or 76.

Compilers, binutils, etc...

The initial ELF toolchain has been completed. This is now based on egcs-1.1.2. We will move to track gcc-3.0 as soon as glibc and the kernel are happy with it (and we get the time).

2.2 What do I need to help?

A VAX, an unix system, (preferably Linux/i386 box), a terminal or terminal emulator like minicom, and a network or shared SCSI disk.

In theory, you should be able to cross compile anywhere you can run GCC, GNU make, GNU binutils and regular Unix shell and text utils. However, most of us cross-compile on Linux/i386. Let us know if you get it working on another combination.

We don't yet support any graphics hardware on these VAXen, so you'll need some sort of serial terminal (or terminal emulator) to boot the VAX. Most newer (post-1986-ish) VAXen have DEC MMJ (modified modular jack) connectors. Older one will have either standard 25-pin RS232 connectors or DEC's 9-pin RS232 (different from IBM's 9-pin RS232 as used on the PC). See the OpenVMS FAQ for details of pinouts.

In order to get the kernel image over to the VAX in order to boot it, you've got two options: MOP or SCSI.

2.3 Explain your CVS setup.

We use sourceforge to supply our CVS services. We are maintaining several packages (modules) in CVS. The CVS is always the definitive source for the latest version of the code. We've pretty much given up making snapshots of the toolchain and kernel code, as most people seem happy with CVS access.

The main modules are;

Access to CVS is via the standard sourceforge method. See our project cvs page for details on that.

Can I get write access?

Sure. Join the mailing list, tell us what you want to work on, and show us some sample patches. If they look ok, you get write access. You'll need to tell us your sourceforge account name. If you don't have one, you'll need to sign up for one.

I dont want to got through all of that, what now?

Send the patch, and one of us will apply it.

2.4 I have a mumbleVAX, is it supported?

See section Kernel for details about which VAXes are currently supported. If you want to help out by adding support for your VAX, feel free. You will need to check the kernel source code out of the CVS repository at sourceforge, and have a look at the cpu_xxx.c files in the arch/vax/kernel directory to get an idea of what you need to implement for a machine vector.

2.5 How do I get started?

Read the "How to get started Hacking" document in the Documentationsection. This describes howto download the compiler and kernel, and set up the MOP boot. Unfortunately its a little out of date. Sorry.


Next Previous Contents >