static/netbsd/man4/man4.i386/elanpar.4 3.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83

<table class="head">
  <tr>
    <td class="head-ltitle">ELANPAR(4)</td>
    <td class="head-vol">Device Drivers Manual (i386)</td>
    <td class="head-rtitle">ELANPAR(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">elanpar</code> &#x2014; <span class="Nd">AMD Elan
    SC520 Programmable Address Regions</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">elansc* at mainbus? bus ?</code>
  <br/>
  <code class="Cd">elanpar* at elansc?</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">elanpar</code> driver supports the
    write-protect feature of the AMD Elan SC520 microcontroller's integrated
    Programmable Address Regions. Currently, <code class="Nm">elanpar</code>
    protects the kernel text from being overwritten by the CPU or errant
  DMA.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
  <dt>elanpar0: cpu violated write-protect window %u</dt>
  <dd></dd>
  <dt>elanpar0: gp violated write-protect window %u</dt>
  <dd></dd>
  <dt>elanpar0: pci violated write-protect window %u</dt>
  <dd></dd>
</dl>
<p class="Pp">A Programmable Address Region stopped either the CPU, the
    general-purpose bus (gp), or a PCI bus master from writing to the indicated
    window of write-protected memory.</p>
<dl class="Bl-diag">
  <dt>elanpar0: %u bytes of kernel text are unprotected</dt>
  <dd></dd>
</dl>
<p class="Pp" id="_u"><code class="Nm">elanpar</code> has not write-protected
    <a class="permalink" href="#_u"><i class="Em">%u</i></a> bytes of the kernel
    text.</p>
</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">i386/elanpex(4)</a>,
    <a class="Xr">i386/elansc(4)</a>, <a class="Xr">dmesg(8)</a>,
    <a class="Xr">syslogd(8)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">elanpar</code> device first appeared in
    <span class="Ux">NetBSD 5.0</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
<p class="Pp">The <code class="Nm">elanpar</code> driver was written by
    <span class="An">David Young</span>
    &lt;<a class="Mt" href="mailto:dyoung@NetBSD.org">dyoung@NetBSD.org</a>&gt;.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
<p class="Pp"><code class="Nm">elanpar</code> leaves as many as 65535 bytes
    unprotected at the beginning and end of kernel text. Also,
    <code class="Nm">elanpar</code> is not compatible with setting breakpoints
    using <a class="Xr">ddb(4)</a>. Disable <code class="Nm">elanpar</code>
    using <code class="Ic">drvctl</code> <code class="Fl">-d</code>
    <var class="Ar">elanpar0</var> before setting a breakpoint with
    <a class="Xr">ddb(4)</a>.</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>