diff options
Diffstat (limited to 'static/netbsd/man4/acpismbus.4 4.html')
| -rw-r--r-- | static/netbsd/man4/acpismbus.4 4.html | 63 |
1 files changed, 0 insertions, 63 deletions
diff --git a/static/netbsd/man4/acpismbus.4 4.html b/static/netbsd/man4/acpismbus.4 4.html deleted file mode 100644 index c72f5620..00000000 --- a/static/netbsd/man4/acpismbus.4 4.html +++ /dev/null @@ -1,63 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">ACPISMBUS(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">ACPISMBUS(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">acpismbus</code> — <span class="Nd">ACPI - SMBus Control Method Interface</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">acpismbus* at acpi?</code> - <br/> - <code class="Cd">iic* at acpismbus?</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">acpismbus</code> driver supports instances of - the ACPI SMBus Control Method Interface. This enables i2c access to bus - segments which might not otherwise be accessible due to missing - "native" driver support. The SMBus Process Call protocol is not - supported. All other SMBus protocols are supported to the extent that the - underlying controller supports them.</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">acpi(4)</a>, <a class="Xr">iic(4)</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">acpismbus</code> driver appeared in - <span class="Ux">NetBSD 6.0</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">Although <code class="Nm">acpismbus</code> SMBus Alerts can be - associated with individual devices, this capability is ignored. When an - <code class="Nm">acpismbus</code> SMBus Alert is generated, all devices on - the i2c bus segment which have registered an interrupt routine are - notified.</p> -<p class="Pp">The SMBus CMI protocol defines a method to provide a list of - devices on an i2c bus segment and their addresses. The - <code class="Nm">acpismbus</code> driver makes no attempt to retrieve or - process this device list.</p> -<p class="Pp">There is currently no way to determine if the i2c controller - managed by an instance of the ACPI SMBus CMI can also be accessed using a - native device driver. Therefore, the <code class="Nm">acpismbus</code> - driver should not be enabled by default. If both a native driver and the - <code class="Nm">acpismbus</code> driver attempt to access the same i2c bus - segment, the results are undefined.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 6, 2010</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |