[eros-cvs] cvs commit: eros/src/doc/www/design-notes UserDrivers.html

[shap@eros.cs.jhu.edu]

shap        01/01/20 15:30:57

  Modified:    src/doc/www/design-notes UserDrivers.html
  Log:
  Clarify that release of driver memory is explicit

Revision  Changes    Path
1.2       +7 -6      eros/src/doc/www/design-notes/UserDrivers.html

Index: UserDrivers.html
===================================================================
RCS file: /cvs/eros/src/doc/www/design-notes/UserDrivers.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- UserDrivers.html	2001/01/15 16:54:53	1.1
+++ UserDrivers.html	2001/01/20 20:30:57	1.2
@@ -91,15 +91,16 @@
 	      Objects in this object range are exempt from checkpoint,
 	      ageing, and such, and the drivers in them therefore will
 	      not be accidentally removed. These objects can be
-	      <em>explicitly</em> released by the driver manager once
-	      all drivers have been configured.
+	      <em>explicitly</em> released from memory by the driver
+	      manager once all drivers have been configured. After
+	      this their pages are subject to removal by ageing.
 	    </p>
 	    <p>
 	      For the sake of simplicity, we will assume for the
-	      moment that <em>no</em> drivers will be released in this
-	      way. For embedded and set-top devices, we probably want
-	      to build system images that contain only necessary
-	      drivers in any case.
+	      moment that <em>no</em> drivers will be released from
+	      memory in this way. For embedded and set-top devices, we
+	      probably want to build system images that contain only
+	      necessary drivers in any case.
 	    </p>
 	    <h2>I/O Registers</h2>
 	    <p>