At 01:01 PM 2/25/02 +0100, Jochen Kunz wrote:
>Speaking of DSSI support: I know that someone was working on this
>and that his work based on the SII because he has only a MV3400.
>How far is this?

I started working on it and then got distracted by a California power 
crisis and BattleBots. So instead of getting it running this past year I've 
entered a 'bot into the show a couple of times. The bad news is that I'm 
still doing BattleBots this year (next event is in May), but the plan is to 
win it all this year and let the rest of the team carry on the tradition. 
Its way too expensive a hobby for me, especially since I've got lots of VAX 
projects I can do for "free."

As for the status, I have managed to get the SII chip configured into the 
system. Using a hack I verified that MSCP is the protocol used over the 
DSSI bus. The next step is to write the bus configurator that runs when 
dssi<n> bus exists to find out what drives and/or systems are out there.

>  I am willing to donate some time to the SHAC side,
>when my RX01/02 driver and the corresponding "NetBSD device driver
>writing HOWTO" is finished. (The finish will be soon.)

I certainly look forward to your write up. The SHAC is a bit more 
complicated than the SII. I've got the KA660 manual that describes it. Its 
frustrating when you run into bogus newbie problems but everyone here is 
very supportive.

>And the usual question: Manuals? DSSI? SHAC? MSCP?

DSSI is described a bit in various CPU -TM's like the KA640 and KA660. MSCP 
is described in the UDA50 programmers manual and SHAC in the KA660 manual.

--Chuck