[Top] [All Lists]

Re: DECStation update...

Subject: Re: DECStation update...
From: Frieder Streffer <>
Date: Thu, 1 May 1997 12:16:20 +0200 (MET DST)
In-reply-to: <>

On Thu, 1 May 1997, Paul Antoine wrote
> I've just loaded the kernel binary onto Softway's FTP, and Luc's 
> wonder-script 
> will pull that back to the main ftp site sometime today (I think this happens 
> hourly but can't remember).  I've created a link to it in the web page,
> and have updated the Port Status and the Development Environment Notes to
> reflect this.
> The test kernel binary should be available at:
> Would you please check that it boots at least to the 'Added tags' point in
> the kernel? It's not getting past the code at kernel_entry in head.S due to 
> R4K'isms in that portion of the code (due to R4K coders setting the assembler 
> to 'noreorder' then assuming all MIPS CPU's have 'some' interlocks as does
> the R4K... :-)
> The new DECStation code uses the 2100/3100 PROM routines prior to 
> initialising the driver code you both wrote.  It also should correctly 
> determine the amount of memory present... tell me if it doesn't, as I've 
> had to call either your code or the original DS5000 code that queries the 
> depending upon which machine it detects... hopefully your code still works!!
> Regards,
> Paul
> _______________________________________________________________________________
> Paul M. Antoine,                                      Net:
> Softway Pty Ltd                                               WWW: 
> PO Box 305, Strawberry Hills, NSW 2012, Australia       Tel: +61 2 9698 2322
> Level 2, 79 Myrtle St, Chippendale, NSW 2008, Australia Fax: +61 2 9699 9174
> "It is the lack of acceptance of diversity which threatens to 
>  destroy society, NOT the free expression of it." - Me.
Hi Paul,
no, sorry the kernel craches immedeatly after the boot with

Excptn    : <vtr=NRML>
Excptn pc : 0x300800d
CReg      : 0x10
SReg      : 0x30080000
Vaddr     : 0x304800d
Sp        : 0xa17fc0000

I don't get any message of the kernel, so something with the PROM call 
might be wrong.


<Prev in Thread] Current Thread [Next in Thread>