linux-vax-commit — [LIST CLOSED] Notifications of commits to complete Linux/VAX CVS tree

[LV-commit] CVS: kernel-2.4/drivers/vsbus vsbus.c,1.5,1.6

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/drivers/vsbus
In directory usw-pr-cvs1:/tmp/cvs-serv558

Modified Files:
	vsbus.c 
Log Message:
DA: vsbus changes for 4000/60... need testing on 3100/m38


Index: vsbus.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/drivers/vsbus/vsbus.c,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- vsbus.c	2001/09/16 15:13:09	1.5
+++ vsbus.c	2001/11/11 22:43:25	1.6
@@ -27,26 +27,27 @@
   unsigned long irqs;
   
   sys_vs.vs_cpu_ptr=(void *)ioremap(VSA_BASE_REGS, 128);
-  
+  sys_vs.vs_mask=sys_vs.vs_cpu_ptr->vc_intreq;
+  printk("vsbus: interrupt mask %x\n", sys_vs.vs_mask);
   irqs=probe_irq_on();
  
   sys_vs.vs_cpu_ptr->vc_intmsk=0;
   sys_vs.vs_cpu_ptr->vc_intclr=0xFF;
   //  printk("vsbus: Getting Interrupt Mask\n");
-  udelay(100000);
+  mdelay(1);
   sys_vs.vs_mask=sys_vs.vs_cpu_ptr->vc_intreq;
-  sys_vs.vs_cpu_ptr->vc_intmsk=0; /*~sys_vs.vs_mask;*/
 
+  /* switch off all interrupts for now */
+  sys_vs.vs_cpu_ptr->vc_intmsk=0; /*~sys_vs.vs_mask;*/
   probe_irq_off(irqs);
   printk("vsbus: interrupt mask %x\n", sys_vs.vs_mask);
-
   return 0;
 }
 
 int vsbus_enable_int(int bit_nr)
 {
   sys_vs.vs_cpu_ptr->vc_intmsk|=1<<bit_nr;
-
+  sys_vs.vs_enabled |= 1<< bit_nr;
   return 0;
 }
 
@@ -60,24 +61,26 @@
 int vsbus_disable_int(int bit_nr)
 {
   sys_vs.vs_cpu_ptr->vc_intmsk&=~(1<<bit_nr);
+  sys_vs.vs_enabled &= ~(1<<bit_nr);
   return 0;
 }
 
 int vsbus_probe_irq_on(void)
 {
   printk("vsbus: probing set mask ~%2X\n", sys_vs.vs_mask);
-  sys_vs.vs_cpu_ptr->vc_intmsk = sys_vs.vs_mask;
+  sys_vs.vs_cpu_ptr->vc_intmsk = 0; //~sys_vs.vs_mask;
   sys_vs.vs_cpu_ptr->vc_intclr=0xff;
   return 0;
 }
 
 unsigned char vsbus_probe_irq_report(void)
 {
- unsigned char x, y;
-
+  unsigned char x, y;
+  
   x=sys_vs.vs_cpu_ptr->vc_intreq;
   y = x & ~sys_vs.vs_mask;
   printk("vsbus: probe returning %2X, %2X\n", x, ffs(y));
+  sys_vs.vs_cpu_ptr->vc_intmsk  = sys_vs.vs_enabled;
   return ffs(y)-1;
 }
 

[LV-commit] CVS: kernel-2.4/drivers/char dz.c,1.10,1.11

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/drivers/char
In directory usw-pr-cvs1:/tmp/cvs-serv32542

Modified Files:
	dz.c 
Log Message:
DA: dz.c fixes for 4000/60 .. need to test on 3100m38


Index: dz.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/drivers/char/dz.c,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- dz.c	2001/09/21 20:54:16	1.10
+++ dz.c	2001/11/11 22:42:39	1.11
@@ -1444,10 +1444,11 @@
 #ifndef CONFIG_SERIAL_CONSOLE
   dz_out(info, DZ_CSR, DZ_CLR);
   while ((tmp = dz_in(info,DZ_CSR)) & DZ_CLR) ;
+#ifndef CONFIG_VAX
   wbflush();
+#endif
   
-  /* enable scanning */
-   dz_out(info, DZ_CSR, DZ_MSE); 
+
 #endif
   
   /* order matters here... the trick is that flags
@@ -1464,9 +1465,9 @@
     i = dz_in(info, DZ_TCR);
     dz_out(info, DZ_CSR, DZ_MSE|DZ_TIE);
     dz_out(info, DZ_TCR, 0);
-    udelay(1000);
+    mdelay(1);
     dz_out(info, DZ_TCR, 1);
-    udelay(10000);
+    mdelay(10);
     dz_out(info, DZ_TCR, i);
     num=vsbus_probe_irq_report();
     irq=autoirq_report(0);
@@ -1482,13 +1483,13 @@
     i = dz_in(info, DZ_TCR);
     dz_out(info, DZ_CSR, DZ_MSE|DZ_TIE);
     dz_out(info, DZ_TCR, 0);
-    udelay(1000);
+    mdelay(1);
     dz_out(info, DZ_TCR, 1);
-    udelay(10000);
+    mdelay(10);
     dz_out(info, DZ_TCR, i);
     vsbus_clear_int(num);
     vsbus_disable_int(num);
-    irq=autoirq_report(100);     
+    irq=autoirq_report(0);
   }
 #else    
 if (is_ka46()){
@@ -1512,7 +1513,8 @@
   if (request_irq (SERIAL, dz_interrupt_rx, SA_INTERRUPT, "DZ", lines[0]))
     panic ("Unable to register DZ interrupt\n");
 #endif
-
+  /* enable scanning */
+  dz_out(info, DZ_CSR, DZ_MSE); 
   return 0;
 }
 
@@ -1544,6 +1546,9 @@
   /* Actually transmit the character. */
   dz_out (dz_console, DZ_TDR, tmp);
 
+  /* spin our wheels */
+  while (((dz_in(dz_console,DZ_CSR) & DZ_TRDY) != DZ_TRDY) &&  loops--)
+    ;
   dz_out(dz_console, DZ_TCR, tcr);
   restore_flags(flags); 
 }
@@ -1650,13 +1655,12 @@
 	dz_console->line = CONSOLE_LINE;
 
 	/* This line locks up Dave Airlie's VS3100m38 after HALT */
-	/* dz_out(dz_console, DZ_CSR, DZ_CLR); */
+#ifndef CONFIG_VAX
+	dz_out(dz_console, DZ_CSR, DZ_CLR);
+#endif
 
 	while ((tmp = dz_in(dz_console,DZ_CSR)) & DZ_CLR)
 	  ;
-
-	/* enable scanning */
-	dz_out(dz_console, DZ_CSR, DZ_MSE); 
 
         /*  Set up flags... */
 	dz_console->cflags = co->cflag;

[LV-commit] CVS: kernel-2.4/drivers/net vaxlance.c,1.17,1.18

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/drivers/net
In directory usw-pr-cvs1:/tmp/cvs-serv8531

Modified Files:
	vaxlance.c 
Log Message:
DA: move to mdelay rather than udelay


Index: vaxlance.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/drivers/net/vaxlance.c,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- vaxlance.c	2001/09/16 15:13:09	1.17
+++ vaxlance.c	2001/11/11 21:33:14	1.18
@@ -1024,7 +1024,7 @@
 	  writereg(&ll->rap, LE_CSR0);
 	  writereg(&ll->rdp, LE_C0_INEA|LE_C0_INIT);
 	  writecsr0(ll, LE_C0_INEA|LE_C0_INIT);
-	  udelay(1000);
+	  mdelay(1);
 	  num=vsbus_probe_irq_report();
 	  irq=autoirq_report(0);
 	  if (num)

[LV-commit] CVS: kernel-2.4/arch/vax/kernel interrupt.c,1.21,1.22 interrupt.h,1.7,1.8 ptrace.c,1.3,1.4

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel
In directory usw-pr-cvs1:/tmp/cvs-serv15389

Modified Files:
	interrupt.c interrupt.h ptrace.c 
Log Message:
DA: ptrace singlestep and trace exception support


Index: interrupt.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/interrupt.c,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- interrupt.c	2001/10/28 23:54:18	1.21
+++ interrupt.c	2001/11/09 23:48:40	1.22
@@ -196,6 +196,11 @@
 		printk("Panic: unable to register breakpoint handler\n");
 		machine_halt();
 	}
+
+	if (register_excep_handler(SCB_TPEND,"Trace Pending (tpend_handler)", tpend_handler, 0, 0)) {
+		printk("Panic: unable to register trace pending handler\n");
+		machine_halt();
+	}
    
    
 }
@@ -256,21 +261,56 @@
 /* This is the handler for break points */
 void bpt_handler(struct pt_regs *regs, void *unused)
 {
+  siginfo_t info;
+#if 0
   printk("\nbp sending SIGTRAP\n");
+
+  printk("\nBreakpoint at PC=%08lx at %08lX\n", regs->pc, &regs->pc);
+
+  printk("\nStack dump\n"); 
+  hex_dump((void *)(regs->sp), 256);
+  show_regs(regs); 
+  show_cpu_regs(); 
+#endif  
+  if (user_mode(regs)) {
+    info.si_signo = SIGTRAP;
+    info.si_errno = 0;
+    info.si_code = TRAP_BRKPT;
+    info.si_addr = regs->pc;
+    force_sig_info(SIGTRAP,&info,current);
+    return;	  
+  }
+  machine_halt();
+
+  force_sig(SIGTRAP, current);
+}
+
+/* This is the handler for break points */
+void tpend_handler(struct pt_regs *regs, void *unused)
+{
+  siginfo_t info;
+
+  regs->psl.t=0;
+
 #if 0
-  printk("\nBreakpoint at PC=%08lx\n", regs->pc);
+  printk("\ntpend sending SIGTRAP\n");
+  printk("\nTrace Pending at PC=%08lx at %08lX\n", regs->pc, &regs->pc);
 
   printk("\nStack dump\n"); 
   hex_dump((void *)(regs->sp), 256);
   show_regs(regs); 
   show_cpu_regs(); 
+#endif
   
   if (user_mode(regs)) {
-    force_sig(SIGTRAP,current);
+    info.si_signo = SIGTRAP;
+    info.si_errno = 0;
+    info.si_code = TRAP_BRKPT;
+    info.si_addr = regs->pc;
+    force_sig_info(SIGTRAP,&info,current);
     return;	  
   }
   machine_halt();
-#endif
   force_sig(SIGTRAP, current);
 }
 
@@ -386,9 +426,10 @@
 
         status = 1;     /* Force the "do bottom halves" bit */
 
+		
 	action = &vec->action;
 	vec_num = vec->vec_num;
-
+	
         status |= action->flags;
         action->handler(vec_num, action->dev_id, regs);
 
