Hi Helmar and all,


> I SEE THE FIRST CONSOLE OUTPUT OF NETBSD-KERNEL ON FALCON  		YEP :-))
> and even with a personal note to me (line with '**' below) ;-))
> unless the kernel hung after one page of output 
> (the position is shown below with '<<=====')
Finally, we're getting somewhere!

> 
> So here is the whole output I got (transcribed with hand):
> 
lot's of transcription deleted...
> fdc0 at mainbus0
> fd0 at fdc0
> zs0 at mainbus0<<===== h e r e the cursor stands and the kernel hung !
I think I fixed this, the code was accessing the SCU which is not present
on the Falcon.

> > 
> > I also disabled some of the colormap stuff. So _maybe_ we can again get 
> > a bit further in the boot process.
> O, you agree that we have done a BIG step in progress. Now You can omit the
> boring dot-lines and put *real* text (for debugging purposes) in future 
> kernels. 
I removed them. I also have put a new loadbsd.ttp into your incoming directory,
this is the latest version that is on sun-lamp. Your version of loadbsd was
responsible for the first 3 or so lines.
I have put 2 kernels into your incoming directory:
 netbsd.h5:
     This kernels tries to automagically find out if it is running on a
     Falcon or TT. Try this one first. If it gives you console output,
     you can skip trying netbsd.h6. I hope it runs nicely through the
     serial port init as I am curious to know what the SCSI code will
     do on a Falcon. I have been busy all week to modify it.
 netbsd.h6:
     Functionally the same as netbsd.h5. The only difference is that
     it is hardcoded to run on a Falcon.
> 
> But at this weekend I'm again on tour with my (fresh repaired) camper
> and I 'll be online at Sunday evening again. At that time I expect your next
> kernel ;-) I'm very exciting.
It sure is beautiful wether to do this! Becarefull with your camper :-)
Guess I did make my dead-line.

Leo.