os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

* Correctly use errorname and literal tags.

Browse source 
* Formally mark up author information in <chapterinfo><authorgroup>..
This commit is contained in:
Murray Stokely 2005-05-04 23:49:08 +00:00
parent 2129a93f77
commit fca3844a99
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24452
1 changed files with 21 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml
View file

@ -5,11 +5,24 @@
-->
<chapter id="scsi">
<title>Common Access Method SCSI Controllers</title>
<chapterinfo>
<authorgroup>
<author>
<firstname>Sergey</firstname>
<surname>Babkin</surname>
<contrib>Written by </contrib>
</author>
</authorgroup>
<authorgroup>
<author>
<firstname>Murray</firstname>
<surname>Stokely</surname>
<contrib>Modifications for Handbook made by </contrib>
</author>
</authorgroup>
</chapterinfo>
<para><emphasis>This chapter was written by &a.babkin;
Modifications for the handbook made by
&a.murray;.</emphasis></para>
<title>Common Access Method SCSI Controllers</title>
<sect1 id="scsi-synopsis">
<title>Synopsis</title>
@ -601,7 +614,7 @@
that we have a pending operation, return the CCB back and ask
CAM to re-queue it. Later when the resources become available
the SIM queue must be unfrozen by returning a ccb with the
<varname>CAM_SIMQ_RELEASE<varname> bit set in its status. Otherwise, if all went
<literal>CAM_SIMQ_RELEASE</literal> bit set in its status. Otherwise, if all went
well, link the CCB with the hardware control block (HCB) and
mark it as queued.</para>
@ -647,7 +660,7 @@
have two separate functions, <function>vtop()</function> and <function>ptobus()</function> then <function>vtobus()</function>
would be a simple superposition of them.] In case if a
physical address is requested it is OK to return the CCB with
the status <errname>CAM_REQ_INVALID</errname>, the current drivers do that. But
the status <errorname>CAM_REQ_INVALID</errorname>, the current drivers do that. But
it is also possible to compile the Alpha-specific piece of
code, as in this example (there should be a more direct way to
do that, without conditional compilation in the drivers). If
@ -697,7 +710,7 @@
handling for the details on the address-translation issues.
If some variation is too difficult or impossible to implement
with a particular card it is OK to return the status
<errname>CAM_REQ_INVALID</errname>. Actually, it seems like the scatter-gather
<errorname>CAM_REQ_INVALID</errorname>. Actually, it seems like the scatter-gather
ability is not used anywhere in the CAM code now. But at least
the case for a single non-scattered virtual buffer must be
implemented, it is actively used by CAM.</para>
@ -805,7 +818,7 @@
request description) and sent to the controller or the SCSI
controller may be immediately programmed to send this RESET
message to the device or this request may be just not supported
(and return the status <errname>CAM_REQ_INVALID</errname>). Also on completion of
(and return the status <errorname>CAM_REQ_INVALID</errorname>). Also on completion of
the request all the disconnected transactions for this target
must be aborted (probably in the interrupt routine).</para>