From owner-man-jp-reviewer@jp.freebsd.org  Fri May 19 21:21:32 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id VAA23263;
	Fri, 19 May 2000 21:21:32 +0900 (JST)
	(envelope-from owner-man-jp-reviewer@jp.FreeBSD.org)
Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.102])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id VAA23258
	for <man-jp-reviewer@jp.freebsd.org>; Fri, 19 May 2000 21:21:31 +0900 (JST)
	(envelope-from takamune@vrl.mei.co.jp)
Received: by bulls.mei.co.jp (8.9.3/3.7W) with ESMTP id VAA25663
	for <man-jp-reviewer@jp.freebsd.org>; Fri, 19 May 2000 21:21:00 +0900 (JST)
Received: by mariners.mei.co.jp (8.9.1/3.7W) with ESMTP id VAA09795
	for <man-jp-reviewer@jp.freebsd.org>; Fri, 19 May 2000 21:21:00 +0900 (JST)
Received: by dream.vrl.mei.co.jp (8.9.3/3.7W-11/29/99)
	id VAA18542; Fri, 19 May 2000 21:20:59 +0900 (JST)
To: man-jp-reviewer@jp.freebsd.org
From: Kazu TAKAMUNE (=?iso-2022-jp?B?GyRCOWI9IU9CNkcbKEI=?=)
 <takamune@avrl.mei.co.jp>
X-Mailer: Mew version 1.94.1 on Emacs 20.6 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-Id: <20000519212059B.takamune@vrl.mei.co.jp>
Date: Fri, 19 May 2000 21:20:59 +0900
X-Dispatcher: imput version 20000228(IM140)
Lines: 423
Reply-To: man-jp-reviewer@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: man-jp-reviewer 2513
Subject: [man-jp-reviewer 2513] scsi.4
Errors-To: owner-man-jp-reviewer@jp.freebsd.org
Sender: owner-man-jp-reviewer@jp.freebsd.org
X-Originator: takamune@vrl.mei.co.jp

