diff options
Diffstat (limited to 'static/netbsd/man4/man4.mvme68k/memc.4 3.html')
| -rw-r--r-- | static/netbsd/man4/man4.mvme68k/memc.4 3.html | 63 |
1 files changed, 0 insertions, 63 deletions
diff --git a/static/netbsd/man4/man4.mvme68k/memc.4 3.html b/static/netbsd/man4/man4.mvme68k/memc.4 3.html deleted file mode 100644 index 5cddc300..00000000 --- a/static/netbsd/man4/man4.mvme68k/memc.4 3.html +++ /dev/null @@ -1,63 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">MEMC(4)</td> - <td class="head-vol">Device Drivers Manual (mvme68k)</td> - <td class="head-rtitle">MEMC(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">memc</code> — - <span class="Nd">MVME162-MVME177 Memory Controller Chip</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">memc* at mainbus0</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">memc</code> devices are used on MVME162, - MVME167, MVME172 and MVME177 boards to manage one or more DRAM modules.</p> -<p class="Pp">Depending on the type of DRAM module fitted, the device will - either be a MEMC040 device or an MCECC device. The former manages a Parity - DRAM module while the latter manages an ECC DRAM module.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag Bl-compact"> - <dt>memc0 at mainbus0.</dt> - <dd>This is the normal autoconfiguration message indicating that the Memory - Controller Chip has been found and attached to the main processor - bus.</dd> - <dt>memc0: Correctable error on CPU read access to 0x12345678.</dt> - <dd>This indicates that an MCECC memory controller detected and corrected a - single bit error in one of the DRAM banks. There are a few variations on - the message where "CPU" can be replaced with "Peripheral - Device" or "Scrubber", and "read" can be - substituted for "write". This message is followed by some more - details which can help pin-point the error...</dd> - <dt>memc0: ECC Syndrome 0x23 (DRAM Bank C, Bit#16).</dt> - <dd>Pin-points exactly where the error occurred.</dd> - <dt>memc0: Uncorrectable error on CPU read access to 0x12345678.</dt> - <dd>Errors like this have the potential to corrupt data. As such, it is likely - the system will panic very soon afterwards.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">mvme68k/mainbus(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The <code class="Nm">memc</code> driver does not yet fully support - the MEMC040 (Parity) version of the device.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 17, 2017</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |