The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] Trouble with 2.11BSD and CQD-220
Date: Tue, 6 Nov 2001 12:50:43 -0800 (PST)	[thread overview]
Message-ID: <200111062050.fA6Koh627439@moe.2bsd.com> (raw)

Hi -

> From: Tom Ivar Helbekkmo <tih at Hamartun.Priv.NO>
> Not exactly.  You and I actually worked this out together back in
> 1995, when I was figuring out how to get Reno to boot my VAX using a
> CQD-220.  :-)  You don't have to present any interrupt vector, but you

	Has it been that long? ;)

> shouldn't lie to the controller about this.  Instead of setting the

	But if you do present a vector then everything should work, right?

	The problem isn't in the standalone 'ra' driver though - that seems
	to be working.   The boot block though ends up in an endless loop
	during the 'online the unit' command (after the initialization).

> "please interrupt" bit in the MSCP datagram, and waiting for the
> controller to set the "I've interrupted now" bit, you should set the
> "controller owns this datagram now" bit, and wait for it to clear it.
> This make much better sense, anyway, while running in polled mode.

	True.  I'd have to look at the mdec/rauboot.s sources to see
	exactly what it is doing (or not doing ;)).  The change Tim Shoppa
	made was to specify a vector and that did the trick for the Viking
	controller.

	Steven



             reply	other threads:[~2001-11-06 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 20:50 Steven M. Schultz [this message]
2001-11-07  0:48 ` Chuck Dickman
  -- 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=200111062050.fA6Koh627439@moe.2bsd.com \
    --to=sms@2bsd.com \
    /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).