$B9b=!$G$9!#(Bscsi.4 $B$N=iLu$G$9!#(B

  o wired (down), counted $B$NNI$$Lu$,$o$+$j$^$;$s!#(B
  o wired, counted $B$NOC$,=P$F$/$kItJ,(B(`$B%+!<%M%k$N@_Dj(B'$B$N%;%/%7%g%s(B
    $B$N:G8e$NJ}(B) $B$NM}2r$,2x$7$$$G$9!#(B

$B::FI$*4j$$$7$^$9!#(B
--
$B9b=!(B $BOB6G(B($B$?$+$`$M(B $B$+$:$H$-(B)
mailto:takamune@avrl.mei.co.jp

--- scsi.4.orig	Mon Feb 15 19:43:56 1999
+++ scsi.4	Fri May 19 21:00:00 2000
@@ -1,4 +1,5 @@
 .\"	$Id: scsi.4,v 1.12 1998/10/16 04:28:39 ken Exp $
+.\" jpman %Id: scsi.4,v 0.0 1999/02/22 16:13:54 horikawa Stab %
 .\" Copyright (c) 1996
 .\"	Julian Elischer <julian@freebsd.org>.  All rights reserved.
 .\"
@@ -27,11 +28,11 @@
 .Dd October 15, 1998
 .Dt SCSI 4
 .Os FreeBSD 3.0
-.Sh NAME
+.Sh $BL>>N(B
 .Nm SCSI ,
 .Nm CAM
-.Nd CAM SCSI subsystem
-.Sh SYNOPSIS
+.Nd CAM SCSI $B%5%V%7%9%F%`(B
+.Sh $B=q<0(B
 .Cd "controller scbus0"
 .Cd "controller scbus1 at ahc0"
 .Cd "controller scbus3 at ahc1 bus 0"
@@ -52,204 +53,228 @@
 .Cd options		SCSI_NO_SENSE_STRINGS
 .Cd options		SCSI_NO_OP_STRINGS
 .Cd options		SCSI_DELAY=8000
-.Sh DESCRIPTION
-The CAM
+.Sh $B2r@b(B
+CAM
 .Tn SCSI
-subsystem provides a uniform and modular system for the implementation
-of drivers to control various
+$B%5%V%7%9%F%`$O!"(B
+$B3F<o$N(B
 .Tn SCSI
-devices, and to utilize different
+$B%G%P%$%9$r@)8f$9$k%I%i%$%P$d!"%[%9%H%"%@%W%?%I%i%$%P$r7PM3$7$F0[$J$k(B
 .Tn SCSI
-host adapters through host adapter drivers. When the system probes the 
+$B%[%9%H%"%@%W%?$rMxMQ$9$k%I%i%$%P$r<BAu$9$k$?$a$N!"(B
+$B6Q<A$G%b%8%e!<%k2=$5$l$?%7%9%F%`$rDs6!$7$^$9!#(B
+$B%7%9%F%`$,(B
 .Tn SCSI
-busses, it attaches any devices it finds to the appropriate
-drivers.  The
+$B%P%9$r%W%m!<%V$7!"H/8+$7$?%G%P%$%9$rE,@Z$J%I%i%$%P$K%"%?%C%A$7$^$9!#(B
 .Xr pass 4
-driver, if it is configured in the kernel, will attach to all
+$B%I%i%$%P$,%+!<%M%k$KAH$_9~$^$l$F$$$l$P!"$9$Y$F$N(B
 .Tn SCSI
-devices.
-.Sh KERNEL CONFIGURATION
-There are a number of generic kernel configuration options for the
+$B%G%P%$%9$,%"%?%C%A$5$l$^$9!#(B
+.Sh $B%+!<%M%k$N@_Dj(B
 CAM
 .Tn SCSI
-subsystem:
+$B%5%V%7%9%F%`MQ$K0lHLE*$J%+!<%M%k@_Dj%*%W%7%g%s$,$$$/$D$+$"$j$^$9(B:
 .Bl -tag -width SCSI_NO_SENSE_STRINGS
 .It Dv CAMDEBUG
-This option enables the CAM debugging printf code.  This won't actually
-cause any debugging information to be printed out when included by itself.
-Enabling printouts requires additional configuration.  See below for
-details.
+$B$3$N%*%W%7%g%s$O!"(BCAM $B%G%P%C%0MQ$N(B printf $B%3!<%I$rM-8z$K$7$^$9!#(B
+$B<B:]$K$O!"$3$N%*%W%7%g%s$@$1$G$O%G%P%C%0>pJs$O=PNO$5$l$^$;$s!#(B
+$B=PNO$9$k$?$a$K$ODI2C@_Dj$,I,MW$G$9!#>\:Y$O2<5-$r;2>H$7$F2<$5$$!#(B
 .It Dv "CAM_MAX_HIGHPOWER=4"
-This sets the maximum allowable number of concurrent "high power" commands.
-A "high power" command is a command that takes more electrical power than
-most to complete.  An example of this (and the only command currently
-tagged as "high power") is the
-.Tn SCSI
-START UNIT command.  Starting a SCSI disk often takes significantly more
-electrical power than normal operation of the disk.  This option allows the
-user to specify how many concurrent high power commands may be outstanding
-without overloading the power supply on his computer.
+$BF1;~;HMQ$G$-$k(B "high power" $B%3%^%s%I$N:GBg?t$r@_Dj$7$^$9!#(B
+"high power" $B%3%^%s%I$H$O!"(B
+$BB>$N%3%^%s%I$KHf$Y$F!"<B9T$9$k$N$K$h$jB?$/$NEENO$rI,MW$H$9$k%3%^%s%I$G$9!#(B
+$B$=$N0lNc$O(B
+.Tn SCSI
+START UNIT $B%3%^%s%I$G$9(B
+($B8=:_$N$H$3$m(B "high power" $B$N_`0u$r2!$5$l$F$$$kM#0l$N%3%^%s%I$G$9(B)$B!#(B
+SCSI $B%G%#%9%/$r5/F0$9$k$K$O!"DL>o$N%G%#%9%/A`:n$KHf$Y$F(B
+$B$+$J$jBg$-$JEENO$r>CHq$7$^$9!#(B
+$B$3$N%*%W%7%g%s$G!"%3%s%T%e!<%?$NEE8;$KIi2Y$r$+$12a$.$:$K(B
+"high power" $B%3%^%s%I$rF1;~$K$$$/$D$^$GH/9T$G$-$k$+$r;XDj$G$-$^$9!#(B
 .It Dv SCSI_NO_SENSE_STRINGS
-This eliminates text descriptions of each
-.Tn SCSI
-Additional Sense Code and Additional Sense Code Qualifier pair.  Since this
-is a fairly large text database, eliminating it reduces the size of the
-kernel somewhat.  This is primarily necessary for boot floppies and other
-low disk space or low memory space environments.  In most cases, though,
-this should be enabled, since it speeds the interpretation of
 .Tn SCSI
-error messages.  Don't let the "kernel bloat" zealots get to you -- leave
-the sense descriptions in your kernel!
+Additional Sense Code $B$H(B Additional Sense Code Qualifier $B$NAH$K$D$$$F$N(B
+$B2r@bJ8$r$9$Y$F=|5n$7$^$9!#(B
+$B$3$NJ8$OK\Ev$KBg$-$J%F%-%9%H%G!<%?%Y!<%9$J$N$G!"(B
+$B=|5n$9$l$P!"%+!<%M%k$N%5%$%:$r>/$7:o8:$G$-$^$9!#(B
+$B$3$N%*%W%7%g%s$O!"<g$H$7$F%V!<%H%U%m%C%T$d!"(B
+$BB>$N%G%#%9%/6u4V$"$k$$$O%a%b%j6u4V$,>.$5$$4D6-$GI,MW$H$J$j$^$9!#(B
+$BB>$N4D6-$G$b!"(B
+$BB?$/$N>l9g$O$3$N%*%W%7%g%s$rM-8z$K$9$Y$-$G$9!#(B
+.Tn SCSI
+$B$N%(%i!<%a%C%;!<%8$N2r<a$rB.$a$k$3$H$K$J$k$+$i$G$9!#(B
+$B%+!<%M%k$rL5MQ$KKDD%(B ("kernel bloat") $B$5$;$k$3$H$P$+$j$KG.Cf$7$J$$$G!"(B
+$B$"$J$?$N%+!<%M%k$K2r@bJ8$r;D$5$J$$$h$&$K$7$^$7$g$&(B!
 .It Dv SCSI_NO_OP_STRINGS
-This disables text descriptions of each
 .Tn SCSI
-opcode.  This option, like the sense string option above, is primarily
-useful for environments like a boot floppy where kernel size is critical.
-Enabling this option for normal use isn't recommended, since it slows
-debugging of
+opcode $B$N2r@bJ8$r$9$Y$FL58z$K$7$^$9!#(B
+$B$3$N%*%W%7%g%s$O!"A0=R$7$?(B sense $BJ8;zNs$H>l9g$HF1MM!"<g$H$7$F(B
+$B%+!<%M%k%5%$%:$,$-$o$I$$%V!<%H%U%m%C%T$N$h$&$J4D6-$GLr$KN)$A$^$9!#(B
+$BDL>o$N;HMQ4D6-$G$3$N%*%W%7%g%s$rM-8z$K$9$k$3$H$O?d>)$5$l$^$;$s!#(B
 .Tn SCSI
-problems.
+$B$N>c32$N%G%P%C%0$rCY$i$;$k$+$i$G$9!#(B
 .It Dv SCSI_DELAY=8000
-This is the
-.Tn SCSI
-"bus settle delay."  In CAM, it is specified in
-.Em milliseconds ,
-not seconds like the old
-.Tn SCSI
-layer used to do.  When the kernel boots, it sends a bus reset to each
 .Tn SCSI
-bus to tell each device to reset itself to a default set of transfer
-negotiations and other settings.  Most
-.Tn SCSI
-devices need some amount of time to recover from a bus reset.  Newer disks
-may need as little as 100ms, while old, slow devices may need much longer.
-If the
+$B$N%P%9D4DjCY1d(B ("bus settle delay") $B$G$9!#(B
+CAM $B$N>l9g!"(B
+.Em $B%_%jIC(B
+$BC10L$G;XDj$7$^$9!#(B
+$B0JA0$N(B
+.Tn SCSI
+$BAX$G;H$o$l$F$$$?ICC10L$G$O$"$j$^$;$s!#(B
+$B%+!<%M%k$O%V!<%H;~$K%P%9%j%;%C%H$r3F(B
+.Tn SCSI
+$B%P%9$KAw$j!"3F%G%P%$%9$,E>Aw%M%4%7%(!<%7%g%s$d$=$NB>$N@_Dj$r(B
+$B%G%U%)%k%H$N>uBV$K<+J,<+?H$G%j%;%C%H$9$k$h$&DLCN$7$^$9!#(B
+$B$[$H$s$I$N(B
+.Tn SCSI
+$B%G%P%$%9$O!"%P%9%j%;%C%H$+$iI|5"$9$k$N$K!"$"$kDxEY$N;~4V$rI,MW$H$7$^$9!#(B
+$B:G6a$N%G%#%9%/$O(B 100ms $BDxEY$NC;$+$$;~4V$7$+I,MW$H$7$^$;$s$,!"(B
+$B8E$/$FCY$$%G%P%$%9$O$b$C$HD9$$;~4V$rI,MW$H$9$k$+$b$7$l$^$;$s!#(B
 .Dv SCSI_DELAY
-isn't specified, it defaults to 2 seconds.  The minimum allowable value for
+$B$r;XDj$7$J$1$l$P!"%G%U%)%k%H$G$O(B 2 $BIC$K$J$j$^$9!#(B
 .Dv SCSI_DELAY
-is "100", or 100ms.  One special case is that if the
+$B$N:G>.CM$O(B "100"$B!"$9$J$o$A(B 100ms $B$G$9!#(B
+$BM#0lFC<l$J%1!<%9$O(B
 .Dv SCSI_DELAY
-is set to 0, that will be taken to mean the "lowest possible value."  In
-that case, the
+$B$K(B 0 $B$r;XDj$7$?>l9g$G!"(B"$B$G$-$k$@$1>.$5$$CM(B" $B$r0UL#$7$^$9!#(B
+$B$3$N>l9g!"(B
 .Dv SCSI_DELAY
-will be reset to 100ms.
+$B$O(B 100ms $B$K%j%;%C%H$5$l$^$9!#(B
 .El
 .Pp
-All devices and the SCSI busses support boot time allocation so that
-an upper number of devices and controllers does not need to be configured;
+$B$9$Y$F$N%G%P%$%9$*$h$S(B SCSI $B%P%9$O%V!<%H;~$N3dEv$F$r%5%]!<%H$7$F$$$k$N$G!"(B
+$B>e0L$NHV9f$N%G%P%$%9$*$h$S%3%s%H%m!<%i$r@_Dj$9$kI,MW$O$"$j$^$;$s(B;
 .Cd "device da0"
-will suffice for any number of disk drivers.
+$B$OG$0U$NHV9f$N%G%#%9%/%I%i%$%P$KBP$7$F==J,$J5-=R$G$9!#(B
 .Pp
-The devices are either
+$B%G%P%$%9$O!"FCDj$N%G%P%$%9%f%K%C%H$H$7$FG'<1$5$l$k(B
 .Em wired
-so they appear as a particular device unit or
+$B$+!"(B
+$B$=$N<!$KM-8z$JL$;HMQ%f%K%C%H$H$7$FG'<1$5$l$k(B
 .Em counted
-so that they appear as the next available unused unit.
+$B$N$I$A$i$+$G$9!#(B
 .Pp
-To configure a driver in the kernel without wiring down the device use a
-config line similar to
+$B%+!<%M%kFb$N%I%i%$%P$,%G%P%$%9$rB+G{$7$J$$$h$&$K@_Dj$9$k$K$O!"(B
 .Cd "device ch0"
-to include the changer driver.
+$B$N$h$&$J@_Dj9T$r5-=R$7$F!"%A%'%s%8%c%I%i%$%P$rAH$_9~$s$G2<$5$$!#(B
 .Pp
-To wire down a unit use a config line similar to
+$B%f%K%C%H$rB+G{$9$k$K$O!"(B
 .Cd "device ch1 at scbus0 target 4 unit 0"
-to assign changer 1 as the changer with SCSI ID 4,
-SCSI logical unit 0 on SCSI bus 0.
-Individual scbuses can be wired down to specific controllers with
-a config line similar to
+$B$N$h$&$J@_Dj9T$r5-=R$7$F!"(B
+$B%A%'%s%8%c(B 1 $B$r(B SCSI $B%P%9(B 0 $B>e$N(B SCSI ID 4$B!"(BSCSI $BO@M}%f%K%C%H(B 0 $B$N(B
+$B%A%'%s%8%c$K3d$jEv$F$^$9!#(B
+$B3F(B SCSI $B%P%9$r;XDj$7$?%3%s%H%m!<%i$KB+G{$9$k$K$O!"(B
 .Cd "controller scbus0 at ahc0"
-which assigns scsi bus 0 to the first unit using the ahc driver.
-For controllers supporting more than one bus,
-the particular bus can be specified as in
+$B$N$h$&$K@_Dj9T$r5-=R$7$^$9!#(B
+$B$3$l$O!"(BSCSI $B%P%9(B 0 $B$r(B ahc $B%I%i%$%P$rMQ$$$k:G=i$N%f%K%C%H$K3d$jEv$F$^$9!#(B
+$BJ#?t$N%P%9$r%5%]!<%H$9$k%3%s%H%m!<%i$N>l9g!"(B
+$BFCDj$N%P%9$r(B
 .Cd "controller scbus3 at ahc1 bus 1"
-which assigns scbus 1 to the second bus probed on the ahc1 device.
+$B$N7A<0$G;XDj$G$-$^$9!#(B
+$B$3$l$O!"(BSCSI $B%P%9(B 1 $B$r(B ahc1 $B%G%P%$%9>e$G(B 2 $BHVL\$K%W%m!<%V$5$l$?%P%9$K(B
+$B3d$jEv$F$^$9!#(B
 .Pp
-When you have a mixture of wired down and counted devices then the
-counting begins with the first non-wired down unit for a particular
-type.  That is, if you have a disk wired down as
-.Em "device da1" ,
-then the first non-wired disk shall come on line as
-.Em da2 .
-.Sh ADAPTERS
-The system allows common device drivers to work through many different
-types of adapters. The adapters take requests from the upper layers and do
-all IO between the 
+wired $B%G%P%$%9$H(B counted $B%G%P%$%9$,:.:_$7$F$$$k>l9g!"(B
+$B$=$N%G%P%$%9%?%$%W$K$D$$$F$N:G=i$NHs(B wired $B%f%K%C%H$+$i?t$(;O$a$^$9!#(B
+$B$9$J$o$A!"(Bwired $B%G%#%9%/(B
+.Em "device da1"
+$B$,$"$k$H!":G=i$NHs(B wired $B%G%#%9%/$O(B
+.Em da2
+$B$H$7$FG'<1$5$l$k$3$H$K$J$j$^$9!#(B
+.Sh $B%"%@%W%?(B
+$B$3$N%7%9%F%`$G$O!"$?$/$5$s$N<oN`$N0[$J$k%"%@%W%?$K(B
+$B6&DL$N%G%P%$%9%I%i%$%P$r;HMQ$9$k$3$H$,2DG=$G$9!#(B
+$B%"%@%W%?$O>e0LAX$+$iMW5a$r<u$1$F!"(B
 .Em SCSI
-bus and the system. The maximum size of a transfer is governed by the
-adapter. Most adapters can transfer 64KB in a single operation, however
-many can transfer larger amounts.
-.Sh TARGET MODE
-Some adapters support 
-.Em target mode
-in which the system is capable of operating as a device, responding to
-operations initiated by another system. Target mode is supported for
-some adapters, but is not yet complete for this version of the CAM
-.Tn SCSI
-subsystem.
-.Sh FILES
-see other scsi device entries.
-.Sh DIAGNOSTICS
-When the kernel is compiled with options CAMDEBUG, an XPT_DEBUG CCB can be
-used to enable various amounts of tracing information on any 
-specific device. Devices not being traced will not produce trace information.
-There are currently four debugging flags that may be turned on:
+$B%P%9$H%7%9%F%`$N4V$N$9$Y$F$N(B IO $B$r<B9T$7$^$9!#(B
+$BE>Aw$N:GBg%5%$%:$O%"%@%W%?$K$h$C$F;YG[$5$l$^$9!#(B
+$B$[$H$s$I$N%"%@%W%?$,0lEY$NA`:n$G(B 64KB $B$rE>Aw$G$-$^$9$,!"(B
+$BB?$/$N%"%@%W%?$O$b$C$HBgNL$KE>Aw$G$-$k$+$b$7$l$^$;$s!#(B
+.Sh $B%?!<%2%C%H%b!<%I(B
+$B$$$/$D$+$N%"%@%W%?$O!"(B
+.Em $B%?!<%2%C%H%b!<%I(B
+$B$r%5%]!<%H$7$F$$$^$9!#(B
+$B$3$N%b!<%I$G$O!"(B
+$B%7%9%F%`$r$R$H$D$N%G%P%$%9$H$7$FA`:n$9$k$3$H$,2DG=$H$J$j!"(B
+$BJL$N%7%9%F%`$,H/9T$7$?A`:n$K1~Ez$9$k$h$&$K$J$j$^$9!#(B
+$B%?!<%2%C%H%b!<%I$O!"$$$D$/$+$N%"%@%W%?$G%5%]!<%H$5$l$F$$$^$9$,!"(B
+$B$3$N%P!<%8%g%s$N(B CAM
+.Tn SCSI
+$B%5%V%7%9%F%`$G$O$^$@40A4$G$O$"$j$^$;$s!#(B
+.Sh $B4XO"%U%!%$%k(B
+$BB>$N(B SCSI $B%G%P%$%9$N%(%s%H%j$r;2>H$7$F2<$5$$!#(B
+.Sh $B?GCG(B
+$B%+!<%M%k$,(B options CAMDEBUG $BIU$-$G%3%s%Q%$%k$5$l$F$$$k>l9g!"(B
+XPT_DEBUG CCB $B$rMQ$$$l$P!"(B
+$BG$0U$N;XDj$7$?%G%P%$%9$K4X$7$F!"$5$^$6$^$JNL$N%H%l!<%9>pJs$r(B
+$B<hF@2DG=$K$J$j$^$9!#(B
+$B%H%l!<%9$5$l$F$$$J$$%G%P%$%9$O%H%l!<%9>pJs$r@8@.$7$^$;$s!#(B
+$B8=:_$O(B 4 $B$D$N%G%P%C%0%U%i%0$r%*%s$K$G$-$^$9(B:
 .Bl -tag -width CAM_DEBUG_SUBTRACE
 .It Dv CAM_DEBUG_INFO
-This debugging flag enables general informational printfs for the device
-or devices in question.
+$B3:Ev$9$k%G%P%$%9(B ($B72(B) $B$K$D$$$F0lHLE*$J>pJs$N(B printf $B=PNO$,2DG=$K$J$j$^$9!#(B
 .It Dv CAM_DEBUG_TRACE
-This debugging flag enables function-level command flow tracing.  i.e.
-kernel printfs will happen at the entrance and exit of various functions.
+$B4X?t%l%Y%k$G$N%3%^%s%I%U%m!<$N%H%l!<%9$,2DG=$K$J$j$^$9!#(B
+$B$9$J$o$A!"4X?t$NF~8}$H=P8}$G%+!<%M%k$N(B printf $B=PNO$,H/@8$7$^$9!#(B
 .It Dv CAM_DEBUG_SUBTRACE
-This debugging flag enables debugging output internal to various functions.
+$B4X?tFbIt$G$N%G%P%C%0=PNO$,2DG=$K$J$j$^$9!#(B
 .It Dv CAM_DEBUG_CDB
-This debugging flag will cause the kernel to print out all
+$BFCDj$N%G%P%$%9(B ($B72(B) $B$KAw?.$5$l$?$9$Y$F$N(B
 .Tn SCSI
-commands sent to a particular device or devices.
+$B%3%^%s%I$r%+!<%M%k$,0u;z$9$k$h$&$K$J$j$^$9!#(B
 .El
 .Pp
-Some of these flags, most notably
+$B$3$l$i$N%U%i%0$N$&$A!"FC$K(B
 .Dv CAM_DEBUG_TRACE
-and
+$B$H(B
 .Dv CAM_DEBUG_SUBTRACE
-will produce kernel printfs in EXTREME numbers.  Because of that, they
-aren't especially useful.  There aren't many things logged at the
+$B$OKDBg$JNL$N%+!<%M%k$N(B printf $B=PNO$rH/@8$7$^$9$N$G!"(B
+$B$"$^$jM-1W$G$O$"$j$^$;$s!#(B
 .Dv CAM_DEBUG_INFO
-level, so it isn't especially useful.  The most useful debugging flag is
-the
+$B$N%l%Y%k$G%m%0=PNO$5$l$k$b$N$OB?$/$O$"$j$^$;$s$N$G!"(B
+$B$3$l$b$=$l$[$IM-1W$G$O$"$j$^$;$s!#(B
+$B:G$bM-1W$J%G%P%C%0%U%i%0$O(B
 .Dv CAM_DEBUG_CDB
-flag.  Users can enable debugging from their kernel config file, by using
-the following kernel config options:
+$B%U%i%0$G$9!#(B
+$B0J2<$N%+!<%M%k%*%W%7%g%s$r;HMQ$7$F!"(B
+$B%+!<%M%k@_Dj%U%!%$%k$+$i%G%P%C%0$rM-8z$K$G$-$^$9(B:
 .Bl -tag -width CAM_DEBUG_TARGET
 .It Dv CAMDEBUG
-This enables CAM debugging.  Without this option, users will not even be able
-to turn on debugging from userland via
-.Xr camcontrol 8 .
+CAM $B$N%G%P%C%0$rM-8z$K$7$^$9!#(B
+$B$3$N%*%W%7%g%s$J$7$G$O!"%f!<%6%i%s%I$+$i(B
+.Xr camcontrol 8
+$B$r7PM3$7$F%G%P%C%0$rM-8z$K$9$k$3$H$b$G$-$^$;$s!#(B
 .It Dv CAM_DEBUG_FLAGS
-This allows the user to set the various debugging flags described above
-in a kernel config file.  Flags may be ORed together if the user wishes to
-see printfs for multiple debugging levels.
+$B>e$K=R$Y$?$h$&$J3F<o$N%G%P%C%0%U%i%0$r!"(B
+$B%+!<%M%k@_Dj%U%!%$%k$G@_Dj$9$k$3$H$,2DG=$K$J$j$^$9!#(B
+$B%U%i%0$NO@M}OB$r<h$l$P!"(B
+$BJ#?t$N%G%P%C%0%l%Y%k$G$N(B printf $B=PNO$r8+$k$3$H$b$G$-$^$9!#(B
 .It Dv CAM_DEBUG_BUS
-Specify a bus to debug.  To debug all busses, set this to -1.
+$B%G%P%C%0$NBP>]$H$9$k%P%9$r;XDj$7$^$9!#(B
+$B$9$Y$F$N%P%9$r%G%P%C%0$9$k$K$O!"$3$NCM$r(B -1 $B$K@_Dj$7$^$9!#(B
 .It Dv CAM_DEBUG_TARGET
-Specify a target to debug.  To debug all targets, set this to -1.
+$B%G%P%C%0$NBP>]$H$9$k%?!<%2%C%H$r;XDj$7$^$9!#(B
+$B$9$Y$F$N%?!<%2%C%H$r%G%P%C%0$9$k$K$O!"$3$NCM$r(B -1 $B$K@_Dj$7$^$9!#(B
 .It Dv CAM_DEBUG_LUN
-Specify a lun to debug.  To debug all luns, set this to -1.
+$B%G%P%C%0$NBP>]$H$9$kO@M}%f%K%C%HHV9f$r;XDj$7$^$9!#(B
+$B$9$Y$F$NO@M}%f%K%C%HHV9f$r%G%P%C%0$9$k$K$O!"$3$NCM$r(B -1 $B$K@_Dj$7$^$9!#(B
 .El
 .Pp
-When specifying a bus, target or lun to debug, you
-.Em MUST
-specify all three bus/target/lun options above.  Using wildcards, you
-should be able to enable debugging on most anything.
+$B$"$k%P%9!"%?!<%2%C%H!"$b$7$/$OO@M}%f%K%C%HHV9f$r;XDj$9$k>l9g$K$O!"(B
+$B>e=R$7$?(B 3 $B$D$N%P%9(B/$B%?!<%2%C%H(B/$BO@M}%f%K%C%HHV9f$N%*%W%7%g%s$r(B
+$B$9$Y$F;XDj$9$k$3$H$,I,?\$H$J$j$^$9!#(B
+$B%o%$%k%I%+!<%I$r;HMQ$9$l$P!"(B
+$B$[$H$s$I$N5!4o$K$D$$$F%G%P%C%0$rM-8z$K$9$k$3$H$,$G$-$^$9!#(B
 .Pp
-Users may also enable debugging printfs on the fly, if the
 .Dv CAMDEBUG
-option is their config file, by using the
+$B%*%W%7%g%s$r@_Dj%U%!%$%k$K4^$a$F$$$l$P!"(B
 .Xr camcontrol 8
-utility.  See
+$B%f!<%F%#%j%F%#$r;HMQ$7$F!"5/F0Cf$K(B printf $B%G%P%C%0$rM-8z$K$9$k$3$H$b$G$-$^$9!#(B
+$B>\:Y$O(B
 .Xr camcontrol 8
-for details.
-.Sh SEE ALSO
+$B$r;2>H$7$F2<$5$$!#(B
+.Sh $B4XO"9`L\(B
 .Xr aha 4 ,
 .Xr ahb 4 ,
 .Xr ahc 4 ,
@@ -262,13 +287,13 @@
 .Xr sa 4 ,
 .Xr xpt 4 ,
 .Xr camcontrol 8
-.Sh HISTORY
-The CAM
+.Sh $BNr;K(B
+CAM
 .Tn SCSI
-subsystem first appeared in
-.Fx 3.0 .
-.Sh AUTHORS
-The CAM
+$B%5%V%7%9%F%`$O(B
+.Fx 3.0
+$B$G=i$a$FEP>l$7$^$7$?!#(B
+.Sh $B:n<T(B
+CAM
 .Tn SCSI
-subsystem was written by Justin Gibbs and Kenneth Merry.
-
+$B%5%V%7%9%F%`$O(B Justin Gibbs $B$H(B Kenneth Merry $B$K$h$C$F=q$+$l$^$7$?!#(B