@@ -403,7 +444,7 @@
 
 static inline void do_irq(struct pt_regs *regs, struct irqvector *vec)
 {
-	int flags;
+        int flags;
 	int status;
 	int cpu;
 	/* Fake a single-priority-level interrupt system by raising IPL

Index: interrupt.h
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/interrupt.h,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- interrupt.h	2001/10/28 23:54:18	1.7
+++ interrupt.h	2001/11/09 23:48:40	1.8
@@ -68,3 +68,4 @@
 extern void resam_handler(struct pt_regs *regs, void *unused);
 extern void arith_handler(struct pt_regs *regs, void *excep_info);
 extern void bpt_handler(struct pt_regs *regs, void *excep_info);
+extern void tpend_handler(struct pt_regs *regs, void *excep_info);

Index: ptrace.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/ptrace.c,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ptrace.c	2001/11/08 22:17:16	1.3
+++ ptrace.c	2001/11/09 23:48:40	1.4
@@ -40,7 +40,6 @@
   
   regs_ptr = stack_top - 16 - sizeof(struct pt_regs);
 
-  printk("putreg called with regno %d\n", regno>>2);
   switch(regno >> 2) {
   case 0 ... 16:
     //    retval = *(((unsigned long *)regs_ptr) + (regno>>2));
@@ -82,7 +81,6 @@
 	  retval=0;
 	  break;
 	}
-	printk("getreg returning %8lX\n", retval);
 	return retval;
 }
 
@@ -93,7 +91,7 @@
 	extern void save_fp(void*);
 
 	lock_kernel();
-#if 1
+#if 0
 	printk("ptrace(r=%d,pid=%d,addr=%08lx,data=%08lx)\n",
 	       (int) request, (int) pid, (unsigned long) addr,
 	       (unsigned long) data);
@@ -182,7 +180,6 @@
 	  unsigned long tmp;
 
 	        res = -EIO;
-		printk("Addr is %8lX, sizeof is %8lX\n", addr, sizeof(struct user));
 		if ((addr & 3) || addr < 0 || addr > sizeof(struct user)-3)
 		  break;
 		
@@ -204,7 +201,7 @@
 		goto out;
 
 	case PTRACE_POKEUSR: {
-		struct pt_regs *regs;
+	  //		struct pt_regs *regs;
 		int res = 0;
 		res = -EIO;
 		if ((addr & 3) || addr < 0 || 
@@ -250,6 +247,29 @@
 		wake_up_process(child);
 		break;
 
+	case PTRACE_SINGLESTEP:
+	  {
+	    unsigned long tmp;
+	    struct psl_fields *psl;
+                res = -EIO;
+                if ((unsigned long) data > _NSIG)
+		        break;
+		child->ptrace &= ~ PT_TRACESYS;
+		if ((child->ptrace & PT_DTRACE)==0)
+		  child->ptrace |= PT_DTRACE;
+		
+		tmp = getreg(child, PT_PSL<<2);
+		psl = &tmp;
+		psl->t=1;
+		putreg(child, PT_PSL<<2, *(unsigned long *)psl);
+		//		printk("tmp is %8lX, psl is now %8lX\n", tmp, *(unsigned long *)psl);
+
+		
+		child->exit_code=data;
+		wake_up_process(child);
+		res = 0;
+		break;
+	  }
 	case PTRACE_DETACH: /* detach a process that was attached. */
 		res = -EIO;
 		if ((unsigned long) data > _NSIG)

[LV-commit] CVS: kernel-2.4/arch/vax/kernel ptrace.c,1.2,1.3

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel
In directory usw-pr-cvs1:/tmp/cvs-serv8907

Modified Files:
	ptrace.c 
Log Message:
DA: ptrace getreg/putreg should be more functional if not correct


Index: ptrace.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/ptrace.c,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ptrace.c	2001/11/04 21:58:32	1.2
+++ ptrace.c	2001/11/08 22:17:16	1.3
@@ -31,16 +31,21 @@
 static int putreg(struct task_struct *child,
 	unsigned long regno, unsigned long value)
 {
-  printk("putreg called with regno %d\n", regno);
+  unsigned long retval = ~0UL;
+  void *stack_top;
+  struct pt_regs *regs_ptr;
+  
+  stack_top = ((union task_union *)child)+1; 
+  stack_top -= 4;
+  
+  regs_ptr = stack_top - 16 - sizeof(struct pt_regs);
+
+  printk("putreg called with regno %d\n", regno>>2);
   switch(regno >> 2) {
-  case 0 ... 13:
-    *(unsigned long *)((&child->thread.pcb)+4+(regno>>2))=value;
-    break;
-  case PT_SP:
-    child->thread.pcb.usp=value;
-    break;
-  case PT_PC:
-    child->thread.pcb.pc=value;
+  case 0 ... 16:
+    //    retval = *(((unsigned long *)regs_ptr) + (regno>>2));
+    *(((unsigned long *)regs_ptr) + (regno>>2)) = value;
+    //    *(unsigned long *)((&child->thread.pcb)+4+(regno>>2))=value;
     break;
   default:
     printk("putreg for %d failed\n", regno);
@@ -55,27 +60,23 @@
 	unsigned long regno)
 {
 	unsigned long retval = ~0UL;
+	void *stack_top;
+	struct pt_regs *regs_ptr;
+	
+	stack_top = ((union task_union *)child)+1; 
+	stack_top -= 4;
 
-	/* this code takes the register from the PCB for the process. PC is reg 15 but 14'th after R0 in
-           the pcb so it is special cased. have to add some stack pointers at some stage */
+	/* get the registers from where we shoved them on the stack at the last 
+	   exception for this process.. not sure if this is always correct but 
+           will do for now - 4 longwords back from end of stack is end of regs */
+	
+	regs_ptr = stack_top - 16 - sizeof(struct pt_regs);
+
+
 	switch(regno >> 2) {
-	case 0 ... 13:
-	  retval = (unsigned long)*(unsigned long *)((&child->thread.pcb)+4+(regno>>2));
-	  break;
-	case PT_SP:
-	  retval = child->thread.pcb.usp;
-	  break;
-	case PT_PC:
-	  {
-	    int i;
-	    struct pt_regs regs;
-	    
-	    //	    hex_dump((void *)(child->thread.pcb.ksp-0x80), 256);
-	    //	    printk("ksp:%8lX ap:%8lX fp:%8lX\n", child->thread.pcb.ksp, child->thread.pcb.ap, child->thread.pcb.ksp+0x64);
-	    /* FIXME: explain 0x64 == 100 = 25 * 4 pc is stored 25 longs into stack.... */
-	    retval = (unsigned long)*(unsigned long *)(child->thread.pcb.ksp + 0x64);
+	case 0 ... 16:
+	  retval = *(((unsigned long *)regs_ptr) + (regno>>2));
 	  break;
-	  }
 	default:
 	  printk("getreg for %d failed\n", regno);
 	  retval=0;

[LV-commit] CVS: kernel-2.4/arch/vax/kernel ptrace.c,1.1,1.2

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel
In directory usw-pr-cvs1:/tmp/cvs-serv29714

Modified Files:
	ptrace.c 
Log Message:
DA: better ptrace for finding PC .. needs more explains


Index: ptrace.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/ptrace.c,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ptrace.c	2001/10/28 23:54:18	1.1
+++ ptrace.c	2001/11/04 21:58:32	1.2
@@ -8,6 +8,7 @@
  * Copyright (C) Linus Torvalds
  * Copyright (C) 1994, 1995, 1996, 1997, 1998 Ralf Baechle
  * Copyright (C) 1996 David S. Miller
+ * Copyright (C) 2001 David Airlie, VAX Porting Project
  */
 #include <linux/kernel.h>
 #include <linux/sched.h>
@@ -63,9 +64,18 @@
 	  break;
 	case PT_SP:
 	  retval = child->thread.pcb.usp;
+	  break;
 	case PT_PC:
-	  retval = child->thread.pcb.pc;
+	  {
+	    int i;
+	    struct pt_regs regs;
+	    
+	    //	    hex_dump((void *)(child->thread.pcb.ksp-0x80), 256);
+	    //	    printk("ksp:%8lX ap:%8lX fp:%8lX\n", child->thread.pcb.ksp, child->thread.pcb.ap, child->thread.pcb.ksp+0x64);
+	    /* FIXME: explain 0x64 == 100 = 25 * 4 pc is stored 25 longs into stack.... */
+	    retval = (unsigned long)*(unsigned long *)(child->thread.pcb.ksp + 0x64);
 	  break;
+	  }
 	default:
 	  printk("getreg for %d failed\n", regno);
 	  retval=0;

[LV-commit] CVS: kernel-2.4/include/asm-vax ptrace.h,1.3,1.4

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/include/asm-vax
In directory usw-pr-cvs1:/tmp/cvs-serv8501

Modified Files:
	ptrace.h 
Log Message:
DA: reg defs .. 


Index: ptrace.h
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/include/asm-vax/ptrace.h,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ptrace.h	2001/07/31 17:33:26	1.3
+++ ptrace.h	2001/10/28 23:55:36	1.4
@@ -3,6 +3,25 @@
 #define _VAX_PTRACE_H
 
 #include <asm/psl.h>
+
+#define PT_R0 0
+#define PT_R1 1
+#define PT_R2 2
+#define PT_R3 3
+#define PT_R4 4
+#define PT_R5 5
+#define PT_R6 6
+#define PT_R7 7
+#define PT_R8 8
+#define PT_R9 9
+#define PT_R10 10
+#define PT_R11 11
+#define PT_AP 12
+#define PT_FP 13
+#define PT_SP 14
+#define PT_PC 15
+#define PT_PSL 16
+#define PT_USP 20
  
 /* this struct defines the way the registers are stored on the 
    stack during a system call. */

[LV-commit] CVS: kernel-2.4/arch/vax/kernel ptrace.c,NONE,1.1 process.c,1.14,1.15 interrupt.c,1.20,1.21 interrupt.h,1.6,1.7 Makefile,1.7,1.8

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel
In directory usw-pr-cvs1:/tmp/cvs-serv8312

Modified Files:
	process.c interrupt.c interrupt.h Makefile 
Added Files:
	ptrace.c 
Log Message:
DA: add initial ptrace support


--- NEW FILE ---
/* $Id: ptrace.c,v 1.1 2001/10/28 23:54:18 airlied Exp $
 *
 * This file is subject to the terms and conditions of the GNU General Public
 * License.  See the file "COPYING" in the main directory of this archive
 * for more details.
 *
 * Copyright (C) 1992 Ross Biro
 * Copyright (C) Linus Torvalds
 * Copyright (C) 1994, 1995, 1996, 1997, 1998 Ralf Baechle
 * Copyright (C) 1996 David S. Miller
 */
#include <linux/kernel.h>
#include <linux/sched.h>
#include <linux/mm.h>
#include <linux/errno.h>
#include <linux/ptrace.h>
#include <linux/smp.h>
#include <linux/smp_lock.h>
#include <linux/user.h>

#if 0
#include <asm/fp.h>
#include <asm/mipsregs.h>
#endif
#include <asm/pgtable.h>
#include <asm/page.h>
#include <asm/system.h>
#include <asm/uaccess.h>

static int putreg(struct task_struct *child,
	unsigned long regno, unsigned long value)
{
  printk("putreg called with regno %d\n", regno);
  switch(regno >> 2) {
  case 0 ... 13:
    *(unsigned long *)((&child->thread.pcb)+4+(regno>>2))=value;
    break;
  case PT_SP:
    child->thread.pcb.usp=value;
    break;
  case PT_PC:
    child->thread.pcb.pc=value;
    break;
  default:
    printk("putreg for %d failed\n", regno);
    break;
  }
  
  return 0;

}

static unsigned long getreg(struct task_struct *child,
	unsigned long regno)
{
	unsigned long retval = ~0UL;

	/* this code takes the register from the PCB for the process. PC is reg 15 but 14'th after R0 in
           the pcb so it is special cased. have to add some stack pointers at some stage */
	switch(regno >> 2) {
	case 0 ... 13:
	  retval = (unsigned long)*(unsigned long *)((&child->thread.pcb)+4+(regno>>2));
	  break;
	case PT_SP:
	  retval = child->thread.pcb.usp;
	case PT_PC:
	  retval = child->thread.pcb.pc;
	  break;
	default:
	  printk("getreg for %d failed\n", regno);
	  retval=0;
	  break;
	}
	printk("getreg returning %8lX\n", retval);
	return retval;
}

asmlinkage int sys_ptrace(long request, long pid, long addr, long data)
{
	struct task_struct *child;
	int res;
	extern void save_fp(void*);

	lock_kernel();
#if 1
	printk("ptrace(r=%d,pid=%d,addr=%08lx,data=%08lx)\n",
	       (int) request, (int) pid, (unsigned long) addr,
	       (unsigned long) data);
#endif
	if (request == PTRACE_TRACEME) {
		/* are we already being traced? */
		if (current->ptrace & PT_PTRACED) {
			res = -EPERM;
			goto out;
		}
		/* set the ptrace bit in the process flags. */
		current->ptrace |= PT_PTRACED;
		res = 0;
		goto out;
	}
	res = -ESRCH;
	read_lock(&tasklist_lock);
	child = find_task_by_pid(pid);
	if (child)
		get_task_struct(child);
	read_unlock(&tasklist_lock);
	if (!child)
		goto out;

	res = -EPERM;
	if (pid == 1)		/* you may not mess with init */
		goto out;

	if (request == PTRACE_ATTACH) {
		if (child == current)
			goto out_tsk;
		if ((!child->dumpable ||
		    (current->uid != child->euid) ||
		    (current->uid != child->suid) ||
		    (current->uid != child->uid) ||
	 	    (current->gid != child->egid) ||
		    (current->gid != child->sgid) ||
	 	    (current->gid != child->gid) ||
		    (!cap_issubset(child->cap_permitted,
		                  current->cap_permitted)) ||
                    (current->gid != child->gid)) && !capable(CAP_SYS_PTRACE))
			goto out_tsk;
		/* the same process cannot be attached many times */
		if (child->ptrace & PT_PTRACED)
			goto out_tsk;
		child->ptrace |= PT_PTRACED;

		write_lock_irq(&tasklist_lock);
		if (child->p_pptr != current) {
			REMOVE_LINKS(child);
			child->p_pptr = current;
			SET_LINKS(child);
		}
		write_unlock_irq(&tasklist_lock);

		send_sig(SIGSTOP, child, 1);
		res = 0;
		goto out_tsk;
	}
	res = -ESRCH;
	if (!(child->ptrace & PT_PTRACED))
		goto out_tsk;
	if (child->state != TASK_STOPPED) {
		if (request != PTRACE_KILL)
			goto out_tsk;
	}
	if (child->p_pptr != current)
		goto out_tsk;
	switch (request) {
	case PTRACE_PEEKTEXT: /* read word at location addr. */ 
	case PTRACE_PEEKDATA: {
		unsigned long tmp;
		int copied;

		copied = access_process_vm(child, addr, &tmp, sizeof(tmp), 0);
		res = -EIO;
		if (copied != sizeof(tmp))
			break;
		res = put_user(tmp,(unsigned long *) data);

		goto out;
		}

	/* Read the word at location addr in the USER area.  */
	case PTRACE_PEEKUSR: {
	  unsigned long tmp;

	        res = -EIO;
		printk("Addr is %8lX, sizeof is %8lX\n", addr, sizeof(struct user));
		if ((addr & 3) || addr < 0 || addr > sizeof(struct user)-3)
		  break;
		
		tmp=0;
		if (addr < 16*sizeof(unsigned long))
		  tmp = getreg(child, addr);
		
		res = put_user(tmp, (unsigned long *) data);
		goto out;
		}

	case PTRACE_POKETEXT: /* write the word at location addr. */
	case PTRACE_POKEDATA:
		res = 0;
		if (access_process_vm(child, addr, &data, sizeof(data), 1)
		    == sizeof(data))
			break;
		res = -EIO;
		goto out;

	case PTRACE_POKEUSR: {
		struct pt_regs *regs;
		int res = 0;
		res = -EIO;
		if ((addr & 3) || addr < 0 || 
		    addr > sizeof(struct user) - 3)
			break;

		if (addr < 17*sizeof(long)) {
			res = putreg(child, addr, data);
			break;
		}
		/* We need to be very careful here.  We implicitly
		   want to modify a portion of the task_struct, and we
		   have to be selective about what portions we allow someone
		   to modify. */
		break;
		}

	case PTRACE_SYSCALL: /* continue and stop at next (return from) syscall */
	case PTRACE_CONT: { /* restart after signal. */
		res = -EIO;
		if ((unsigned long) data > _NSIG)
			break;
		if (request == PTRACE_SYSCALL)
			child->ptrace |= PT_TRACESYS;
		else
			child->ptrace &= ~PT_TRACESYS;
		child->exit_code = data;
		wake_up_process(child);
		res = 0;
		break;
		}

	/*
	 * make the child exit.  Best I can do is send it a sigkill. 
	 * perhaps it should be put in the status that it wants to 
	 * exit.
	 */
	case PTRACE_KILL:
		res = 0;
		if (child->state != TASK_ZOMBIE)	/* already dead */
			break;
		child->exit_code = SIGKILL;
		wake_up_process(child);
		break;

	case PTRACE_DETACH: /* detach a process that was attached. */
		res = -EIO;
		if ((unsigned long) data > _NSIG)
			break;
		child->ptrace &= ~(PT_PTRACED|PT_TRACESYS);
		child->exit_code = data;
		write_lock_irq(&tasklist_lock);
		REMOVE_LINKS(child);
		child->p_pptr = child->p_opptr;
		SET_LINKS(child);
		write_unlock_irq(&tasklist_lock);
		wake_up_process(child);
		res = 0;
		break;

	default:
		res = -EIO;
		goto out;
	}
out_tsk:
	free_task_struct(child);
out:
	unlock_kernel();
	return res;
}

asmlinkage void syscall_trace(void)
{
	if ((current->ptrace & (PT_PTRACED|PT_TRACESYS))
			!= (PT_PTRACED|PT_TRACESYS))
		return;
	current->exit_code = SIGTRAP;
	current->state = TASK_STOPPED;
	notify_parent(current, SIGCHLD);
	schedule();
	/*
	 * this isn't the same as continuing with a signal, but it will do
	 * for normal use.  strace only continues with a signal if the
	 * stopping signal is not SIGTRAP.  -brl
	 */
	if (current->exit_code) {
		send_sig(current->exit_code, current, 1);
		current->exit_code = 0;
	}
}

Index: process.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/process.c,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- process.c	2001/09/22 19:44:18	1.14
+++ process.c	2001/10/28 23:54:18	1.15
@@ -122,7 +122,6 @@
    
 //   printk("copy_thread: pid %d, task 0x%08lx, kstack_top 0x%8lx, usp 0x%08lx, ksp 0x%08lx\n", 
 //   	p->pid, (unsigned long)p, stack_top, usp, child_stack); 
-
    child_regs = &child_stack->regs;
 
    *child_regs = *regs;
@@ -217,11 +216,6 @@
 int sys_vfork(struct pt_regs *regs)
 {
 	return do_fork(CLONE_VFORK | CLONE_VM | SIGCHLD, regs->sp, regs, 0);
-}
-
-int sys_ptrace(long request, long pid, long addr, long data)
-{
-	return -ENOSYS;
 }
 
 /*

Index: interrupt.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/interrupt.c,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- interrupt.c	2001/09/16 15:23:20	1.20
+++ interrupt.c	2001/10/28 23:54:18	1.21
@@ -192,6 +192,10 @@
 		printk("Panic: unable to register arithmetic fault handler\n");
 		machine_halt();
 	}
+	if (register_excep_handler(SCB_BPT,"Breakpoint fault (bpt_handler)", bpt_handler, 0, 0)) {
+		printk("Panic: unable to register breakpoint handler\n");
+		machine_halt();
+	}
    
    
 }
@@ -249,6 +253,26 @@
 	machine_halt();
 }
 
+/* This is the handler for break points */
+void bpt_handler(struct pt_regs *regs, void *unused)
+{
+  printk("\nbp sending SIGTRAP\n");
+#if 0
+  printk("\nBreakpoint at PC=%08lx\n", regs->pc);
+
+  printk("\nStack dump\n"); 
+  hex_dump((void *)(regs->sp), 256);
+  show_regs(regs); 
+  show_cpu_regs(); 
+  
+  if (user_mode(regs)) {
+    force_sig(SIGTRAP,current);
+    return;	  
+  }
+  machine_halt();
+#endif
+  force_sig(SIGTRAP, current);
+}
 
 /* This is the handler for reserved addressing mode exceptions.
    Eventually this will have to check if the fault was from user
@@ -300,8 +324,7 @@
 };
 
 void arith_handler(struct pt_regs *regs, void *excep_info)
-{
-        int code = *(unsigned int *)(excep_info);
+{        int code = *(unsigned int *)(excep_info);
 	printk("Arithmetic Fault at PC=%8lx, %s, (code=%x)\n",regs->pc,arith_faults[code],code);
    /* FIXME: need to code up the info for user handler */
         if (user_mode(regs)) {

Index: interrupt.h
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/interrupt.h,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- interrupt.h	2001/09/06 23:39:42	1.6
+++ interrupt.h	2001/10/28 23:54:18	1.7
@@ -67,3 +67,4 @@
 extern void syscall_handler(struct pt_regs *regs, void *excep_info);
 extern void resam_handler(struct pt_regs *regs, void *unused);
 extern void arith_handler(struct pt_regs *regs, void *excep_info);
+extern void bpt_handler(struct pt_regs *regs, void *excep_info);

Index: Makefile
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/Makefile,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Makefile	2001/03/04 23:44:42	1.7
+++ Makefile	2001/10/28 23:54:18	1.8
@@ -13,7 +13,7 @@
 
 O_TARGET := kernel.o
 
-obj-y   := process.o setup.o regdump.o interrupt.o entry.o time.o \
+obj-y   := ptrace.o process.o setup.o regdump.o interrupt.o entry.o time.o \
 		syscall.o signal.o semaphore.o vax_dev_init.o\
 		init_task.o reboot.o cpu_generic.o \
 		cpu_ka630.o cpu_ka640.o cpu_ka650.o cpu_ka660.o \

[LV-commit] CVS: www/htdocs todo.html,NONE,1.1 todoframe.html,NONE,1.1 header.html,1.1,1.2

[Richard B. <rb...@us...>]

Update of /cvsroot/linux-vax/www/htdocs
In directory usw-pr-cvs1:/tmp/cvs-serv310/htdocs

Modified Files:
	header.html 
Added Files:
	todo.html todoframe.html 
Log Message:
Added To Do list


--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="GENERATOR" CONTENT="Mozilla/4.10 [en] (X11; I; Linux 2.0.36 i586) [Netscape]">
   <META NAME="Author" CONTENT="rbbanks">
   <TITLE>Linux/VAX Porting Project</TITLE>
</HEAD>
<frameset rows="130,*" border=0>
<frame src="header.html" name=header>
<frame src="todoframe.html" name=body >
</frameset>
</HTML>

--- NEW FILE ---
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="GENERATOR" content="Mozilla/4.75 [en] (X11; U; Linux 2.4.4 i586) [Netscape]">
</head>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">
<FONT FACE="Helvetica, Arial"><FONT SIZE=+1>

<h1>
Kernel</h1>

<p><br>When we get an arithmetic fault of types 8,9,10. The PC is backed
up to point at the instruction causing the fault. If we just send a SIGFPE
and return, and there is no SIGFPE hander, the program goes into an infinite
loop with the arith_fault handler, and the faulting instr. Should we a)
try and advance PC, or b) send it a signal that kills it?
<p>Swapon to a file would be useful.
<p>Implement RT signals, Siginfo (arch/vax/kernel/signal.c)
<p>Occasionally processes will go into an infinite loop (configure --target=vax-dec-linux
for zlib is one) that refuses to respond to signals - ctrl z, c, \. We
need to do_signal somewhere where we are not, or there is something missing
from the console driver.
<p>Machine check implementations (arch/vax/kernel/cpu_xxx.x)
<p>Condense the three pages/task we use for pgd and pmd into one page.
(arch/vax/mm/pgalloc.c) Guard page to catch overruns and underruns at the
boundary between P0 and P1 ptes.
<p>Guard page in processes task_struct to catch kernel stack overflow.
<p>Implement interrupt stats in /proc/interrupts (arch/vax/kernel/interrupt.c)
<p>Clean up the definitions of mk_pte in pagelet_pte.h, make sure the early
code and iomap are using it correctly. (Andy Phillips)
<p>Track latest linus tree.
<p>Write a flush_tlb_8 that flushes a set of pagelet hwptes and use where
needed in place of current flush_tlb_all()'s.
<p>Write a translation-not-valid fault hander that doesnt lock up the machine
or lock up a process in a deadlock at the capture of the mm semaphore if
we are in the middle of an existing access violation or translation invalid
mmfault. (e.g. Bad S0 pte in the middle of a user page fault) (arch/vax/mm/fault.c)
<p>Save/Set up the RPB properly so we can restart if needed.
<p>Make sure we keep the VMB/PROM bitmap safe from the memory allocator.
Use the information in the prom bitmap to feed information about bad pages
to the bootmem allocator.
<p>Replace CONFIG_VAX_4000HC with something else.... Currently its more
like CONFIG_HARDCODE_INTERRUPT_NUMBERS anyway, and we need to remove the
is_ka46() rubbish. This is what machine vectors are for...
<p>Implement system call trace pathway (arch/vax/kernel/entry.S, syscall.c)
<p>Implement ptrace and profiling processes etc...
<p>Read/Write system clock routines.
<p>Systems with full hardware clock implementations (KA55) need correct
handling of ticks.
<p>Implement DMA routines for vsbus systems. KA46 has a stub that could
be more intelligent.
<p>Implement missing SCB fault vectors (floating point, reserved addressing
mode etc) in place of the stubs.
<p>Arithmetic needs attention to do a proper job on SIGFPE - returning
info etc...
<p>Occasionally, parent processes dont get woken up, when their child exits,
and we end up in the idle loop.
<p>Coredump problem sizeof(elf_gregset_t) (64) != sizeof(struct pt_regs)
(68)
<p>The KA46 needs code to turn the Floating Point unit on at boot.
<br>&nbsp;
<h1>
Drivers</h1>

<p><br>Occasional Misdetection of console and network interrupt vectors.
<p>Improve ka43_diagmem handling in lance driver. (parity control bit and
memory over 16mb).
<p>SGEC network card driver (Richard Banks)
<p>vax-5380 driver is snail like slow, and occasionally locks up under
heavy swapping.
<p>Need a NCR53x9x driver for the 4000/60. There is a chipset driver in
drivers/scsi/ and several example templates. The sun3 one looks good.
<p>Lance driver doesnt work on KA46. It gets to init the card, and dies
with a memory error (csr=8881).&nbsp; The KA46 DMA region/registers need
sorting properly.
<p>If we halt using the usual method (/sbin/halt) the console stops accepting
input. On halt how should the dz console be setup?
<p>Sometimes, we get null characters fed to a shell, when one of its children
exits. This can be interpreted as EOF, and the shell will exit unless ignoreeof
is set. (Seen on tcsh, and bash (although bash had other problems))
<br>&nbsp;
<h1>
GCC</h1>

<p><br>Update to gcc 3.0 when glibc can compile with it.
<p>Can't compile natively without REAL_ARITHMETIC defined, why not? If
we do, constant doubles are stored with the wrong bit pattern, and generate
reserved operand faults. e.g. compile + run "make". Debug native compiler
build.
<br>&nbsp;
<h1>
GLIBC</h1>

<p><br>Start port. (Dave Airlie)
<br>&nbsp;
<h1>
uClibc</h1>

<p><br>Assembler error messages compiling des.c
<br>&nbsp;&nbsp;&nbsp; /tmp/ccX7jORA.s: Assembler messages:
<br>&nbsp;&nbsp;&nbsp; /tmp/ccX7jORA.s:1231: Warning: Ignoring statement
due to "Bad operand"
<br>&nbsp;&nbsp;&nbsp; /tmp/ccX7jORA.s:1231: Warning: Ignoring statement
because "a register has no address"
<br>&nbsp;
<h1>
Bootloader</h1>

<p><br>Generic Bootloader. asbl handles basic scsi boot on KA42/KA43...
<br>&nbsp;
<h1>
Miscellaneous</h1>

<p><br>Update mopd to use new packet filter API.
<p>Dynamic libraries.
<p>

<script>
<!--
document.write("<font size=-1>Last modified "+document.lastModified+"</font>");
// -->
</script>

</body>
</html>

Index: header.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/header.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- header.html	2001/09/19 15:53:39	1.1
+++ header.html	2001/10/09 22:44:44	1.2
@@ -22,5 +22,7 @@
 <A HREF="links.html" target="_top">Links</A>
 |
 <A HREF="download/index.html" target="_top">Downloads</A>
+|
+<A HREF="todo.html" target="_top">ToDo</A>
 </FONT></FONT>
 <HR width=690 align=left>

[LV-commit] CVS: www/htdocs/newfaq linux_vax-1.html,1.1,1.2 linux_vax-1.html.old,1.1,1.2 linux_vax.sgml,1.3,1.4

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/newfaq
In directory usw-pr-cvs1:/tmp/cvs-serv26116

Modified Files:
	linux_vax-1.html linux_vax-1.html.old linux_vax.sgml 
Log Message:
link to open bsd/vax



Index: linux_vax-1.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-1.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux_vax-1.html	2001/09/19 17:41:35	1.1
+++ linux_vax-1.html	2001/10/08 10:09:57	1.2
@@ -71,6 +71,8 @@
 <A HREF="http://www.netbsd.org">NetBSD/VAX</A></LI>
 <LI>
 <A HREF="http://www.linux-vax.org">Linux/VAX</A></LI>
+<LI>
+<A HREF="http://www.openbsd.org/vax.html">OpenBSD/VAX</A></LI>
 </UL>
 <P>
 <H2><A NAME="ss1.4">1.4 Where do I buy one?</A>

Index: linux_vax-1.html.old
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-1.html.old,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux_vax-1.html.old	2001/09/19 17:41:35	1.1
+++ linux_vax-1.html.old	2001/10/08 10:09:57	1.2
@@ -71,6 +71,8 @@
 <A HREF="http://www.netbsd.org">NetBSD/VAX</A></LI>
 <LI>
 <A HREF="http://www.linux-vax.org">Linux/VAX</A></LI>
+<LI>
+<A HREF="http://www.openbsd.org/vax.html">OpenBSD/VAX</A></LI>
 </UL>
 <P>
 <H2><A NAME="ss1.4">1.4 Where do I buy one?</A>

Index: linux_vax.sgml
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- linux_vax.sgml	2001/09/24 10:27:58	1.3
+++ linux_vax.sgml	2001/10/08 10:09:57	1.4
@@ -61,6 +61,7 @@
 <item>Compaq ULTRIX/VAX
 <item><htmlurl url="http://www.netbsd.org" name="NetBSD/VAX">
 <item><htmlurl url="http://www.linux-vax.org" name="Linux/VAX">
+<item><htmlurl url="http://www.openbsd.org/vax.html" name="OpenBSD/VAX">
 </itemize>
 
 <sect1>Where do I buy one?<p>

[LV-commit] CVS: www/htdocs newsframe.html,1.1,1.2

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs
In directory usw-pr-cvs1:/tmp/cvs-serv20348

Modified Files:
	newsframe.html 
Log Message:
news items about root image and death of FTP site


Index: newsframe.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newsframe.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- newsframe.html	2001/09/19 15:53:39	1.1
+++ newsframe.html	2001/09/24 14:01:13	1.2
@@ -14,6 +14,34 @@
 <!-- News entry boundary -->
 
 <TR VALIGN=TOP NOSAVE>
+<TD>24 Sep 2001</TD>
+
+<TD NOSAVE>
+The old FTP site is no more. A copy has been saved at 
+<a href="http://www.pergamentum.com/~atp/vax/old_ftp/">
+http://www.pergamentum.com/~atp/vax/old_ftp/</a> But its
+pretty much out of date. New stuff is at the download link 
+off the main page.
+<P>
+</td>
+
+<!-- News entry boundary -->
+
+<TR VALIGN=TOP NOSAVE>
+<TD>23 Sep 2001</TD>
+
+<TD NOSAVE>
+A new root image has been posted to the download area.
+This contains instructions and prebuilt kernels for some
+VAXstatsions, and should allow (with some self assembly)
+most people to enjoy the bleeding edge of Linux/VAX 
+development.
+<P>
+</td>
+
+<!-- News entry boundary -->
+
+<TR VALIGN=TOP NOSAVE>
 <TD>20 Sep 2001</TD>
 
 <TD NOSAVE>

[LV-commit] CVS: www/htdocs/newfaq linux_vax-2.html,1.2,1.3 linux_vax-2.html.old,1.2,1.3 linux_vax.sgml,1.2,1.3

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/newfaq
In directory usw-pr-cvs1:/tmp/cvs-serv1858

Modified Files:
	linux_vax-2.html linux_vax-2.html.old linux_vax.sgml 
Log Message:
Remove old ftp link as the ftp site is going away


Index: linux_vax-2.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-2.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- linux_vax-2.html	2001/09/20 23:35:10	1.2
+++ linux_vax-2.html	2001/09/24 10:27:58	1.3
@@ -154,9 +154,10 @@
 
 <P> 
 <A NAME="started"></A> 
-Read Documentation/vax/README at 
-<A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax</A>. 
+Read the "How to get started Hacking" document in the 
+<A HREF="../docs/index.html">Documentation</A>section. 
 This describes howto download the compiler and kernel, and set up the MOP boot.
+Unfortunately its a little out of date. Sorry.
 <P>
 <HR>
 <A HREF="linux_vax-3.html">Next</A>

Index: linux_vax-2.html.old
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-2.html.old,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- linux_vax-2.html.old	2001/09/20 23:35:10	1.2
+++ linux_vax-2.html.old	2001/09/24 10:27:58	1.3
@@ -154,9 +154,10 @@
 
 <P> 
 <A NAME="started"></A> 
-Read Documentation/vax/README at 
-<A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax</A>. 
+Read the "How to get started Hacking" document in the 
+<A HREF="../docs/index.html">Documentation</A>section. 
 This describes howto download the compiler and kernel, and set up the MOP boot.
+Unfortunately its a little out of date. Sorry.
 <P>
 <HR>
 <A HREF="linux_vax-3.html">Next</A>

Index: linux_vax.sgml
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax.sgml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- linux_vax.sgml	2001/09/20 23:35:10	1.2
+++ linux_vax.sgml	2001/09/24 10:27:58	1.3
@@ -212,10 +212,10 @@
 need to implement for a machine vector. <p>   
    
 <sect1> How do I get started? <p> <label id="started">
-Read Documentation/vax/README at 
-<url url="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax" 
-   name="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">. 
+Read the "How to get started Hacking" document in the <htmlurl
+url="../docs/index.html" name="Documentation">section. 
 This describes howto download the compiler and kernel, and set up the MOP boot.
+Unfortunately its a little out of date. Sorry.
 
 <sect>Specific problems<p>
 <sect1>Where's the serial console switch on my VAX?<p>

[LV-commit] CVS: kernel-2.4/arch/vax/kernel process.c,1.13,1.14

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel
In directory usw-pr-cvs1:/tmp/cvs-serv6723/arch/vax/kernel

Modified Files:
	process.c 
Log Message:
DA: setup AP with current SP .. needed for dynamic loader


Index: process.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/arch/vax/kernel/process.c,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- process.c	2001/09/11 19:23:38	1.13
+++ process.c	2001/09/22 19:44:18	1.14
@@ -260,6 +260,7 @@
   set_fs(USER_DS);
   regs->pc = new_pc;
   regs->sp = new_sp;
+  regs->ap = new_sp;
   regs->psl.prevmode = PSL_MODE_USER;
   regs->psl.accmode = PSL_MODE_USER;
   /* write the sp into the user stack pointer register */

[LV-commit] CVS: www/htdocs/download README.vaxroot-20010920,NONE,1.1 vaxroot-20010920.tar.bz2,NONE,1.1 dlframe.html,1.3,1.4

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/download
In directory usw-pr-cvs1:/tmp/cvs-serv21513

Modified Files:
	dlframe.html 
Added Files:
	README.vaxroot-20010920 vaxroot-20010920.tar.bz2 
Log Message:
Add vax root image and readme


--- NEW FILE ---
readme for vaxroot-20010920
 Contents:
 	1)  Installation
	  	- common
		- NFS
		- SCSI
	2)  Example Bootlog
	3)  List of installed packages.

 *****************************************************************
 WARNING This is not "Internet ready" The root and default users 
 	 have no passwords set. Several of the packages are old and
	 have known vulnerabilities. This is for development only.
	 Additionally if you use NFS boot, this requires the file
	 system exported r/w, and with root remapping turned off
	 from your NFS server. 
 *****************************************************************

 This tar file holds a Linux/VAX filesystem. This file system can
 be installed to boot from a SCSI disk, or as an NFS root file 
 system from a suitabe NFS server. 
 
 It also holds two kernel images, the first called vmlinux.ka43.SYS
 which is suitable for these KA42 or KA43 systems 
      Vaxstation 3100m30
      Vaxstation 3100m38
      Vaxstation 3100m40
      Vaxstation 3100m48
      Vaxstation 3100m76
 The second image is called vmlinux.ka46.SYS and is suitable for these
 KA46 based systems;
      Vaxstation 4000/60
      
 Both kernels can be used for either scsi or mop booting.
 
 1) Common install tasks.
 
 Untar this file into a suitable directory (e.g. /disk/vax/vaxroot)
 
 Decide on a suitable name and IP address for your vax, and 
 edit the etc/hosts file, and etc/HOSTNAME files to set these for 
 your VAX. 
 
 e.g.
 # more etc/HOSTNAME  
 vax.pergamentum.co.uk                        
 # more etc/hosts
 127.0.0.1 localhost  
 192.168.70.10 vax.pergamentum.co.uk vax
 
 Edit the etc/fstab file to setup suitable values for the root file
 system and swap device. If you are using the NFS booting method then
 comment out references to scsi disks (e.g. /dev/sda1). You dont need
 to supply a root file system entry for NFS boot, as it is supplied 
 by your NFS server.
 
 Decide if you want to set a root password, and a password for the
 example user "user". Both are currently blank, and passwords are 
 not prompted for. See the note above. 
 
 NFS boot
 --------
 
 Other things you will need;
   1) The mopd-linux daemon on your NFS server to download the kernel
      to the vax. This can be got from the Linux/VAX webserver.
   2) bootpd, or dhcpd to supply the vax with its IP address, and hostname.
   3) NFS server programs 
   4) The setcmdline program from the asbl-0.1. package.

 The rest of this section assumes you have access to a system running
 Linux/i386, or similar and that this is your NFS server on a private 
 network to your VAX.
 
 Set up the mopd-linux to download the kernel of your choice to the 
 vax when it boots. e.g. if you have a KA43 with ethernet address 
 08:00:2B:27:37:C6, copy the vmlinux.ka43.SYS file to /tftpboot/mop
 and create a link from it to the file name 08002b2737c6.SYS. 
 i.e. 
 /tftpboot/mop/08002b2737c6.SYS -> /tftpboot/mop/vmlinux.ka43.SYS
 Start mopd.
  
 Setup dhcpd to supply the right IP address and hostname.
 e.g /etc/dhcpd.conf looks like this
 subnet 192.168.70.0 netmask 255.255.255.0 {
      range 192.168.70.50 192.168.70.100;
 }
 host vax {
      hardware ethernet 08:00:2b:27:37:c6;
      fixed-address 192.168.70.10;
      option host-name "vax";
 }
 Start dhcpd.
 
 Export the directory you untarred into from your NFS server to your
 vax. Put your vax in the NFS servers /etc/hosts file.
 e.g. /etc/exports
 /disk/vax/vaxroot  vax(rw,no_root_squash) msslv2(rw,no_root_squash)
 
 Start the nfs server programs (portmap/nfsd/mountd)

 Set the kernel command line in your mop boot image to match the path
 in the /etc/exports file, using the setcmdline program from the asbl-0.1
 package e.g. (all on one line)
 setcmdline /tftpboot/mop/vmlinux.ka43.SYS \
  "root=/dev/nfs nfsroot=/disk/vax/vaxroot/ rw debug"

 Try and boot your VAX
 e.g. on a KA42/43 
 >>> boot esa0
 
 Eventually, if all goes well, you should see something resembling the 
 boot log at the end of this readme. If not, the system logs are your
 friend.
 
 SCSI boot.
 ----------
 
 This is currently only available on KA42/KA43's as we dont have a 
 driver for the scsi card in the KA46 organised yet.
 
 This assumes you have a SCSI disk you can partition and attach to the
 VAX, or a shared SCSI chain. This example supposes a RZ24 type disk.
 
 In addition to this, you will need the asbl-0.1 package from the 
 Linux/VAX webserver.
 
 Partition the disk using fdisk e.g.
 # fdisk /dev/sda                    
