svn commit: r40923 - head/en_US.ISO8859-1/books/arch-handbook/isa
Rene Ladan
rene at FreeBSD.org
Mon Feb 11 00:02:50 UTC 2013
Author: rene
Date: Mon Feb 11 00:02:49 2013
New Revision: 40923
URL: http://svnweb.freebsd.org/changeset/doc/40923
Log:
Some 'igor -z' improvements.
Approved by: gjb (mentor)
Modified:
head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
Modified: head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:07 2013 (r40922)
+++ head/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml Mon Feb 11 00:02:49 2013 (r40923)
@@ -31,7 +31,7 @@
</authorgroup>
</chapterinfo>
- <title>ISA device drivers</title>
+ <title>ISA Device Drivers</title>
<sect1 id="isa-driver-synopsis">
<title>Synopsis</title>
@@ -49,7 +49,7 @@
</sect1>
<sect1 id="isa-driver-basics">
- <title>Basic information</title>
+ <title>Basic Information</title>
<para>A typical ISA driver would need the following include
files:</para>
@@ -208,7 +208,7 @@
</sect1>
<sect1 id="isa-driver-device-t">
- <title>Device_t pointer</title>
+ <title>Device_t Pointer</title>
<para><structname>Device_t</structname> is the pointer type for
the device structure. Here we consider only the methods
@@ -277,8 +277,8 @@
</sect1>
<sect1 id="isa-driver-config">
- <title>Configuration file and the order of identifying and probing
- during auto-configuration</title>
+ <title>Configuration File and the Order of Identifying and Probing
+ During Auto-Configuration</title>
<indexterm><primary>ISA</primary><secondary>probing</secondary></indexterm>
@@ -593,7 +593,7 @@
<listitem>
<para><emphasis>RF_TIMESHARE</emphasis> - resource may be
- time-shared by multiple drivers, i.e. allocated at the
+ time-shared by multiple drivers, i.e., allocated at the
same time by many but activated only by one at any given
moment of time.</para>
</listitem>
@@ -731,7 +731,7 @@
</sect1>
<sect1 id="isa-driver-busmem">
- <title>Bus memory mapping</title>
+ <title>Bus Memory Mapping</title>
<para>In many cases data is exchanged between the driver and the
device through the memory. Two variants are possible:</para>
@@ -849,7 +849,7 @@
the future <function>bus_dmamem_alloc()</function> but
not <function>bus_dmamap_create()</function> calls.
Must be power of 2. If the memory is planned to be used
- in non-cascaded DMA mode (i.e. the DMA addresses will be
+ in non-cascaded DMA mode (i.e., the DMA addresses will be
supplied not by the device itself but by the ISA DMA
controller) then the boundary must be no larger than
64KB (64*1024) due to the limitations of the DMA
More information about the svn-doc-all
mailing list