moving clists out of kdata

Article View: net.bugs.2bsd

Article #64

#64

From: utzoodecvaxharponpoisucbvaxmicha...
Date: Tue, 29 Jun 1982 04:33

9 lines
872 bytes

Looking at the dh code it seems that if the clists are not all in the
same unibus region (have the same extension bits) that the code will
not work properly.  The dhcsr dosn't track the extension bits
and therefore arbitrary or'ing of IENABLE may change them to the wrong
value.  I think the problems may actually not come up, but has someone
thought this through?  I am sure there would be problems
if a single clist element could span a region.  In dhxint the
&= ~XINT could reset the bits to 0 when the line has already incremented
them to 1.

Technical Details

Message-ID: <bnews.ucbvax.7811>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

From: utzoo!decvax!harpo!npois!ucbvax!michael
Newsgroups: net.bugs.2bsd
Title: moving clists out of kdata
Article-I.D.: ucbvax.7811
Posted: Tue Jun 29 04:33:03 1982
Received: Wed Jun 30 01:07:43 1982
Subject: moving clists out of kdata
Date: Tue, 29 Jun 1982 04:33:03 +0000
Message-ID: <bnews.ucbvax.7811>