Command (m for help): p    Disk
/dev/sda: 64 heads, 32 sectors, 200 cylinders
Units = cylinders of 2048 * 512 bytes
   Device Boot    Start       End     Blocks   Id  System
/dev/sda1             1       150     153584   83  Linux
/dev/sda2           151       200     51200    82  Linux swap    

  make an ext2 filesystem on /dev/sda1 (and other devices as needed)
  mke2fs /dev/sda1
  mkswap /dev/sda2
  
  Mount /dev/sda1 and untar the vaxroot.tar.gz file onto the disk. 
  Edit the etc/fstab file to reflect the right scsi devices for 
  root, swap and any other mount points.
  
  e.g. etc/fstab
  none            /proc           proc    defaults        0       0
  /dev/sda2       swap            swap    defaults        0       0 
  /dev/sda1       /               ext2    defaults        1       1
  none            /dev/pts        devpts  gid=5,mode=620  0       0
  
  Change to the directory you have mounted the root filesystem under, 
  and change the kernel command line of the vmlinux.ka43.SYS kernel
  image to reflect the new root device, using the setcmdline utility
  from the asbl-0.1 package e.g. (all on one line)
  
    setcmdline vmlinux.ka43.SYS "root=/dev/sda1 rw debug"

  Create a boot block using the asbl program. Note, you will need to 
  cross compile the sdboot.S file to produce a VAX binary boot block. 
  
  Install the boot block using dd. 
 
  unmount the disk, power down, and transfer to the VAX, and boot. 
  e.g. 
  >>> boot DKA300
  
  If all goes well you should see a boot log like the following. 
  
  
2)  Sample Boot log
    ---------------

>>> boot esa0

-ESA0
CPU type: 
80007E04KA43
Boot Head.S loaded at address 00007E00
rpb/bootr5/ap/sp  00000000 00000000 00000334 00007C00
relocated at phys address 001002F1
CPU type: 0B000006 sidex: 04010002

Starting VM
Linux/VAX (lin...@mi...)
IO mapped phys addr 0x200a0000, 0x0001 pages at virt 0x813c0000 (IOMAP PTE index 0x0000)
IO mapped phys addr 0x20080000, 0x0001 pages at virt 0x813c1000 (IOMAP PTE index 0x0001)
IO mapped phys addr 0x21100000, 0x0001 pages at virt 0x813c2000 (IOMAP PTE index 0x0002)
IO mapped phys addr 0x21000000, 0x0020 pages at virt 0x813c3000 (IOMAP PTE index 0x0003)
RPB info:  l_pfncnt: 00009e00, .l_vmb_version: 0b000106 .l_badpgs: 00000000
Physical memory: 00009e00 HW pagelets, 000013c0 pages  (20224KB)
CPU type: KA43, SID: 00000000
VM: mapped physical from 80000000 to 813c0000, iomap from 813c0000
VM: vmalloc from 814c0000 to 818c0000
VM: ptemap from 818c0000 to 83bc0000 for 64 processes
calling start_kernel...

Linux version 2.4.2-20010307 (at...@at...) (gcc version 2.95.2-linuxvax-20001231 (release)) #251 Fri Sep 21 14:16:00 BST 2001
kernel_cmd_line 80007e04
root=/dev/nfs nfsroot=/home/disk_vax/vaxroot rw debug
VAXMM: Initialising mm layer for 64 tasks of size 64MB
VAXMM: system page table base 80270000, length (bytes)    77800 length (ptes)    1de00
bootmap size = 00000278
calling free_bootmem(start=00001000, len=000ff000)
calling free_bootmem(start=002e8000, len=010d8000)
On node 0 totalpages: 5056
zone(0): 4096 pages.
zone(1): 960 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/nfs nfsroot=/home/disk_vax/vaxroot rw debug
Calibrating delay loop... 10.13 BogoMIPS
Memory: 17932k/20224k available
Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
IO mapped phys addr 0x20080000, 0x0001 pages at virt 0x813e3000 (IOMAP PTE index 0x0023)
vsbus: interrupt mask 0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
pty: 256 Unix98 ptys configured
block: queued sectors max/low 11824kB/3941kB, 64 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Serial driver version 5.02 (2000-08-09) with no serial options enabled
DECstation DZ serial driver version 1.02
ttyS0 at 0x813c0000
ttyS1 at 0x813c0000
ttyS2 at 0x813c0000
ttyS3 at 0x813c0000
dz.c: using irq rx 176, irq tx 177
PPP generic driver version 2.4.1
vaxlance.c: v0.008 by Linux Mips DECstation task force + ai...@li...
KA43: enabling KA43_DIAGMEM for memory from (802f0000) to (80300000)
IO mapped phys addr 0x200e0000, 0x0001 pages at virt 0x813e4000 (IOMAP PTE index 0x0024)
IO mapped phys addr 0x20090000, 0x0001 pages at virt 0x813e5000 (IOMAP PTE index 0x0025)
Ethernet address in ROM: 08:00:2b:27:37:c6
IO unmapping 0x0001 pages at PTE index 0x0025
 probed IRQ 148, vsbus 5
Using LANCE interrupt vector 148
SCSI subsystem driver Revision: 1.00
IO mapped phys addr 0x200c0000, 0x0001 pages at virt 0x813e5000 (IOMAP PTE index 0x0025)
scsi0 : at 0x813e5080 irq 254 options CAN_QUEUE=32  CMD_PER_LUN=2 release=1 generic options AUTOPROBE_IRQ AUTOSENSE generic release=7
scsi0 : VAXstation 3100/MicroVAX 3100 NCR5380 SCSI
  Vendor: DEC       Model: RZ24     (C) DEC  Rev: 221B
  Type:   Direct-Access                      ANSI SCSI revision: 01 CCS
  Vendor: DEC       Model: RX23     (C) DEC  Rev: 0054
  Type:   Direct-Access                      ANSI SCSI revision: 01 CCS
Detected scsi disk sda at scsi0, channel 0, id 3, lun 0
Detected scsi removable disk sdb at scsi0, channel 0, id 5, lun 0
SCSI device sda: 409792 512-byte hdwr sectors (210 MB)
Partition check:
 sda: sda1 sda2
sdb : READ CAPACITY failed.
sdb : status = 0, message = 00, host = 0, driver = 28 
sdb : extended sense code = 2 
sdb : block size assumed to be 512 bytes, disk size 1GB.  
 sdb: I/O error: dev 08:10, sector 0
 unable to read partition table
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 1024)
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 192.168.70.8, my address is 192.168.70.10
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.70.8
Looking up port of RPC 100005/2 on 192.168.70.8
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 36k freed
INIT: version 2.77 booting

			Welcome to Linux/VAX


Mounting proc filesystem
Setting clock : Thu Jan  1 00:00:06  1970
Thu Jan  1 00:00:07  1970
Activating swap partitions
Adding Swap: 51196k swap-space (priority -1)
Setting hostname vax.pergamentum.co.uk
Remounting root filesystem in read-write mode
Mounting local filesystems
Enabling swap space
INIT: Entering runlevel: 3
Enabling IPv4 packet forwarding [  OK  ]
/proc/sys/net/ipv4/ip_always_defrag is missing -- cannot control IP defragmentation
Bringing up interface lo [  OK  ]
Initializing random number generator [  OK  ]
Mounting other filesystems [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting INET services: [  OK  ]

vax login: root
# uname -a
Linux vax 2.4.2-20010307 #251 Fri Sep 21 14:16:00 BST 2001 vax unknown
#    
    
3) List of installed packages 

    All packages compiled static, with a native compiler, against uClibc.  
 Some packages are incompletely built. Info files, man pages and 
 internationalization files have been removed to keep the download small.

asbl-0.1/ 		-- scsi boot loader
ash-linux-0.2/		-- default shell. 
bison-1.28/
byacc/
diffutils-2.7/
e2fsprogs-1.15/
filesystem-1.3.5.tar
fileutils-4.0/
findutils-4.1/
flex-2.5.4/
gawk-3.0.4/
grep-2.3/
initscripts-4.48/
jed/
make-3.77/
mingetty-0.9.4/
ncurses-4.2/
net-tools-1.53/
netkit-base-0.10/
netkit-telnet-0.10/	-- telnetd does not work.
popt-1.4/
sed-3.02/
sh-utils-2.0/
slang/
sysklogd-1.3-31/
sysvinit-2.77/
tar-1.13.11/
tcsh-6.08.00/		-- this has the odd lockup (SIGCHLD related?)
termcap-2.0.8/
texinfo-3.12h/
textutils-2.0/
tools/			-- binutils, egcs-1.1.2 under /usr/vax-dec-linux
uclibc/			-- From our CVS 20010917
util-linux-2.9w/
zlib-1.1.3/

