The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: chd_1@nktelco.net (Chuck Dickman)
Subject: [pups] Trouble with 2.11BSD and CQD-220
Date: Tue, 06 Nov 2001 19:48:57 -0500	[thread overview]
Message-ID: <3BE884F9.9D4752A5@nktelco.net> (raw)
In-Reply-To: <200111062050.fA6Koh627439@moe.2bsd.com>

Hi
Combining what Steven and Tom have said and looking at ra.c
in standalone, I think I have a working version of rauboot now. 

rauboot set the bit to cause an interrupt on ring transitions,
and then looped on the interrupt flag of the command and
response packets. I guess since CQD-220 was not completely set
up for interrupts, it would never set these flags.

pdpstand/ra.c did not set the interrupt on ring transitions bit,
and instead looped on the packet ownership bits. The CQD-220
seems to handle these bits as the standalone code expects.

Here are the changes that I made to rauboot.s. 

Chuck

[Steven, Let me know if you want me to send you more than
this.]
------------------------cut here----------------------
*** rauboot.s.orig      Wed May 31 22:54:49 1995
--- rauboot.s   Mon Nov  5 19:21:26 2001
***************
*** 16,22 ****
 
  MSCPSIZE =    64.     / One MSCP command packet is 64bytes long (need
2)

! RASEMAP       =       140000  / RA controller owner semaphore

  RAERR =               100000  / error bit
  RASTEP1 =     04000   / step1 has started
--- 16,23 ----

  MSCPSIZE =    64.     / One MSCP command packet is 64bytes long (need
2)
  
! /RASEMAP =    140000  / RA controller owner semaphore and _interrupt_
! RASEMAP       =       100000  / RA controller owner semaphore

  RAERR =               100000  / error bit
  RASTEP1 =     04000   / step1 has started
***************
*** 287,304 ****
        mov     $RASEMAP,*$ra+RARSPH    / set mscp semaphores
        mov     $RASEMAP,*$ra+RACMDH
        mov     *raip,r0                / tap controllers shoulder
!       mov     $ra+RACMDI,r0
  1:
        tst     (r0)
!       beq     1b                      / Wait till command read
!       clr     (r0)+                   / Tell controller we saw it, ok.
  2:
        tst     (r0)
!       beq     2b                      / Wait till response written
        clr     (r0)                    / Tell controller we go it
        rts     pc

! icons:        RAERR
        ra+RARING
        0
        RAGO
--- 288,308 ----
        mov     $RASEMAP,*$ra+RARSPH    / set mscp semaphores
        mov     $RASEMAP,*$ra+RACMDH
        mov     *raip,r0                / tap controllers shoulder
!       mov     $ra+RACMDH,r0
  1:
        tst     (r0)
!       bmi     1b                      / Wait till command read
! /     clr     (r0)+                   / Tell controller we saw it, ok.
!       mov     $ra+RARSPH,r0
  2:
        tst     (r0)
!       bmi     2b                      / Wait till response written
!       mov     $ra+RACMDI,r0
!       clr     (r0)+                   / Tell controller we saw it, ok.
        clr     (r0)                    / Tell controller we go it
        rts     pc
  
! icons:        RAERR + 033
        ra+RARING
        0
        RAGO



  reply	other threads:[~2001-11-07  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 20:50 Steven M. Schultz
2001-11-07  0:48 ` Chuck Dickman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07  4:01 Steven M. Schultz
2001-11-05  4:15 Steven M. Schultz
2001-11-06 19:55 ` Tom Ivar Helbekkmo
2001-11-05  2:37 Chuck Dickman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BE884F9.9D4752A5@nktelco.net \
    --to=chd_1@nktelco.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).