The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: simul8@simul8.demon.co.uk (James Lothian)
Subject: 2.11BSD boot looping
Date: Mon, 29 Nov 1999 14:55:49 +0000	[thread overview]
Message-ID: <384293F5.959724D5@simul8.demon.co.uk> (raw)
In-Reply-To: <13503043955.14.DSEAGRAV@toad.xkl.com>

For what it's worth, this does sound suspiciously like what the 4.3
boot code did with the Viking. As far as I can remember, there is a 
flag in one of the UDA50 registers that is set to 1 one the device
interrupts. The 4.3 boot code runs the UDA50 with interrupts disabled,
but polls this flag to find out when the controller has finished a
command.
On the UDA50, even if interrupts are disabled, this flag gets set. On
the viking, it doesn't. I can't remember the exact change I made, but I
got it from the sources for some later version of 4.3, which I probably
found on the internet. I'll try firing the beast up tonight, and see if
I
can figure out what I did. 

My hacked around version of UW 4.3+NFS that Michael Sokolov uploaded
to PUPS should also contain this modification. Somebody could try 
comparing my version to the original UW version -- they're both in the
archive, as far as I know.

James

"Daniel A. Seagraves" wrote:
> 
> It's looping around at 157702.
> 
> 157702 contains 001776
> 
> -------



       reply	other threads:[~1999-11-29 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13503043955.14.DSEAGRAV@toad.xkl.com>
1999-11-29 14:55 ` James Lothian [this message]
1999-11-29 22:07 Steven M. Schultz
1999-12-08 21:09 ` Daniel A. Seagraves
1999-12-09 21:18 Daniel A. Seagraves

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=384293F5.959724D5@simul8.demon.co.uk \
    --to=simul8@simul8.demon.co.uk \
    /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).