--- NEW FILE ---
BZh91AY&SYŽ¾ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿå)ûß{o9ÞóÕöú|™³töÌ®‡AánÎj°
@ÜXû—eì:(¯g¬—­



vÈ­´[3¶ƒì{°- ¦-+°ÓÓæ†tTUöèI«a•
¢‚B¨éÛ(ø^Ö%äP­yÝÍ׎z.ÔßlŽøßéŠâzs‡u64ÛíÜ¢(¾ÝÙϏtû}»´ðà:K>€vÎq1Õ]5U­öÞ-CÞ»ÂôIqzÐrù±®¼îëëÀõîê6°6ÈwQKÖNÅìï{Ûz§l6ÐK·M9¶­€d`zÓâpÃ4¬,ßAéÂð+è
Z8f°O£î«Ô³_<ôœòâzç
ݟo_3ÉÂ}ö–‹ÚN^S¾wÒ¶o¯‚ú=í»wx8eöÏ oiô=³¾m
m™‘ÐuÑKn‡A_	 ÷¼9ޜêF#«
îpq˜a˜nç4ŽûNîðìhŒ;ÝÚR½Ã°ÇÞàq¬3¾ó£¡è„÷Øûì> =bF6pß}îÃ}	‰ºÜ=Îqƒ±“c=.áÃ0ÝGnv«·8kµë˜À
T
U'¶]¸ÛÛÓÞÌ»€zß=ï÷Ë)+›<œïu;°ËJn÷yÌÍÓ®{ÙÔzʙ¼Çrt
•ïp=íh|'¯5•è¡I

|¯9Ôv¶’鹺­ØöŸí:ãѤ†²¦Žº
GÛ;Ö¯‰ÑÐUd{ïs¦Û ëâ>€è6Ï ñ´
­¯xc¡ôzùï;|,P=÷ŽØöÞÑ.ÇÞ¯äø}áõóR»îÝ>Wƒ×m| ‰ß¦5¯­ögl¬×{Õñˆ•v‘ë§T®´uì>Uâ+É4-$¾îsoOr½¨¶Ù&Äòníã‡mãÙAî§WC¾ót:¥Pl¡ôuփAÑіMX0x¹8¬Ø¼®rT—ßy_o¾›ÌÅÛYøÆ©M6¯rž÷²9Nu:jš3m)·>îz’Rç}½ÕR¼Ì„QDˆM.-Æf€("(HÞ[îYð(ûKåËnnÁuk@	ïo{ãæï½Äúm³¼õȵ ¶-›ïwÆï»Êú†7TåÊíÛjA¶y›”­¶ØmÄê{Ýã<&8¹Îìî=ð¼ÆwrŽlm_nƒ¯Žß3Kݝ¶óYÞÞø³¸Í;G°‚2éo{¸»$èÈKX½2Îs¶9ÖmÛGʾìÍs†¹Q æË´
B,û»‹°Ñõ¡N€Ûu÷ÃÈùš¶gmÓ»,|œõ®™W]:c¤žöÊÅë-‹=ãh:ñvcJ•§EzÄê8çlwP)äfûîà
°wŽ½¢ŸXW!÷¡ÕO}j:ïw½_C™gËÙæᜏ}Þúù^óי=:둪Ëݝö
w>ï<Ԗë#²µõ­ªÅkb<諭\öPU$ﻤP ¥J¤ã㾬ûû3¬e{e˜ŸfÆm5
ZÐ*±}Š	Ö:½ŽÌ9»Øê½
©¼z=ÈÐ0 ÜÛaXVï˜ï¾c
TÇ2MÚñÜöÕ=t݀
õé×vU5‰ZÜÛnÛ¦™®ÒÝuíâwۈé¾n;`
(wÉèç`ꫪ¬õ‚…Ù iïw<ǧºuÒ
êõV=áÞõµ¥WŠ•Z5»uLځ›F†™òóëŽé„ê%wtǵÜ9¥;¬ww-e‡ö=̑€=ۍ¦vÃëì

”$¤ˆ
[...34967 lines suppressed...]
JmE±híÇ4øß¿cõ<>Z»‘†í½E›d¢~ǺfÙ°ü˜íl3͗<æ,»z†ï|B›;¿4é¡:vc¥øÅI=[ÔVºñ}3७…UÌ
áêLÛÇç>ÕʔY¿âKmWaÍ}_7©Ë}[[C±op“PfœÜ}áŠf‹Þ´ªÕÂjÄLœìlÍô´Jm¬Â5Š0ãÅÀ_Z{ÜÍm,’¾Öá‚1¬¡ã¶l"ŠêÆ1kQ
Èíƒ6·4)¡bû‘(ÍJÇÃK
>	ÑoY)[s£`Qƒú]øwÀÛª¨ËŸ0µ(IóþþÃýõW+e¦‡ñå^ô÷¯Êûž»þëýv»œ‚9ìE?cgî{oª’†P0̏PãydÚ¬CáÐ( ²æ³yí›·ãÍ?®Ö²
M2z^V«
¹ïj?ÍÓïËwö(dXîՎ¥Ôåú™E³âz·¯{ÄÃjÀQvûÙÞuLºã¤Ò@ÐÅû·½Àg÷ˆIT¦I„¡<r›è­6•Bˆ¾×ú
.ïõÒl؆Ä.[~‚Ì•¥û6˜ËdÌÀ…Uœ¿Þvx·÷pð³{€´è(öcË}øü5÷Âó'âV¢ù°Áî¤Ð(j´(•p‰"ÛÉe†=Óùõ#e½ž?¯­y=y@ü;Â~4þ/×áâäø½æ
ؾÿq[wò~rØÝe4×Ý ê÷ü>6{oÈ,O—üvG8š?£ÜVõ¿çnÁì,ºÌɞ<¶5‘›¾ùNî·)%Aâp»õ]p±
XQñߣŒt[¯÷´«Déoñ-ø_üî0Ðu˜[ÃÉ)Ê¥	 1í{þÁÍYÎFBc¢>×èÃ
åu­¶µYŸdêdh`Çx0öqýßýöÆö±0„¨ZwfΦäzú¸ö±ÁÆV¬Xõ¢GíkIóÛ=My¹2ɐ>·õâ¯ÃäøJܵ³Áë˸yw$`óÜÀ7K¾Ü ;ô8¨C¤‹=ÁÒ/á¼ÚNÝËÀ$»¯È‡
yŸ¹ßÜƏë™O‰
¯kF
­t>gò¤@$p´Ô0P†¥KÒC<’Ñ[¢ðMðèn\Jس¼§Àð&ì-hðÕß)°x‘ê_Pã:óÚ ˆnFäq?p|dpåÇxЅ¹èèxŽtÊÉ.·l|K;žöHÞ¢£Í!ú£á>Û£3¤±{‡Ç«Ì?.åù³ºÄBn=j1ùoȎá؎(ûÂû‘y³‰ñ¡ÓÍS5ñ ˆ¨SáCnã6¼Ì±hÌ|íŽúIV¿ÖÖ½ó«Æo!Îü•â±ë©&û¡MËn
ÄÄ8—I¹iûÞ\¼jS‘¹ØÚyËùå·,.Xn[	˜wÈò„wfArt"HLXŒ¡ýLŠ·$‘@Ç?Pd7f×8‚=ä§hc?¸ÕfóÔ\ÜÖYÞh“Ž«g«2Ó<¦-)>7‹_S_qܑףÑÚ'ŽÚW
ȋu;vÛÐ9ŒX]Òh‹nçé36ÔÄ»T”úW=Èã‚xW´ø/tE¼Üیiˆ±74AÃO»Åœ
Á²üœ-®=éµòvŸã »óg½}æ…dôÇB†š)Cpþ‡5=WN¾ÂÉ;_u##½7ðÅZêNó$|sî3üFÃ<2K™K:(כLaDyò<¸Žs¨£êxûÅåöV!jø|ñì¨5n=óÂ+„2ÛF—/{vë;V¡˜`±V7ÚËMmOńv-Ò­`üêMn4ï9V¦3G\'s‡®¸¶®¹Šlj« ›9‹scÝG›Ýßí¦/ͦ$­²_»àðc™Êƒ¯™êþv¢rlî¹ûYvqrVÆ9NÍs[§û”áڛÎÝ8qœiG²ÓaÇ4x—znÔåT&qR®ÅgNã饺k^f±eloO2©Làœ8òuŠ™_4Âyþo&nÞ#´
#abÊP7Oƒ…˜]±Ð{^ö"ÍÝ8š²Ýƒ%	|–ODåÜU·s
WS½þ âf`a•ê]Ó$e¶WÃJÑÙ¯,¹S6Cs«¸çÚ#ØKuõLc<Nw(Ù…jØÛ žîfð}áϨ[LMÝc²>oGƒô[è$I‰-Ì_DZéߓÅhã
¬8E”J±ïšSÌ€=~:RAÜñ+{9£áv®äã¼ÿï쑳3™3ìö8.¾,™T†ïl€ 5Pq‰Ø(:)´ôéÛ—<ûêê÷tœ#ü?‚ßâþ{¦Ánýë(àÊô­Ó•ûýÉ¥Âóû¯°ýrõ¾&#ûàþâ¤ý§øø}÷aÀ¿ß=<»PÃ|Æoa'–ô_5¼¾cÕÉIhe¯	¢ê–”æ=¶–
}5Ïù;÷ˆÞ&§Ìì¯>OÊkÓ
//5˜ä{ÚH"áÅð</§ò‡‰áѹ>ìn׈aû±	lžÛzÎ~Foßî½Y:Kç§êÝŠ'©neö®Ž–9î|Í.å˜s=”ä+KL—GüvüLÒ~ˆ:íóÅL:æ
Çèûy}{Ø|–ßêèXS¦â™0á÷tsÝ(z¿YÊú3Ø|Y'‹<;Q	ÞX„„$Œ'äsՈý›QŠˆÍ¹~.]UŒE}µõa_·þ^­¯üÁÊ
Å –§d™ÞÛ½@T]ځ‚!GëÑÏ{¿‡ü±Áþ-W‡X$’ðý;Y•~¯ê]y jB’A•³¸:ïÆ¥OèŽyíðe»y8Ÿ›¿^“
Œ°yÿ~ŸÜÊtñÜèm·ð5©‘Še Ê)€3˜aÕ23#ægäki
Ž{ódmùKàŦ9QøJh|o‰„5­
ª¥_b+¿m;ÎþxO™<uQ5ñ…O¯V5l”íµkW(’'œ
6íûôiÀԆ;ºT8шݬVT¨×
_Þ6o>pwÖ&!:§£y8³ì¿
,I¸ÎÙ„.è7]“ùߨ°1$“t8Bb¡ùÁx&†Y
ªÞCÉã~•à
d„
âÎÿå^hÂHDäãžp¨	Oùb¤Pæ¢dG~;~É’EZ‡,²/^ŸúFY‚?½»¸’Â'´Ák±
$Œ{ZÖÇÙsAS'ßíp뒧øÙ±ÜñQðWð>nïa{=wmÍÛP?O+†ôµÍÍAђ?Ɯ9”‡/:Üu»‹17Ñòa‚Ãå{—Ç—Vù¸T=Ž~z~ÿ°[a¿wЄ¶;åÂ!ÉÙ+ÄÀ…åñ53ÿ$0´AYz'ý$¯6pG¡ËtéXëï?³œKʎŸ5°Ìô1h zP½VįúP>aDÿ<F\Ãc¼bõ@ëöî$÷=Š§'¶<£ëó[ÍvO²ad5¼QTšo6~B6!¦þÿÏfê{9Aá¹øk	PX°ékg)D5Fڇ6GŽs}¬ÿkANÆçr[džÞ†èf»^(KrI)#ßÏÖ×U¯ÞìBr>²Q×gy†ƒ¨‡x8E¸‡´D•fBL:ÿS¼âÖTx‰ïÆñ£È.5v˜9ïââö¡gæ
Œæ›1®Ñ4šeZçìMÚ\¢×w\£ãôü¶lÅÁËûªNG^ǽؒA#…_}­'$GW
Jg,	i,#bΔl?ù6 ±;9íÇÐocHºÏpã;¡Èûë`Yת©:;ë=öZÒ¨ú¾²¿Îþ‡ü–ÈìܞGÖ7䃒@àB-PîÔC‚/'QH
¹
Rˆ¢	}…ʺ˜g-D+”I´‘7.DRm¦­X«ØŒÜEX8¥“u˜‹S°¹,6e0C+B *̺3Êu{äކAFõ{âѲE9w„YU°Ÿ4îõBf‘ZæMˆ™ÌÄN á6Yß‹5$øòÏTç3ªmy“a|­¨<†GP–bÑÃ6ac©Q˜”î™Ü«³6„ ’å³0ãT¥Øƒl<¹Ë¾ŠCÃ`¡Œ:kaÌó@Ÿö,S0P8A
o5+%-ÓøT—ÇÑ%Á?ËטåƸCïÑñ^*“p´³ÂˆH»ÁC˞k^áR[¼üßóZPýÑ@óBßü:=HKÇuGÔp³óOd¹%ÀG‚»Ñâ"ˆ|¶­Ö
€áœA‡—õDhîøÝ9ÐèzçÔ ¾E%"jþ
TÒ"(zuLjçfV<¿†ª
šAZ›êR7iš¦EQ"tкÔúб±I#ý©ÉeàÓ'<(aÀ÷{y¬vŠš™LòPŽA=÷Ê9öø¯ÍûÙ¢™¶!ËlI
oeW/_f<\\_Dä!Œ¹ìC˜ˆ×?³ÞäõALo%§[¶j«mø·ð:ÿ×´å¡h*+˜Nâ=±#(\úb7ú
Ô¹EqÊÕ=£7m¯±‡)}q°Xò™­çÿnnÂZPE<š}}â6³Ã§ÊaCoòo2ZÕ	
14kßð¼ÿÜùºØ„!£(…nêÿúô-ÚД,:ØUAƒWh!
׸ätܟ	æk™‹ Ïú¿/E«“àí\¾ø[Öïãâ8o٘	#è!¼õ\;/²°_¼¡ÆK赝¸á‹ÜÆø™{ycœwQ(z/WÏ|øÛ5¦Ù==<;þ§E'A	‹å\…Ì‹§$¨¸(ã¬{[Z^ɔ2â_0OÖ$Bã:[Ë7=ÝŸSnI	#7^—G~
!ÆÿÝHgÐçõ¿…ô¬aæy²Ì€ˆ„bSçÏ#G¼ù>ƒ·£þô
Index: dlframe.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/download/dlframe.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- dlframe.html	2001/09/21 20:12:47	1.3
+++ dlframe.html	2001/09/21 21:25:29	1.4
@@ -27,6 +27,8 @@
 <li><a href="tools-bin-linuxvax-20001231.tar.bz2">Cross compilation toolset
 for Linux/i386</a> 
 <li><a href="asbl-0.1.tar.gz">Andy's SCSI boot loader</a>
+<li><a href="README.vaxroot-20010920">Instructions for Linux/VAX root image</a>
+<li><a href="vaxroot-20010920.tar.bz2">vaxroot-20010920 root filesystem (8583002 bytes)</a>
 </ul>
 
 

[LV-commit] CVS: kernel-2.4/drivers/char dz.c,1.9,1.10

[Dave A. <ai...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/drivers/char
In directory usw-pr-cvs1:/tmp/cvs-serv14245

Modified Files:
	dz.c 
Log Message:
DA: hopefully correct fix for dz rx/tx ints


Index: dz.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/drivers/char/dz.c,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- dz.c	2001/09/21 18:04:53	1.9
+++ dz.c	2001/09/21 20:54:16	1.10
@@ -1472,8 +1472,8 @@
     irq=autoirq_report(0);
      if (num)
       {
-	dz_vsbus_tx_int=num;
-	dz_vsbus_rx_int=num+1;
+	dz_vsbus_rx_int=num;
+	dz_vsbus_tx_int=num+1;
       }
     autoirq_setup(0);
     

[LV-commit] CVS: www/htdocs/download asbl-0.1.tar.gz,NONE,1.1

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/download
In directory usw-pr-cvs1:/tmp/cvs-serv2908

Added Files:
	asbl-0.1.tar.gz 
Log Message:
 add scsi boot loader to downloads dir


--- NEW FILE ---
‹
Ñéˆb©•“$.»âõ<ÎE™c!Íä—QY*¾>9´Ôê¬ÿ|yL|EÍ
m]ÅA$\³°åçy¹ˆBZ:il 
¤´¯h‘É[ᘳ«€Ù/â,í
ì¸Sñs¹X愤˜û…Ò¿´ºv±LnÃ_°Ûè—2¾ò“(-D6Iœd]q^BF´o däó_ßïÂ_
¬’±–¨ÞžZd„º”ÙLúˁe5pÁ¢ËH¦QR1ý}VŠÀ‹sÿ
«2Iìø)ìÀ,÷DX²äK¿.Ü$^Ä¢Á¥Ö­Ë
¯@èã¿ó’Dâ'É­˜ø!þ½–qQ@¼e'q
Rl0Áür<I [ˆ0N¯"˜’¸&¹³lÌ8òS˜Rʼ¹×¦Ý€k_Lã$Ò¶†*ÂÂx:}Ûðg~œæ¬i»·LƳ8õ-./|åEĐ>ƒC­Ó<{Ø ]dRFAÑ
»
eŠ±ãšà¥–‰7´¯…Yeé]-Âܽøþ¢­Yîö*ëk
ï"^,á;ÑüSmÖÞùÿùßKX7řßMã7ò¿ÁöÖ¶Êÿw·ûCÊ{˜ÿ;ÿû+>Œò¼,Å
ùŠò‘,ÏéZâ@&×Ë$L¸T4뺟Ÿ]\ŒØH(Jz°a2N¶õŽ«`\ñÀ$+ìöp¯<ËuÀ£}âÂuýÊÞ΂@tžÇG/^Ÿ~?‹F2³k.Dç[ßëøa:Orã\	Îêά†3 ³Q2%k4#ådܹú~&vщÀ«0e“Ÿƒly+:g»÷‘BvÎE7͐ÌÑã”öu.,*X9>Ä‘8ôo7pÞl¦ä¤ÇÜJL ”ªGB¤¢3mLW©PU_â7:9pÌS«°úœ$‘Ÿ‚#¹ Š›ÿ›•*(¤ÕU¾ÉzX£ø:{HZ\}„í?—a,Eg©C'XòÎ*÷S§^üóÚoÒ7éy¤SaUü°‘—tª#€~œäâMº
vþ¯}ó¯ø¼Gü7ö»i¼;þ†}ªù¹ÿC
Ì~“GÍúþø2Cٗª
WW÷’<ª:U'l\	!3ïÒ,§ô²DÕÉY<Š?Ôs#Bœˆ}KcI†¢U"Ê2–\£ªNA“<Tõã%ÒÿZöµ´?ìÝÔr0
’ºû~û7Ñ·¼ªæt¿Oۂ
Ê<̛’:ŸNKnµŸxrpkóѪNßöÎGî{Û-¹GbÀšL³Yx4»"‚Gdj}žQñ€û¾Hé}‘a³zQ’u×ÈdÂf£¡û즹,H$kº_7§	ÃâÿfÐå{>h*TKj›CäR'J$[åë`wîÂ"F¹|ˆ(Pú°
€ì»kMÀ”ƒñWã4ÔèvXFå‰*Òqõ²5+üÄR†øáQç)´‹üÇW%:È6ו]]63
€¬.(B®$
Y:lg´–^ÎR6˜g¸r4­ö‘¤#w=ã_<¬i½ÄzaM>ñ•éŽÖؕÈÏfFö­¾XU6¶ðkFÁ-B—>Ÿá}®8š™Ü2[Js’YžK‡C?ÉêÚ¿¥D|–Qþ	kbåQ	H¹
£$Zóè¦[}g7…}xê-±²ÐÅÚÔÆ%û„“šCÀôÃÐu †
,žy<ƒ':ÏÜÓÁSƒf¡“iÓÈ$
ۈ2‡œ¹a8!Ój úêäÕóßÿú…Ã]/z¡
ŸÖf‹DâǟFÊÊ9U8&†N•qÛF ³WÛÌ­¶C‹a›ÜÞPõï|—out“
ŠCš*aÕ³4
m.®Nâ1ïÿˆTYõ¡ûVlNªÄH¼úæôôнËÂ&Ê«q]MQÓºÊâ°}èÒäšåbq;£«q‘óË[D„ÔñfÙlbجPW,ÇIbð¸O/"x¡/g§mâùªí²ȾƦï¡LB–Ìûã-Q‹~<
=&K'ü©æãØSN§¶kñ*1ˆJÄäø§ZÃ󸢄oGž’­âAÁXé2ÇK¸öœ€þt¨ë;xŽgÎ>(=¬¬®´E&™ÁÔ‰TƒÉšjŠÅß*vYêþϞ¿šaÞÔUå1™çìÙ%SÔ¡[`÷1aÖöÌ@œ—O[æoÒ
¯2ý¶ÂAåq‹4)>Ã6¬X-ÜP÷ŝ‹~ÀƒÅB`!Z}ƒç­¥¨UCÍ B~õãà'ïl|þüìÕé÷íŠ7¢m ?}E>’2“f•!Ôh:L¦Z=%;08¼ò¢½Šhƒ 6Öãá'6@ì
uÌî·çíʖ\AoÜéZ®µ
*/þë켅“2/È5¬6š?yuwÞ²`ð|0ûmrš:¦Hg)¿²·Ió•@õ¢{ıˆ°ŸVe„^ß-¯‹!&~T+4°áŠK§§²À;`*Ô芆Å4dpW
´«Š°kùØÔ¼ãÓ//.~øüÅk؍uæ6á­«mȂn¼K~5Æ"?;Á¢ã‹¼l<[OÁ
š¬Æ‘è+ÆÔé6º“h¾I$
„4IéK[¨ãc°àV½çIœö*²7ý†@8¾ß㔊pç“Zº%´96
¡<¡¼•Tšë «Ödôó$Å]5`µ²àùÂü~Æ2šø›Ñm“2·?õ!LÕbõ#eú}U\twˆnR]óO[ø‡Å<+© ‡|yÔ⊄9x²0Õ_ù#º2¢ŒÂTa”tי3ˆ|ÐOb¾zDï h·Ôì\T÷•ü€_Å!Á
¯é0µªb©A4RºŒU(¹3t,Õ½3Ґ֍É󡷖ÅÑÓ	2ì§×«ÉÆaFQÑdÒü¥†K
Ô¿»á÷ße­	’,ôi¿š	Ô%!>1͍ZîN-Žè1‚[1ôN€šWúÖÚTú3ú¹
–
~Ɩ|(3«×ëƒñ6D…T[¾ôȧªH—x­Y¡“9íÿdӒ‘ÒgŸBO÷Á
 Gz온U8Án
áA¬ud=½»MÒuη‹ÂÑç+ûL«Ë
X ¹µggdØ03Ìç¨#©Í½es||,Û%ȁf¦¹Ù8RÝéXDžÒ@«>7ì Üá`>šùȐ¤ÎFd®{à0{IߨªB×PîFs‰Ñx-K*ì|òö–hæ,¦í½â;…Ö+̨è:B²ö´	@¾Ø¾äŸ¢0£þ희+ªV)úV}Lj²Ü€.ŒÚ\²ë
±òï“éԈ¹³æˆé¸-X¦`B5¨h*s²
dæ\nnSfå®´w—7-´ç‘…˜ÉiyËè*þ^P±aª*fW{#«¼ÏijÑL)W¡h…<½Ðƒ¼2*X&ýϓ
~öðÉCKÑìtḦ́_ášLüT*T©í"0n©ì˜d®•!V+pDÝÜBòÄÂ}ƒe­b½¸€Îô×¥5ô¿W¼ÿ>Pÿ±>íŸþgtA
üï‚^c÷
*)œÏ'èô³#(ƒ§^¶#¿†¸áŒ›‡lï{Sbk
Îv³Õ[ŠâÆr©=mA»ÙTlVYO&CbÄŸvãi;Œë`œváX	üUêÓ¯SJûóŒ>hxþ3(©‘¶Ä6+*D(׌Æ7Ul6"æŠÑŒÅÉüwÙ¥5åÿ»lÀMì¿æ	À
œý·Ú ÿ·¶
7±ÿ¸ÿ[¾³ÿvBÎþ»ß´‰üok®”ÿ0°å?‚Fàä”íi'Û÷‹6ÿ­mÀ•òï‡ù÷±³ÿvB¯ÀßkZCþ³V÷ÆyùòÄ
Zÿ}a%Fìÿ~¸kù_åßõ‹Êÿ;ÛÙo²òR¡ä%à)iøb£;/
ÁU!𔽫yãÑ5A~”
y¥;>„•Èp0ºòmàõRÆ_a^¼nM¼,õ®SˆvIþ™‰ÏDòäZÁný©¼ț$}
¼Œ[1jҎäù_oÐn™ÇŠù?ò#Úÿ÷#aöE!ìÿˆµÀÍÿ» Œó’ýëõs˜^ìôË\ê~‡”îâ“û8DD}à zÁ]K™‹Cå‘ޟ2¨åÆSw5êÄuÌôΫK˜1Í&D\dt,å;:Ç`¬®œ›ÌøÆ DL¯!¬yd^(d

[LV-commit] CVS: www/htdocs/download dlframe.html,1.2,1.3

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/download
In directory usw-pr-cvs1:/tmp/cvs-serv2702

Modified Files:
	dlframe.html 
Log Message:
 add in some new files


Index: dlframe.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/download/dlframe.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- dlframe.html	2001/09/20 23:35:10	1.2
+++ dlframe.html	2001/09/21 20:12:47	1.3
@@ -26,6 +26,7 @@
 (mopd-linux.tar.gz)</a>
 <li><a href="tools-bin-linuxvax-20001231.tar.bz2">Cross compilation toolset
 for Linux/i386</a> 
+<li><a href="asbl-0.1.tar.gz">Andy's SCSI boot loader</a>
 </ul>
 
 

[LV-commit] CVS: kernel-2.4/drivers/char dz.c,1.8,1.9

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/kernel-2.4/drivers/char
In directory usw-pr-cvs1:/tmp/cvs-serv21685

Modified Files:
	dz.c 
Log Message:
Swap the tx/dx interrupt numbers (hardwired section only) to make things
work proper like.


Index: dz.c
===================================================================
RCS file: /cvsroot/linux-vax/kernel-2.4/drivers/char/dz.c,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- dz.c	2001/09/16 15:13:09	1.8
+++ dz.c	2001/09/21 18:04:53	1.9
@@ -1492,12 +1492,12 @@
   }
 #else    
 if (is_ka46()){
-  dz_vsbus_tx_int=4;
-  dz_vsbus_rx_int=5;
+  dz_vsbus_tx_int=5;
+  dz_vsbus_rx_int=4;
   irq=149;
 } else {
-  dz_vsbus_tx_int=6;
-  dz_vsbus_rx_int=7;
+  dz_vsbus_tx_int=7;
+  dz_vsbus_rx_int=6;
   irq=177;
 }
 #endif

[LV-commit] CVS: www/htdocs/download tools-bin-linuxvax-20001231.tar.bz2,NONE,1.1

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/download
In directory usw-pr-cvs1:/tmp/cvs-serv896

Added Files:
	tools-bin-linuxvax-20001231.tar.bz2 
Log Message:
add the precompiled tools cross kit to the download dir


--- NEW FILE ---
BZh91AY&SYƒK{ÚÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿåÔÏcêzû\h(£ª
ß4í€]Û½j€”öÀÑGyáO¼	

)xîÝ6iuc¥¶ìß09–e@327{@EÇNÇ:è\îÓAXcÛ®gÝÐ=ïOe¾÷ݞٟà¹mǟ>ùà=w/»Ý¹¾Þ:íëÖ½»Råïo<ôïx´²T
j³ß{6ø-tlù¹íïM³ëݯ}÷»·H<t¹îxç­ö}|¼	ëë}{q‡±^ùàÝ}÷]Ý}¾a`]ßUßwCÞûÞö>›àtãŦí™(!P{ŠwŸ|<°WØú>š¾î>%±|÷vƒ<âÃ
{¹ÙÝÙs*”=4ûÇr”¡:kã×½ßO{»ïW¯½å­U¸Ü]Έa¸\µèò«¼sàZ8ÕѶwh«OØûïpî{ç»Ó¾îøt
‘+¾÷o·ÔÛ·¸fIÆÔ+A“Xï{v^
×6J—½Ý±éÇ®6wÜÝê´¤{«ª6z;´|u}m¢´Ü<úúÓK°+NíE

gÛWNìР(
ÌȬÐecïUË´•G­´èçÓ'Ù§ËIZkíäAJ”»__}ôq£ì=ÓOªÚlßn®ÝÇNPgÛæx÷^ã¹UW­æƒUdi³_pÈ݇+Û^ÙOµÍsT’ÛÝÄn[SÙ¢võ'¯5îᢥßwÇ×ÃèûÞ¾÷ÀUÙÑÉM±öûÞ—“]ôøÕkÞë¸ÞûØ:ë–ùÙÅ©k±9ݍ>ﯧf<®˜’¥c}ñó½¾úáӏ.Žj=JhÈ7Ç\ÍÇ]¾æ…vÚ¨ûeîûèùäºÁ÷F­¨øóÛ5m
÷nó;Û_-!Öꗩš#ƒÈ,]p£u…}‰÷(_×o¹í¸.¥îî•ãæO}ޞºZU·×WÇ6ûáÕòûì3·‡Ù|¾B!Iáä,b¼<ä.u½¹±aÎ;2Sˆ¯^ë‡R÷£
M
½9$)¡¥
iÓB€$¢•­
*J¡ïŽÃ	7Ì{êàðc×6>û¼ÛÞ¶Ï
Ž«†2Z̲ÌM‚Òzæ"¨¦aˆ0ŠÊ³ä»ÀÍŝo,Ì1Š6péY܋ä_¥-VnLüVv«,½Îäa_Ù¢oß磛K×r®·Ÿ˜Nՙ¨Ý+ÌqZâتë0JyùÆ8ôh%–ÇMšÏÛëFDE¹L,/„ˆᘸ1¥8­ i)¦ÍÝ`Î3Éqƒ"L§Ù¥ê­ÎJ“Å,RÆ=®6ö¹È@†jæŽM	¯ŠšòdJS`~ª”	oË°’ V\ÚñKq¯CLÖ]!cg.l¾>´œ²j$²0ŒŒôB’«æi«»#W°Y¤.Re™ao£!‡Ƒj¦F<Þ¡a±ÏºÚØÁ¤P6Ì-	9˜=Z…QŒ8ôA#„oæÉe|k®åз${æÞcBX^&>Ë©1|õó &^ÌŠÊ¡ìÇÐK)”ð7„ÉœC^/+æ(f¶r)k¹ž½eݧ|Ž¦í¼ÅÙXstRIotIˆ  ,hhŠÛ-±`ÝÞpC¿+%”ïª0š`Ó"ZŒÁ$Úö;`n㹍ȋݍ#p;
„߈ë¬MžF€˜7¶	k3²4ªôÍ`èÆ'sÙ½;Yg$°uY]"ñHȓhÒj
ìÛ2¨»OvZ jàž_E­ZH8+Wc*¨#˜úZD6ɉ2)mn˜ZúìZm`Ë´Ïãzªa«kg|‚+ãßÍw›Už—߶û7óÈ&Ÿ[ò6¸Ëi(QDV*°ˆ'ÈŸkÚù?¦ÜÞõÑ4{¢Àö÷Í4	ƒ^?¹™×P}º=äÃhs‘S!Ï­C;îpL†7ï܍_m=+6hjÁeC'áb7zmD±ƒ:΢b1ÄJ££÷6péN¼{·n¶áw·éì½°fí¢E°H¤!¯¼,˜È(‰
,HV°‚Š
Y'°À$2wøt1Õì>ï˜*
.ÈÑ[*Wn¸5]Ÿa2%é=ow H "*€ª)"ÏjùŸ£ín
ÄNß®øȆï®ÇÇz\÷½l"*ÔTAEQ‘T‘©SEõë*ð0‚«"	"*€Õ(-AUZ‚ŠŠgD,UAQˆÅDÏé<G­P[¾ï®Jኾ×$ÞÀUm¯Uºñû›/vp5{Yòý4i+_…„eՏlËZ^é‰~§Yù¿em‹ó"é3ûYûìò?’꽧œ³›¡Ñ~?8$?2mCæ;Ö§°³í,eºý˜o­»ðZççîvp<\׆÷PæP¯ý#Ž3I"%þ‚Áê4ü\*,og¿*n*÷€Iò…T	,“Žì€·fÖS
FÚªf?O…LÆLɕv;CØðÝ #ñ¯cn,}ãÙÛÙdXÞ7Écò¸?Þ÷?9æÑ8
ðlµ°Fë«8pF‹ùî$``68lÒšÑ0~q^Ù¸®E¶ÿCÚ«œÐzk;Ÿ{™ºÆ+×"
ƒ1cñeug¹Ô:ªÑÒQ3{¥&_à?ü|ϕ`ÿtC_èÅî#
ƒù.ï™ë¡Ÿï•vA_Ñúµ1_b°l¶£÷óÉbì_ç_oîù>=œ÷EÞª2Ö»ÞÉý[cÿïñ^Â^R·”ãLb üðÐ)½Y¡$éNÁ¥éÈÀÍ
þ©‹HI‚—"1 :§K·tÝX.‰˜\7 
ñ¶¶«po5ÌÚyzðÌÍ桇îp9„![µÏíÿt³ÄfVhTs;‹ºN­J»ÞcX"˜ïÕy3|ˆ%Øx8Þ:ŒH(ìü¤šXWc”2–©Ù4ƌµ%ÿñÃޙ
lÊtik‹—)•’Iåà–奍}Jù>ÐîRˈ„q
Gõ=V­:ÜfcPf…è%W,sÃVZª¡Ì»Æs
[...29331 lines suppressed...]
P¹í”âߒ¦IRxG=µ¶wÉö{yæÐýí̲ÅSĝ°#〉±:~u
dHÁ,**ñDadï@#j]ÝþÃ#G‰
f
]!£@Ô!»V@ ÍTðj¨:xˆjÄ µŅR‰!´
,Á¸Õ
Œaì;«¤R”-dƚYŽA" a€ÙŠ"©"q>›×;=&eÖg;ö	V'C,!úñ^‘²Þ0áõÅ
Ûv9¶ÑÅcG°mú^gìîxøµàbä²0^8'Csƒ(ÀÖë’2BvÆMdä
K$CRö¨yKyKHIl‡EÓõ
䨀Ø!å	Kz`-9Ýȏ$Âi^Q€º‰Þ
¤;㔴Ѩ=Kì#èø
­µR>
=JE˜Ã&	ɂr=äüˆØMKÄџn¸ö8_¢yÏ3ê]ÁÒý»7ÎÈwË>’ˆœ¿*¼J¨jDrÝüPAȪ‡ƒÀ,Ðü€vá,¨Îyz
OóOÔ@?‘Þ<Fn— ÉIZÜÈan[†C1 AÜnT»ÇÃÄ6M+Á­SRÕlsÝ^Iþƒ‡ÚÒV¡7Ôç¯Ä}
`Š	—aÜN¸=ďöÈÒ§‡,dÃGš{3È>!ôíäŽĊA9dH…I‘#uí1
ßÑ8Äl>½ƒùc*aEW¿öøê
ù—/dú¿SÉÁåW-ó”ýD|ó⣠{ÃáD'»àp§¶Plg…µââÔя¨!ö0'#dú‰÷üÄ°6¿)yº‰2
‘ˆ5VüaÔ4HP-54­1E5%4D•E,Hf5­Q5¶DÒfˆŠ˜¥he) 6HÂ*µU’2>aÐÅÞ!y€£æõ‚”©J±*{ÈL…(DÌ0i8%猏Rˆªû’¸RŠÙèRN„9ù.õaÄ
d©‡Z'²§òÿ÷ÿùP|¿áÿ×ùþÿþÝïÛÿ×Å·ê¿íúrÖS˜'?À‚=Á|¾'
‘HPRfi¤/6(Äá¢{%&ÖXP'‡Ì۞?2o§<¾Giø)ÂÙ(¶‰R¥þl¸Z[¶Ê·ø(W
c‚ ƒÂqK]Øæ+cDL‰Î·yeŸ0ÑÝ7’pk¤:º¢í¸ìul	i›±Žuµ0±ÑÝÄëFÖ&3
:qy&»Ã»ºLrãbsQ8-#bŠ™t¡öºŠV‚€ Iª0ŸóWôîu²—
¤i
)_Âü9¿	/§<@@Zpu¡r$¥2O¬,éÀ­üÜø¢‘H!æÎØVO•¸ìfê…Ev_Í:9Ø4L»×œÕÈ‹&é݆í×Z© ÷i†
|j“Z"·s ÎqâìY(6صÂÜi–-ËżrE?ÀÂÅ9´a°
Dêß6¨:ÝI£sBa¤"$;
„X/gˆ>›D”LLLD‡Ñ 0@¢B½_ðÌsy&!1t¡-Xâñ§:r‘ì€~ÐòýDòϒ£Ú‹¼ä…ö:)ñ#ðXÆJé5A–ӁüþwË#ú *
)¢Ÿ¡hI’’í;ü•Ðžyî€øG˜
·ˆ(C¨{\	àwJ˜t¥
æCëë²H±#AAM”A÷ÞÃJ~ï¸CÍÜ4hV†‘<Ð´Ñ]ć£¡¤ 
aR)‰FÃBÿrÏf_’  y‘KÑÏE7¹?ÚÃñ+ì/»	Nµ@4ÓSKHDD-'o÷ó^‚uøQ†è8—Ùʤé¥MÝ
ÑÒ
ˆM âA¤¡ª”ÐhA G¤Òüi‘¼ØšCm@P5ï ¾€J'Xÿ< P#‰(åþRÑþ?½Œ{3ÒÜ5”=,¨z¡í„(6‡ÂDԈjˆšƒÀú³;ì:ºÌ@ç+Ã
4©0T¤Paùô&Uن#œ™!@%P9·þ1ß´wû½¿`m«òA@‚?jŒš ¦OãGò~×{Úî&¢{¬/]Þ¨L†Ç«µ½w©«+[Ë¢dÙ-,L)Ò¡³$Ý8f\Έ$SI.¦óu
´h€’SÎ
.$ln¹Là’°H¡A]&Ž¹"N¤;õNÃáÃ-½u×–:þ½³³
誂ʤ«™Ù<÷×0îà/]
¡CìÁI™–!˜CɚŠÇ’ˤ™8e+9S)XnXvI$³®i±Ðá™+s;õäªôP©ržŽK¯9CµU
Ò)²Cj
Çð횧5§jV­b.Uµˆ°qÈdÛøö]o&Xœnë13¾¶R‡´´ˆVÔµK2#åo{]V^n\ •½³Ø÷1¢ŒàrŠús^1
q_š&÷uBµ$‚žfð;Õ<ÙÝð…¥Üq^;¸zœNqb€°fñ›“œç”=9ÏZi=‹t¿aßL¾M<¾ÿ§ØóÁŸKã¾îfAfHä‚
8ÆæQõOMæq´ªÒâr…ÂòÕ]¶k
•¸àä;é¹3Ææðª¹ÕÌv”Q-ÁURª—2ù¶&[cD1£ÄÄo–'7rg:·-eE¥ن›m•[æiÊË_aúÆzšiÚu˜xg‡ØóÒӆû´öpy=døÒŠiêN0zOC¾\ºLTÛ¨¡
<Ãâz‰_íR†PRI$ 
¬@gö@þ„©ÉÐÉ
ʲÓKÁÛÄð€("OÆ@2(Z(‘ h) †š
‚ ZV’…ª¥
(Pd"׈||„æ’
Jª>´Ò@8<ª¨¤ªC óìhûßt_åúTMH¡Îhý©

[LV-commit] CVS: www/htdocs/download dlframe.html,1.1,1.2

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/download
In directory usw-pr-cvs1:/tmp/cvs-serv30641/download

Modified Files:
	dlframe.html 
Log Message:
Update faq with CVs page details


Index: dlframe.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/download/dlframe.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dlframe.html	2001/09/19 15:59:22	1.1
+++ dlframe.html	2001/09/20 23:35:10	1.2
@@ -4,12 +4,29 @@
 <h1>Downloads</h1>
 
 Snapshots and binaries. These may be out of date, and if possible you 
-are advised to get the source direct from the CVS server. <p>
+are advised to get the source direct from the CVS server to be sure 
+that you are getting the most up to date version. We haven't really
+released any formal packages as yet but these will get you in the game.<p>
+
+<h2>CVS</h2>
+
+Our <a href="https://www.sourceforge.net/cvs/?group_id=2626/">CVS page at
+sourceforge</a> holds information on how to get up and running with the 
+CVS modules (See the <a href="../newfaq/newfaq.html">FAQ</a> for details on
+the different modules in CVS). You can also browse the CVS using the 
+<a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/linux-vax/">web based 
+viewer</a>. 
+<p>
+<h2>HTTP downloads</h2>
+
+The FTP service hosted by sourceforge has been retired. Packages are 
+now being made available only via HTTP.<p>
 <ul>
 <li><a href="mopd-linux.tar.gz">Maintenance Operations Protocol Daemon
 (mopd-linux.tar.gz)</a>
+<li><a href="tools-bin-linuxvax-20001231.tar.bz2">Cross compilation toolset
+for Linux/i386</a> 
 </ul>
-
 
 
 <SCRIPT>

[LV-commit] CVS: www/htdocs/newfaq linux_vax-2.html,1.1,1.2 linux_vax-2.html.old,1.1,1.2 linux_vax.sgml,1.1,1.2

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/newfaq
In directory usw-pr-cvs1:/tmp/cvs-serv30641/newfaq

Modified Files:
	linux_vax-2.html linux_vax-2.html.old linux_vax.sgml 
Log Message:
Update faq with CVs page details


Index: linux_vax-2.html
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-2.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux_vax-2.html	2001/09/19 17:41:35	1.1
+++ linux_vax-2.html	2001/09/20 23:35:10	1.2
@@ -119,7 +119,8 @@
 to glibc soon, but at the moment, this is the libc we use. </LI>
 <LI> usr - various useful programs, busybox, mopd, asbl..</LI>
 </UL>
-<P>Access to CVS is via the standard sourceforge method. 
+<P>Access to CVS is via the standard sourceforge method. See our 
+<A HREF="http://www.sourceforge.net/cvs/?group_id=2626/">project cvs page</A> for details on that. 
 <P>
 <H3>Can I get write access?</H3>
 

Index: linux_vax-2.html.old
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax-2.html.old,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux_vax-2.html.old	2001/09/19 17:41:35	1.1
+++ linux_vax-2.html.old	2001/09/20 23:35:10	1.2
@@ -119,7 +119,8 @@
 to glibc soon, but at the moment, this is the libc we use. </LI>
 <LI> usr - various useful programs, busybox, mopd, asbl..</LI>
 </UL>
-<P>Access to CVS is via the standard sourceforge method. 
+<P>Access to CVS is via the standard sourceforge method. See our 
+<A HREF="http://www.sourceforge.net/cvs/?group_id=2626/">project cvs page</A> for details on that. 
 <P>
 <H3>Can I get write access?</H3>
 

Index: linux_vax.sgml
===================================================================
RCS file: /cvsroot/linux-vax/www/htdocs/newfaq/linux_vax.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- linux_vax.sgml	2001/09/19 17:41:35	1.1
+++ linux_vax.sgml	2001/09/20 23:35:10	1.2
@@ -187,7 +187,9 @@
  <item> usr - various useful programs, busybox, mopd, asbl..
  </itemize>
  <p>
- Access to CVS is via the standard sourceforge method. 
+ Access to CVS is via the standard sourceforge method. See our <htmlurl
+url="http://www.sourceforge.net/cvs/?group_id=2626/" name="project cvs
+page"> for details on that. 
  
  <sect2>Can I get write access?<p>
  

[LV-commit] CVS: www/htdocs/newfaq fix_html,NONE,1.1 linux_vax-1.html,NONE,1.1 linux_vax-1.html.old,NONE,1.1 linux_vax-2.html,NONE,1.1 linux_vax-2.html.old,NONE,1.1 linux_vax-3.html,NONE,1.1 linux_vax-3.html.old,NONE,1.1 linux_vax-4.html,NONE,1.1 linux_vax-4.html.old,NONE,1.1 linux_vax.html,NONE,1.1 linux_vax.html.old,NONE,1.1 linux_vax.sgml,NONE,1.1 newfaq.html,NONE,1.1 newfaq.html.old,NONE,1.1

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/newfaq
In directory usw-pr-cvs1:/tmp/cvs-serv22512/newfaq

Added Files:
	fix_html linux_vax-1.html linux_vax-1.html.old 
	linux_vax-2.html linux_vax-2.html.old linux_vax-3.html 
	linux_vax-3.html.old linux_vax-4.html linux_vax-4.html.old 
	linux_vax.html linux_vax.html.old linux_vax.sgml newfaq.html 
	newfaq.html.old 
Log Message:
Final part of website update


--- NEW FILE ---
#!/bin/sh
# I cant see a way of imposing our style on sgml2html generated output
# and to be perfectly honest, I cant be bothered wasting time learning
# Yet Another Typesetting Language, to warp it into doing the most basic
# formatting possible (White background, black text please). I know basic
# HTML and LaTeX and dislike both, despite having written a book in the 
# latter. 
# 
# Hence this file.
# 
sgml2html linux_vax.sgml
for i in *.html
do 
echo zapping body tag in $i
mv -f ${i} ${i}.old
sed -e 's/\<BODY\>/\<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica"\>/' ${i}.old > ${i}
done

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: General Info</TITLE>
 <LINK HREF="linux_vax-2.html" REL=next>

 <LINK HREF="linux_vax.html#toc1" REL=contents>
</HEAD>
<<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
<A HREF="linux_vax-2.html">Next</A>
Previous
<A HREF="linux_vax.html#toc1">Contents</A>
<HR>
<H2><A NAME="s1">1. General Info</A></H2>

<P>
<A NAME="geninfo"></A> <H2><A NAME="ss1.1">1.1 Whats a VAX?</A>
</H2>

<P>
<P>VAXes were 32-bit computer systems from Digital Equipment Corporation
(or DEC). They enjoyed huge popularity throughout the 1980's and early 
1990's. The VAX was the 32 bit computer that
the ancestors of  modern UNIXes were made on, and was the standard computer
architecture (like the IBM PC is now) of its day. The VAX was also one of the
major testbeds for the early Internet.
<P>
<P>VAXes come in several shapes and sizes, ranging from the small room sized
VAX 11/780 (1970's) through to the desktop sized microVAXes and VAXStations
of the 1990's. The VAX architecture and Digital's VAX/VMS operating system 
are mutually intertwined, so for a review of VAXes see
<P>
<A HREF="http://www.vaxarchive.org/">The VAX Archive</A><P>
<A HREF="http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf">VMS 20th  anniversary special</A><P>
<H2><A NAME="ss1.2">1.2 Is that the same as a DECstation?</A>
</H2>

<P>
<P>No. The DECstations use the MIPS processor, and have names like 
<UL>
<LI>DECstation 5000/200</LI>
<LI>DECstation 5000/240</LI>
<LI>Personal DECstation</LI>
</UL>
<P>These use the R3000 or similar MIPS CPU. Many of the peripherals are similar
to those found in later model VAXstations, but they are not the same.
<P>These were a stopgap for a few years while DEC developed what would become 
the Alpha processor. I've got one, but I'm not an expert on them, so please
don't ask us questions about them.
<P>
<P>The DECstations ran ULTRIX/Mips as the only offering from DEC. They never
ran VMS. If you have one of these, you can also run;
<UL>
<LI>
<A HREF="http://decstation.unix-ag.org/">Linux/MIPS for DECstations</A></LI>
<LI>
<A HREF="http://www.netbsd.org/">NetBSD/pmax</A></LI>
</UL>
<P>
<H2><A NAME="ss1.3">1.3 What Operating Systems/Software runs on a VAX?</A>
</H2>

<P>
<P>The following Operating Systems run on a VAX;
<UL>
<LI>
<A HREF="http://www.openvms.compaq.com">Compaq OpenVMS/VAX</A></LI>
<LI>Compaq ULTRIX/VAX</LI>
<LI>
<A HREF="http://www.netbsd.org">NetBSD/VAX</A></LI>
<LI>
<A HREF="http://www.linux-vax.org">Linux/VAX</A></LI>
</UL>
<P>
<H2><A NAME="ss1.4">1.4 Where do I buy one?</A>
</H2>

<P>
<P>The VAX system line has been discontinued, so DEC, now owned by Compaq,
no longer sell them. However, occasionally systems
for sale do come up on EBay and other on line auction houses. Also look out
for companies "upgrading" their VAXes to something more newfangled.
Occasionally port-vax (The NetBSD mailing list) or linux-vax (our mailing
list) will have notices of VAXes up for grabs.
<P>
<H2><A NAME="ss1.5">1.5 Whats the difference between a VAXserver and a VAXstation?</A>
</H2>

<P>
<P>Practically speaking, for the 3100 series, a keyboard, a mouse, a monitor,
and the little switch in the back in the other position. VAXstations were 
designed for graphical work, and tended to come with better graphics cards.
VAXservers just sat there, and used a terminal as the console. 
<P>
<P>For more information about such details see, for example,
<A HREF="http://www.vaxarchive.org">The VAX archive</A><P>
<HR>
<A HREF="linux_vax-2.html">Next</A>
Previous
<A HREF="linux_vax.html#toc1">Contents</A>
</<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: General Info</TITLE>
 <LINK HREF="linux_vax-2.html" REL=next>

 <LINK HREF="linux_vax.html#toc1" REL=contents>
</HEAD>
<BODY>
<A HREF="linux_vax-2.html">Next</A>
Previous
<A HREF="linux_vax.html#toc1">Contents</A>
<HR>
<H2><A NAME="s1">1. General Info</A></H2>

<P>
<A NAME="geninfo"></A> <H2><A NAME="ss1.1">1.1 Whats a VAX?</A>
</H2>

<P>
<P>VAXes were 32-bit computer systems from Digital Equipment Corporation
(or DEC). They enjoyed huge popularity throughout the 1980's and early 
1990's. The VAX was the 32 bit computer that
the ancestors of  modern UNIXes were made on, and was the standard computer
architecture (like the IBM PC is now) of its day. The VAX was also one of the
major testbeds for the early Internet.
<P>
<P>VAXes come in several shapes and sizes, ranging from the small room sized
VAX 11/780 (1970's) through to the desktop sized microVAXes and VAXStations
of the 1990's. The VAX architecture and Digital's VAX/VMS operating system 
are mutually intertwined, so for a review of VAXes see
<P>
<A HREF="http://www.vaxarchive.org/">The VAX Archive</A><P>
<A HREF="http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf">VMS 20th  anniversary special</A><P>
<H2><A NAME="ss1.2">1.2 Is that the same as a DECstation?</A>
</H2>

<P>
<P>No. The DECstations use the MIPS processor, and have names like 
<UL>
<LI>DECstation 5000/200</LI>
<LI>DECstation 5000/240</LI>
<LI>Personal DECstation</LI>
</UL>
<P>These use the R3000 or similar MIPS CPU. Many of the peripherals are similar
to those found in later model VAXstations, but they are not the same.
<P>These were a stopgap for a few years while DEC developed what would become 
the Alpha processor. I've got one, but I'm not an expert on them, so please
don't ask us questions about them.
<P>
<P>The DECstations ran ULTRIX/Mips as the only offering from DEC. They never
ran VMS. If you have one of these, you can also run;
<UL>
<LI>
<A HREF="http://decstation.unix-ag.org/">Linux/MIPS for DECstations</A></LI>
<LI>
<A HREF="http://www.netbsd.org/">NetBSD/pmax</A></LI>
</UL>
<P>
<H2><A NAME="ss1.3">1.3 What Operating Systems/Software runs on a VAX?</A>
</H2>

<P>
<P>The following Operating Systems run on a VAX;
<UL>
<LI>
<A HREF="http://www.openvms.compaq.com">Compaq OpenVMS/VAX</A></LI>
<LI>Compaq ULTRIX/VAX</LI>
<LI>
<A HREF="http://www.netbsd.org">NetBSD/VAX</A></LI>
<LI>
<A HREF="http://www.linux-vax.org">Linux/VAX</A></LI>
</UL>
<P>
<H2><A NAME="ss1.4">1.4 Where do I buy one?</A>
</H2>

<P>
<P>The VAX system line has been discontinued, so DEC, now owned by Compaq,
no longer sell them. However, occasionally systems
for sale do come up on EBay and other on line auction houses. Also look out
for companies "upgrading" their VAXes to something more newfangled.
Occasionally port-vax (The NetBSD mailing list) or linux-vax (our mailing
list) will have notices of VAXes up for grabs.
<P>
<H2><A NAME="ss1.5">1.5 Whats the difference between a VAXserver and a VAXstation?</A>
</H2>

<P>
<P>Practically speaking, for the 3100 series, a keyboard, a mouse, a monitor,
and the little switch in the back in the other position. VAXstations were 
designed for graphical work, and tended to come with better graphics cards.
VAXservers just sat there, and used a terminal as the console. 
<P>
<P>For more information about such details see, for example,
<A HREF="http://www.vaxarchive.org">The VAX archive</A><P>
<HR>
<A HREF="linux_vax-2.html">Next</A>
Previous
<A HREF="linux_vax.html#toc1">Contents</A>
</BODY>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: General Info about the port</TITLE>
 <LINK HREF="linux_vax-3.html" REL=next>
 <LINK HREF="linux_vax-1.html" REL=previous>
 <LINK HREF="linux_vax.html#toc2" REL=contents>
</HEAD>
<<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
<A HREF="linux_vax-3.html">Next</A>
<A HREF="linux_vax-1.html">Previous</A>
<A HREF="linux_vax.html#toc2">Contents</A>
<HR>
<H2><A NAME="s2">2. General Info about the port</A></H2>

<H2><A NAME="ss2.1">2.1 What is the current status? </A>
</H2>

<P> 
<A NAME="status"></A> <P>
<H3>Kernel</H3>

<P>
<A NAME="kernelstat"></A> <P>The kernel boots and works, in a somewhat basic fashion, on a subset of
VAX systems.
<P>
<P>We currently know that we boot to shell on the following VAXen:
<UL>
<LI>VAXstation 3100m30 (KA42 CPU)</LI>
<LI>VAXstation 3100m38 (KA42 CPU)</LI>
<LI>VAXstation 3100m76 (KA43 CPU)</LI>
<LI>VAXstation 4000/60 (KA46 CPU)</LI>
</UL>
<P>We have, in the past, at least partially booted on the following:
<UL>
<LI>VAXstation 3500 (KA650 CPU)</LI>
<LI>VAXstation II/GPX (KA630 CPU)</LI>
<LI>MicroVAX 3400 (KA640 CPU)</LI>
<LI>VAXserver 4000-200 (KA660 CPU)</LI>
<LI>VAXstation 3100m85 (KA55 CPU)</LI>
</UL>
<P>We have drivers for the console, ethernet and SCSI on the;
<UL>
<LI>VAXstation 3100m76 (KA43 CPU)</LI>
<LI>VAXstation 3100m38 (KA42 CPU)</LI>
<LI>VAXstation 4000/60 (KA46 CPU) (not SCSI yet)</LI>
</UL>

and works in progress for the SCSI and ethernet on the
<UL>
<LI>VAXstation 4000/60 (KA46 CPU)</LI>
<LI>VAXstation 3100m85 (KA55 CPU)</LI>
</UL>
<P>So at present, if you want the most complete Linux/VAX experience,
get hold of a VAXStation 3100m30/38 or 76.
<P>
<H3>Compilers, binutils, etc...</H3>

<P>
<P>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).
<P>
<H2><A NAME="ss2.2">2.2 What do I need to help? </A>
</H2>

<P> 
<A NAME="help"></A> <P>
<P>A VAX, an unix system, (preferably Linux/i386 box), a terminal
or terminal emulator like minicom, and a network or shared SCSI
disk.
<P>
<P>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.
<P>
<P>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 
<A HREF="http://www.openvms.digital.com/wizard/openvms_faq.html#MISC1">OpenVMS FAQ</A>
for details of pinouts.
<P>In order to get the kernel image over to the VAX in order to boot it,
you've got two options: MOP or SCSI.
<P>
<UL>
<LI>Put your PC and VAX on the same ethernet segment.  Install mopd
(Maintainence Operations Protocol Daemon) on the PC.  Point mopd
at the vmlinux.SYS image and tell your VAX to boot from the 
network (usually BOOT XQA0 or BOOT ESA0)</LI>
<LI>Put a SCSI card with an external SCSI connector into your PC.
Connect your VAXstation, a hard disk and your PC together on
one SCSI chain.  Then dd the vmlinux.dsk image to the disk and
tell the VAX to boot from that disk.</LI>
</UL>
<P>
<H2><A NAME="ss2.3">2.3 Explain your CVS setup.</A>
</H2>

<P>
<P>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.
<P>The main modules are;
<UL>
<LI> kernel - The 2.2/2.3 series kernel. Dont use it....</LI>
<LI> kernel-2.4 - The current 2.4 series kernel. This is the one that 
we are actively working on.</LI>
<LI> tools - This is the toolchain. If you download this via cvs, just use
the ./build-vax.sh script to build a cross compilation environment for 
Linux/VAX (tested on Linux/i386 and Linux/MIPS only AFAIK, but should
work on other unixes).</LI>
<LI> uClibc - The micro libc from lineo. We're concentrating on moving
to glibc soon, but at the moment, this is the libc we use. </LI>
<LI> usr - various useful programs, busybox, mopd, asbl..</LI>
</UL>
<P>Access to CVS is via the standard sourceforge method. 
<P>
<H3>Can I get write access?</H3>

<P>
<P>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.
<P>
<P>
<H3>I dont want to got through all of that, what now?</H3>

<P>
<P>Send the patch, and one of us will apply it. 
<P>
<H2><A NAME="ss2.4">2.4 I have a mumbleVAX, is it supported?</A>
</H2>

<P>
<P>See section 
<A HREF="#kernelstat">Kernel</A> 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 <CODE>cpu_xxx.c</CODE>
files in the <CODE>arch/vax/kernel</CODE> directory to get an idea of what you
need to implement for a machine vector. 
<P>   
<P>
<H2><A NAME="ss2.5">2.5 How do I get started? </A>
</H2>

<P> 
<A NAME="started"></A> 
Read Documentation/vax/README at 
<A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax</A>. 
This describes howto download the compiler and kernel, and set up the MOP boot.
<P>
<HR>
<A HREF="linux_vax-3.html">Next</A>
<A HREF="linux_vax-1.html">Previous</A>
<A HREF="linux_vax.html#toc2">Contents</A>
</<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: General Info about the port</TITLE>
 <LINK HREF="linux_vax-3.html" REL=next>
 <LINK HREF="linux_vax-1.html" REL=previous>
 <LINK HREF="linux_vax.html#toc2" REL=contents>
</HEAD>
<BODY>
<A HREF="linux_vax-3.html">Next</A>
<A HREF="linux_vax-1.html">Previous</A>
<A HREF="linux_vax.html#toc2">Contents</A>
<HR>
<H2><A NAME="s2">2. General Info about the port</A></H2>

<H2><A NAME="ss2.1">2.1 What is the current status? </A>
</H2>

<P> 
<A NAME="status"></A> <P>
<H3>Kernel</H3>

<P>
<A NAME="kernelstat"></A> <P>The kernel boots and works, in a somewhat basic fashion, on a subset of
VAX systems.
<P>
<P>We currently know that we boot to shell on the following VAXen:
<UL>
<LI>VAXstation 3100m30 (KA42 CPU)</LI>
<LI>VAXstation 3100m38 (KA42 CPU)</LI>
<LI>VAXstation 3100m76 (KA43 CPU)</LI>
<LI>VAXstation 4000/60 (KA46 CPU)</LI>
</UL>
<P>We have, in the past, at least partially booted on the following:
<UL>
<LI>VAXstation 3500 (KA650 CPU)</LI>
<LI>VAXstation II/GPX (KA630 CPU)</LI>
<LI>MicroVAX 3400 (KA640 CPU)</LI>
<LI>VAXserver 4000-200 (KA660 CPU)</LI>
<LI>VAXstation 3100m85 (KA55 CPU)</LI>
</UL>
<P>We have drivers for the console, ethernet and SCSI on the;
<UL>
<LI>VAXstation 3100m76 (KA43 CPU)</LI>
<LI>VAXstation 3100m38 (KA42 CPU)</LI>
<LI>VAXstation 4000/60 (KA46 CPU) (not SCSI yet)</LI>
</UL>

and works in progress for the SCSI and ethernet on the
<UL>
<LI>VAXstation 4000/60 (KA46 CPU)</LI>
<LI>VAXstation 3100m85 (KA55 CPU)</LI>
</UL>
<P>So at present, if you want the most complete Linux/VAX experience,
get hold of a VAXStation 3100m30/38 or 76.
<P>
<H3>Compilers, binutils, etc...</H3>

<P>
<P>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).
<P>
<H2><A NAME="ss2.2">2.2 What do I need to help? </A>
</H2>

<P> 
<A NAME="help"></A> <P>
<P>A VAX, an unix system, (preferably Linux/i386 box), a terminal
or terminal emulator like minicom, and a network or shared SCSI
disk.
<P>
<P>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.
<P>
<P>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 
<A HREF="http://www.openvms.digital.com/wizard/openvms_faq.html#MISC1">OpenVMS FAQ</A>
for details of pinouts.
<P>In order to get the kernel image over to the VAX in order to boot it,
you've got two options: MOP or SCSI.
<P>
<UL>
<LI>Put your PC and VAX on the same ethernet segment.  Install mopd
(Maintainence Operations Protocol Daemon) on the PC.  Point mopd
at the vmlinux.SYS image and tell your VAX to boot from the 
network (usually BOOT XQA0 or BOOT ESA0)</LI>
<LI>Put a SCSI card with an external SCSI connector into your PC.
Connect your VAXstation, a hard disk and your PC together on
one SCSI chain.  Then dd the vmlinux.dsk image to the disk and
tell the VAX to boot from that disk.</LI>
</UL>
<P>
<H2><A NAME="ss2.3">2.3 Explain your CVS setup.</A>
</H2>

<P>
<P>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.
<P>The main modules are;
<UL>
<LI> kernel - The 2.2/2.3 series kernel. Dont use it....</LI>
<LI> kernel-2.4 - The current 2.4 series kernel. This is the one that 
we are actively working on.</LI>
<LI> tools - This is the toolchain. If you download this via cvs, just use
the ./build-vax.sh script to build a cross compilation environment for 
Linux/VAX (tested on Linux/i386 and Linux/MIPS only AFAIK, but should
work on other unixes).</LI>
<LI> uClibc - The micro libc from lineo. We're concentrating on moving
to glibc soon, but at the moment, this is the libc we use. </LI>
<LI> usr - various useful programs, busybox, mopd, asbl..</LI>
</UL>
<P>Access to CVS is via the standard sourceforge method. 
<P>
<H3>Can I get write access?</H3>

<P>
<P>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.
<P>
<P>
<H3>I dont want to got through all of that, what now?</H3>

<P>
<P>Send the patch, and one of us will apply it. 
<P>
<H2><A NAME="ss2.4">2.4 I have a mumbleVAX, is it supported?</A>
</H2>

<P>
<P>See section 
<A HREF="#kernelstat">Kernel</A> 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 <CODE>cpu_xxx.c</CODE>
files in the <CODE>arch/vax/kernel</CODE> directory to get an idea of what you
need to implement for a machine vector. 
<P>   
<P>
<H2><A NAME="ss2.5">2.5 How do I get started? </A>
</H2>

<P> 
<A NAME="started"></A> 
Read Documentation/vax/README at 
<A HREF="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax</A>. 
This describes howto download the compiler and kernel, and set up the MOP boot.
<P>
<HR>
<A HREF="linux_vax-3.html">Next</A>
<A HREF="linux_vax-1.html">Previous</A>
<A HREF="linux_vax.html#toc2">Contents</A>
</BODY>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: Specific problems</TITLE>
 <LINK HREF="linux_vax-4.html" REL=next>
 <LINK HREF="linux_vax-2.html" REL=previous>
 <LINK HREF="linux_vax.html#toc3" REL=contents>
</HEAD>
<<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
<A HREF="linux_vax-4.html">Next</A>
<A HREF="linux_vax-2.html">Previous</A>
<A HREF="linux_vax.html#toc3">Contents</A>
<HR>
<H2><A NAME="s3">3. Specific problems</A></H2>

<P>
<H2><A NAME="ss3.1">3.1 Where's the serial console switch on my VAX?</A>
</H2>

<P>
<P>Good question. On MicroVAX 3100's look at the back, and there is 
a small DIP switch near the power supply. You'll need to power off
and on again to make it use the serial port. The console serial port
is the MMJ connector with the printer symbol on it.
<P>
<P>I'll add more here as + when. 
<P>
<P>
<HR>
<A HREF="linux_vax-4.html">Next</A>
<A HREF="linux_vax-2.html">Previous</A>
<A HREF="linux_vax.html#toc3">Contents</A>
</<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: Specific problems</TITLE>
 <LINK HREF="linux_vax-4.html" REL=next>
 <LINK HREF="linux_vax-2.html" REL=previous>
 <LINK HREF="linux_vax.html#toc3" REL=contents>
</HEAD>
<BODY>
<A HREF="linux_vax-4.html">Next</A>
<A HREF="linux_vax-2.html">Previous</A>
<A HREF="linux_vax.html#toc3">Contents</A>
<HR>
<H2><A NAME="s3">3. Specific problems</A></H2>

<P>
<H2><A NAME="ss3.1">3.1 Where's the serial console switch on my VAX?</A>
</H2>

<P>
<P>Good question. On MicroVAX 3100's look at the back, and there is 
a small DIP switch near the power supply. You'll need to power off
and on again to make it use the serial port. The console serial port
is the MMJ connector with the printer symbol on it.
<P>
<P>I'll add more here as + when. 
<P>
<P>
<HR>
<A HREF="linux_vax-4.html">Next</A>
<A HREF="linux_vax-2.html">Previous</A>
<A HREF="linux_vax.html#toc3">Contents</A>
</BODY>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: References</TITLE>
 <LINK HREF="linux_vax-3.html" REL=previous>
 <LINK HREF="linux_vax.html#toc4" REL=contents>
</HEAD>
<<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
Next
<A HREF="linux_vax-3.html">Previous</A>
<A HREF="linux_vax.html#toc4">Contents</A>
<HR>
<H2><A NAME="s4">4. References</A></H2>

<P>
<A NAME="refs"></A> 
<UL>
<LI>VAX Architecture Reference Manual.  Leonard, T. (2nd ed) 1987 Digital Press Part No  EY-3459Y-DP</LI>
<LI>VAX VMS  Internals and Data Structures. Goldenberg R. (for VN 5.2) 1991 Digital Press. Part No  EY-C171E-DP</LI>
<LI>VAX Assembly Language. Baase, S, 1992 Prentice Hall</LI>
<LI>Alpha Architecture Handbook. Sites, R. 1992. Digital Press Part No.  EY-L520E-DP</LI>
</UL>
<HR>
Next
<A HREF="linux_vax-3.html">Previous</A>
<A HREF="linux_vax.html#toc4">Contents</A>
</<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ: References</TITLE>
 <LINK HREF="linux_vax-3.html" REL=previous>
 <LINK HREF="linux_vax.html#toc4" REL=contents>
</HEAD>
<BODY>
Next
<A HREF="linux_vax-3.html">Previous</A>
<A HREF="linux_vax.html#toc4">Contents</A>
<HR>
<H2><A NAME="s4">4. References</A></H2>

<P>
<A NAME="refs"></A> 
<UL>
<LI>VAX Architecture Reference Manual.  Leonard, T. (2nd ed) 1987 Digital Press Part No  EY-3459Y-DP</LI>
<LI>VAX VMS  Internals and Data Structures. Goldenberg R. (for VN 5.2) 1991 Digital Press. Part No  EY-C171E-DP</LI>
<LI>VAX Assembly Language. Baase, S, 1992 Prentice Hall</LI>
<LI>Alpha Architecture Handbook. Sites, R. 1992. Digital Press Part No.  EY-L520E-DP</LI>
</UL>
<HR>
Next
<A HREF="linux_vax-3.html">Previous</A>
<A HREF="linux_vax.html#toc4">Contents</A>
</BODY>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ</TITLE>
 <LINK HREF="linux_vax-1.html" REL=next>


</HEAD>
<<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
<A HREF="linux_vax-1.html">Next</A>
Previous
Contents
<HR>
<H1> Linux/VAX FAQ</H1>

<H2><CODE>lin...@so...</CODE></H2>
<P><HR>
<EM> This is the Frequently Asked Questions (FAQ) document for the Linux/VAX porting project.</EM>
<HR>
<P>
<H2><A NAME="toc1">1.</A> <A HREF="linux_vax-1.html">General Info</A></H2>

<UL>
<LI><A HREF="linux_vax-1.html#ss1.1">1.1 Whats a VAX?</A>
<LI><A HREF="linux_vax-1.html#ss1.2">1.2 Is that the same as a DECstation?</A>
<LI><A HREF="linux_vax-1.html#ss1.3">1.3 What Operating Systems/Software runs on a VAX?</A>
<LI><A HREF="linux_vax-1.html#ss1.4">1.4 Where do I buy one?</A>
<LI><A HREF="linux_vax-1.html#ss1.5">1.5 Whats the difference between a VAXserver and a VAXstation?</A>
</UL>
<P>
<H2><A NAME="toc2">2.</A> <A HREF="linux_vax-2.html">General Info about the port</A></H2>

<UL>
<LI><A HREF="linux_vax-2.html#ss2.1">2.1 What is the current status? </A>
<LI><A HREF="linux_vax-2.html#ss2.2">2.2 What do I need to help? </A>
<LI><A HREF="linux_vax-2.html#ss2.3">2.3 Explain your CVS setup.</A>
<LI><A HREF="linux_vax-2.html#ss2.4">2.4 I have a mumbleVAX, is it supported?</A>
<LI><A HREF="linux_vax-2.html#ss2.5">2.5 How do I get started? </A>
</UL>
<P>
<H2><A NAME="toc3">3.</A> <A HREF="linux_vax-3.html">Specific problems</A></H2>

<UL>
<LI><A HREF="linux_vax-3.html#ss3.1">3.1 Where's the serial console switch on my VAX?</A>
</UL>
<P>
<H2><A NAME="toc4">4.</A> <A HREF="linux_vax-4.html">References</A></H2>

<HR>
<A HREF="linux_vax-1.html">Next</A>
Previous
Contents
</<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#009900" VLINK="#990032" ALINK="#6F7463" FONT FACE="Helvetica">>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
 <TITLE> Linux/VAX FAQ</TITLE>
 <LINK HREF="linux_vax-1.html" REL=next>


</HEAD>
<BODY>
<A HREF="linux_vax-1.html">Next</A>
Previous
Contents
<HR>
<H1> Linux/VAX FAQ</H1>

<H2><CODE>lin...@so...</CODE></H2>
<P><HR>
<EM> This is the Frequently Asked Questions (FAQ) document for the Linux/VAX porting project.</EM>
<HR>
<P>
<H2><A NAME="toc1">1.</A> <A HREF="linux_vax-1.html">General Info</A></H2>

<UL>
<LI><A HREF="linux_vax-1.html#ss1.1">1.1 Whats a VAX?</A>
<LI><A HREF="linux_vax-1.html#ss1.2">1.2 Is that the same as a DECstation?</A>
<LI><A HREF="linux_vax-1.html#ss1.3">1.3 What Operating Systems/Software runs on a VAX?</A>
<LI><A HREF="linux_vax-1.html#ss1.4">1.4 Where do I buy one?</A>
<LI><A HREF="linux_vax-1.html#ss1.5">1.5 Whats the difference between a VAXserver and a VAXstation?</A>
</UL>
<P>
<H2><A NAME="toc2">2.</A> <A HREF="linux_vax-2.html">General Info about the port</A></H2>

<UL>
<LI><A HREF="linux_vax-2.html#ss2.1">2.1 What is the current status? </A>
<LI><A HREF="linux_vax-2.html#ss2.2">2.2 What do I need to help? </A>
<LI><A HREF="linux_vax-2.html#ss2.3">2.3 Explain your CVS setup.</A>
<LI><A HREF="linux_vax-2.html#ss2.4">2.4 I have a mumbleVAX, is it supported?</A>
<LI><A HREF="linux_vax-2.html#ss2.5">2.5 How do I get started? </A>
</UL>
<P>
<H2><A NAME="toc3">3.</A> <A HREF="linux_vax-3.html">Specific problems</A></H2>

<UL>
<LI><A HREF="linux_vax-3.html#ss3.1">3.1 Where's the serial console switch on my VAX?</A>
</UL>
<P>
<H2><A NAME="toc4">4.</A> <A HREF="linux_vax-4.html">References</A></H2>

<HR>
<A HREF="linux_vax-1.html">Next</A>
Previous
Contents
</BODY>
</HTML>

--- NEW FILE ---
<!doctype linuxdoc system> <!-- -*- SGML -*- -->
<!--
 v0.1 11 Jul 1999 Dave Airlie
-->
<article>

<title> Linux/VAX FAQ

<author><tt>lin...@so...</tt></author>
<abstract> This is the Frequently Asked Questions (FAQ) document for the Linux/VAX porting project.
</abstract>

<toc>

<sect> General Info<p><label id="geninfo">
<sect1>Whats a VAX?<p>

VAXes were 32-bit computer systems from Digital Equipment Corporation
(or DEC). They enjoyed huge popularity throughout the 1980's and early 
1990's. The VAX was the 32 bit computer that
the ancestors of  modern UNIXes were made on, and was the standard computer
architecture (like the IBM PC is now) of its day. The VAX was also one of the
major testbeds for the early Internet.<p>

VAXes come in several shapes and sizes, ranging from the small room sized
VAX 11/780 (1970's) through to the desktop sized microVAXes and VAXStations
of the 1990's. The VAX architecture and Digital's VAX/VMS operating system 
are mutually intertwined, so for a review of VAXes see<p>
<htmlurl url="http://www.vaxarchive.org/" name="The VAX Archive"><p>
<htmlurl url="http://www.openvms.compaq.com/openvms/20th/vmsbook.pdf" name="VMS 20th 
anniversary special">

<sect1>Is that the same as a DECstation?<p>

No. The DECstations use the MIPS processor, and have names like 
<itemize>
<item>DECstation 5000/200
<item>DECstation 5000/240
<item>Personal DECstation
</itemize>

These use the R3000 or similar MIPS CPU. Many of the peripherals are similar
to those found in later model VAXstations, but they are not the same.<p>
These were a stopgap for a few years while DEC developed what would become 
the Alpha processor. I've got one, but I'm not an expert on them, so please
don't ask us questions about them.<p>

The DECstations ran ULTRIX/Mips as the only offering from DEC. They never
ran VMS. If you have one of these, you can also run;
<itemize>
<item><htmlurl url="http://decstation.unix-ag.org/" name="Linux/MIPS for
DECstations">
<item><htmlurl url="http://www.netbsd.org/" name="NetBSD/pmax">
</itemize>

<sect1>What Operating Systems/Software runs on a VAX?<p>

The following Operating Systems run on a VAX;
<itemize>
<item><htmlurl url="http://www.openvms.compaq.com" name="Compaq OpenVMS/VAX">
<item>Compaq ULTRIX/VAX
<item><htmlurl url="http://www.netbsd.org" name="NetBSD/VAX">
<item><htmlurl url="http://www.linux-vax.org" name="Linux/VAX">
</itemize>

<sect1>Where do I buy one?<p>

The VAX system line has been discontinued, so DEC, now owned by Compaq,
no longer sell them. However, occasionally systems
for sale do come up on EBay and other on line auction houses. Also look out
for companies "upgrading" their VAXes to something more newfangled.
Occasionally port-vax (The NetBSD mailing list) or linux-vax (our mailing
list) will have notices of VAXes up for grabs.

<sect1>Whats the difference between a VAXserver and a VAXstation?<p>

Practically speaking, for the 3100 series, a keyboard, a mouse, a monitor,
and the little switch in the back in the other position. VAXstations were 
designed for graphical work, and tended to come with better graphics cards.
VAXservers just sat there, and used a terminal as the console. <p>

For more information about such details see, for example,
<htmlurl url="http://www.vaxarchive.org" name="The VAX archive">

<sect>General Info about the port
<sect1> What is the current status? <p> <label id="status">

<sect2>Kernel<p><label id="kernelstat">

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

We currently know that we boot to shell on the following VAXen:
<itemize>
<item>VAXstation 3100m30 (KA42 CPU)
<item>VAXstation 3100m38 (KA42 CPU)
<item>VAXstation 3100m76 (KA43 CPU)
<item>VAXstation 4000/60 (KA46 CPU)
</itemize>

We have, in the past, at least partially booted on the following:
<itemize>
<item>VAXstation 3500 (KA650 CPU)
<item>VAXstation II/GPX (KA630 CPU)
<item>MicroVAX 3400 (KA640 CPU)
<item>VAXserver 4000-200 (KA660 CPU)
<item>VAXstation 3100m85 (KA55 CPU)
</itemize>

We have drivers for the console, ethernet and SCSI on the;
<itemize>
<item>VAXstation 3100m76 (KA43 CPU)
<item>VAXstation 3100m38 (KA42 CPU)
<item>VAXstation 4000/60 (KA46 CPU) (not SCSI yet)
</itemize>
and works in progress for the SCSI and ethernet on the
<itemize>
<item>VAXstation 4000/60 (KA46 CPU)
<item>VAXstation 3100m85 (KA55 CPU)
</itemize>

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

<sect2>Compilers, binutils, etc...<p>

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).

<sect1> What do I need to help? <p> <label id="help">


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

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.<p>

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 <htmlurl 
   url="http://www.openvms.digital.com/wizard/openvms_faq.html#MISC1" 
   name="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.

<itemize>
<item>
	Put your PC and VAX on the same ethernet segment.  Install mopd
	(Maintainence Operations Protocol Daemon) on the PC.  Point mopd
	at the vmlinux.SYS image and tell your VAX to boot from the 
	network (usually BOOT XQA0 or BOOT ESA0)
<item>
	Put a SCSI card with an external SCSI connector into your PC.
	Connect your VAXstation, a hard disk and your PC together on
	one SCSI chain.  Then dd the vmlinux.dsk image to the disk and
	tell the VAX to boot from that disk.
</itemize>

<sect1>Explain your CVS setup.<p>

   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.
 <p>
 The main modules are;
 <itemize>
 <item> kernel - The 2.2/2.3 series kernel. Dont use it....
 <item> kernel-2.4 - The current 2.4 series kernel. This is the one that 
 we are actively working on.
 <item> tools - This is the toolchain. If you download this via cvs, just use
 the ./build-vax.sh script to build a cross compilation environment for 
 Linux/VAX (tested on Linux/i386 and Linux/MIPS only AFAIK, but should
 work on other unixes).
 <item> uClibc - The micro libc from lineo. We're concentrating on moving
 to glibc soon, but at the moment, this is the libc we use. 
 <item> usr - various useful programs, busybox, mopd, asbl..
 </itemize>
 <p>
 Access to CVS is via the standard sourceforge method. 
 
 <sect2>Can I get write access?<p>
 
 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.<p>
 
 <sect2>I dont want to got through all of that, what now?<p>
 
 Send the patch, and one of us will apply it. 
 
<sect1>I have a mumbleVAX, is it supported?<p>

   See section <ref id="kernelstat" name="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 <tt>cpu_xxx.c</tt>
files in the <tt>arch/vax/kernel</tt> directory to get an idea of what you
need to implement for a machine vector. <p>   
   
<sect1> How do I get started? <p> <label id="started">
Read Documentation/vax/README at 
<url url="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax" 
   name="ftp://linux-vax.sourceforge.net/pub/linux-vax/README.vax">. 
This describes howto download the compiler and kernel, and set up the MOP boot.

<sect>Specific problems<p>
<sect1>Where's the serial console switch on my VAX?<p>

  Good question. On MicroVAX 3100's look at the back, and there is 
  a small DIP switch near the power supply. You'll need to power off
  and on again to make it use the serial port. The console serial port
  is the MMJ connector with the printer symbol on it.<p>
  
  I'll add more here as + when. 
  

<sect> References<p><label id="refs">
<itemize>
<item>VAX Architecture Reference Manual.  Leonard, T. (2nd ed) 1987 Digital Press Part No  EY-3459Y-DP
<item>VAX VMS  Internals and Data Structures. Goldenberg R. (for VN 5.2) 1991 Digital Press. Part No  EY-C171E-DP
<item>VAX Assembly Language. Baase, S, 1992 Prentice Hall
<item>Alpha Architecture Handbook. Sites, R. 1992. Digital Press Part No.  EY-L520E-DP
</itemize>
</article>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="GENERATOR" CONTENT="Mozilla/4.10 [en] (X11; I; Linux 2.0.36 i586) [Netscape]">
   <META NAME="Author" CONTENT="atp">
   <TITLE>Linux/VAX Porting Project</TITLE>
</HEAD>
<frameset rows="130,*" border=0>
<frame src="../header.html" >
<frame src="linux_vax.html" >
</frameset>
</HTML>

--- NEW FILE ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="GENERATOR" CONTENT="Mozilla/4.10 [en] (X11; I; Linux 2.0.36 i586) [Netscape]">
   <META NAME="Author" CONTENT="atp">
   <TITLE>Linux/VAX Porting Project</TITLE>
</HEAD>
<frameset rows="130,*" border=0>
<frame src="../header.html" >
<frame src="linux_vax.html" >
</frameset>
</HTML>

[LV-commit] CVS: www/htdocs/newfaq - New directory

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/newfaq
In directory usw-pr-cvs1:/tmp/cvs-serv22282/newfaq

Log Message:
Directory /cvsroot/linux-vax/www/htdocs/newfaq added to the repository

[LV-commit] CVS: www/htdocs/linux-vax atp_small.gif,1.1,NONE docs.html,1.3,NONE faq.html,1.2,NONE index-test.html,1.1,NONE index.html,1.1.1.1,NONE index.html.24.10.99,1.1,NONE index.html.aa,1.1,NONE index.notable,1.1,NONE index_old.html,1.1,NONE screenshots.html,1.2,NONE status.html,1.3,NONE template.html,1.1,NONE

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/linux-vax
In directory usw-pr-cvs1:/tmp/cvs-serv29329/linux-vax

Removed Files:
	atp_small.gif docs.html faq.html index-test.html index.html 
	index.html.24.10.99 index.html.aa index.notable index_old.html 
	screenshots.html status.html template.html 
Log Message:
Attempt to update web site


--- atp_small.gif DELETED ---

--- docs.html DELETED ---

--- faq.html DELETED ---

--- index-test.html DELETED ---

--- index.html DELETED ---

--- index.html.24.10.99 DELETED ---

--- index.html.aa DELETED ---

--- index.notable DELETED ---

--- index_old.html DELETED ---

--- screenshots.html DELETED ---

--- status.html DELETED ---

--- template.html DELETED ---

[LV-commit] CVS: www/htdocs/images nworkhouse.jpg,NONE,1.1

[Andy P. <at...@us...>]

Update of /cvsroot/linux-vax/www/htdocs/images
In directory usw-pr-cvs1:/tmp/cvs-serv29329/images

Added Files:
	nworkhouse.jpg 
Log Message:
Attempt to update web site


--- NEW FILE ---
ÿØÿà
ÿÛ

 $.' ",#(7),01444'9=82<.342ÿÀ
ÿÄ
%&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÂÃÄÅÆÇÈÉÊÒÓÔÕÖ×ØÙÚáâãäåæçèéêñòóôõö÷øùúÿÚ
ø_zêºÕ´S/[xÛ̗?î.Hüp+ÊõïÚJÚ2ñxC’Sü3ß>ÁŸ÷$ø¯,ñÅox“z]k2ÁnßòÂÏ÷)C·’>¤Ö^‰ãøq³¤ëw–ëÆ=ûã'Ô£eOå^Ÿ þÑú½¶ÈµÝ&Úõkf1Iõ åIúm¯PÐ~4ø']+ԎŸ;`ywéåÿ
ð
(¢¬ØêºeÀ¸°¼¸´œt’	Z6ˆ9¯EÐ~<xÏG	Üðj°/»g\ûœ×§è´O†ï¦µgu¥ËÝÔyñ~j7ãµéÚ7‰tOÃæé­¥êã$C(,¿Uê?Z”QEQEQE2Y¢·‰¥šDŽ4gv
È 
“œïü1ï^{ñãOŸÃþ(ð÷Ž4ôıJ±H݌‘ñçê7¢×¸éš„¶—i¨Ú¶ë{¨VhϪ°Èþuà_-®>&üg¶ð¤Æ;]6ݖIz¬lW{·çå§ÔV§ìñ­ËZׄïw%͜¦â8ŸªŒì{a‚þ,k³øËâOøG>ßyo¶êÿ
Y›Ÿa´ú×gðïÇ6¾=ðÒê1F º‰¼««|çcã9ªG#ñ«‹ñ­¾©¬ümÒü=mâ=cJ³¹Ò|÷7oÞ­/;sŽBÓµj·Â}H£øâàØà›æ ¦høYâ}bóR×ü+¯]ëÍ-/€Á™70ù½Æ?^y5¾0êWÚv­àÕ´¾½¶ŠçR\Çmu$>te“*ÅìO=FksÆ_âÑ/cÐ4;oíoÝ|°ÙDr"$gt§ø@ノxÔþ	𞯤$šˆµýCRÕnXÈð›¹>Ío“’‘ÇœwêGa€;öTQM‘±<lX+¤«<úÈ>⼋ö~Õµ=gڵΩ©^ßL·k½ÕË˵B¸œrOJõ=]wè׫¾DýÃᣑ‘‡Êy¤}Á®#à¥õî¥ðÚÚóP½º¼¹–â]òÜÎò±Ã`±8ÇçU|uã­e¼Qüm®Ì¡în¥
ÀñWü[ŸÚË\]ÑéÚ£	&?É>Isë†Ãþ"¬|LvñïÆ}Á±k;">Òž¬<É}£
¾E{?ŠtÉu?ë]	-̈́ÐB«€2ÈTaÎ+„ø}m/ÃÓ§+…½²º•n!n‚G\vϨ#µz}ÍÌ6v²ÜÜʑA’G8UP2I>•ãß
læ–ãŚôk"iº…è¡—hp­!$màqÇQۈ¼s¤Ýë_ôk+ZãJ´\‹«q—PbGQ×¥Aãß
øãÂÞ—X°ñε¨ÇnÀÝE»c,G«©ôã>Ù=«½øc øoJð´Wþ’k”Ô€žk»‡Ý4­ÏzF|õ<×ñîn.<›ydÔJ$ÀdÆÄ 
Žø<Ô¾&ø>šf…«á)îÿ
;h¾+×l­å£H®
AžG@29ÿ
yý½z
¦™e
•´VÖ°®Øâ‰Bª`+¼ðgÚ¾#YxÀ_ì–ÖÓì‚ÛÉÈd%É;·uùÏoN+§šî!’‘dŠE(èÃ! Jä|àWð,7¶jÍuaq)™-ž¢=vÄàŒô=rïøxÊïFµiý—qö„Qýí•<üϖºúáÓáÌv_ßźN¦Úyœ
we9Žãûžn	ë:ŒòsžâŠ)qF@lpHÈé\wÿ