€•®¸      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ$/translations/zh_CN/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ$/translations/zh_TW/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ$/translations/it_IT/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ$/translations/ja_JP/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ$/translations/ko_KR/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ$/translations/sp_SP/usb/mass-storage”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒMass Storage Gadget (MSG)”h]”hŒMass Storage Gadget (MSG)”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ>/var/lib/git/docbuild/linux/Documentation/usb/mass-storage.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒOverview”h]”hŒOverview”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒblock_quote”“”)”}”(hX®  Mass Storage Gadget (or MSG) acts as a USB Mass Storage device,
appearing to the host as a disk or a CD-ROM drive.  It supports
multiple logical units (LUNs).  Backing storage for each LUN is
provided by a regular file or a block device, access can be limited
to read-only, and gadget can indicate that it is removable and/or
CD-ROM (the latter implies read-only access).

Its requirements are modest; only a bulk-in and a bulk-out endpoint
are needed.  The memory requirement amounts to two 16K buffers.
Support is included for full-speed, high-speed and SuperSpeed
operation.

Note that the driver is slightly non-portable in that it assumes
a single memory/DMA buffer will be usable for bulk-in and bulk-out
endpoints.  With most device controllers this is not an issue, but
there may be some with hardware restrictions that prevent a buffer
from being used by more than one endpoint.

This document describes how to use the gadget from user space, its
relation to mass storage function (or MSF) and different gadgets
using it, and how it differs from File Storage Gadget (or FSG)
(which is no longer included in Linux).  It will talk only briefly
about how to use MSF within composite gadgets.
”h]”(hŒ	paragraph”“”)”}”(hXs  Mass Storage Gadget (or MSG) acts as a USB Mass Storage device,
appearing to the host as a disk or a CD-ROM drive.  It supports
multiple logical units (LUNs).  Backing storage for each LUN is
provided by a regular file or a block device, access can be limited
to read-only, and gadget can indicate that it is removable and/or
CD-ROM (the latter implies read-only access).”h]”hXs  Mass Storage Gadget (or MSG) acts as a USB Mass Storage device,
appearing to the host as a disk or a CD-ROM drive.  It supports
multiple logical units (LUNs).  Backing storage for each LUN is
provided by a regular file or a block device, access can be limited
to read-only, and gadget can indicate that it is removable and/or
CD-ROM (the latter implies read-only access).”…””}”(hhÐhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhÊubhÏ)”}”(hŒÌIts requirements are modest; only a bulk-in and a bulk-out endpoint
are needed.  The memory requirement amounts to two 16K buffers.
Support is included for full-speed, high-speed and SuperSpeed
operation.”h]”hŒÌIts requirements are modest; only a bulk-in and a bulk-out endpoint
are needed.  The memory requirement amounts to two 16K buffers.
Support is included for full-speed, high-speed and SuperSpeed
operation.”…””}”(hhÞhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhÊubhÏ)”}”(hX4  Note that the driver is slightly non-portable in that it assumes
a single memory/DMA buffer will be usable for bulk-in and bulk-out
endpoints.  With most device controllers this is not an issue, but
there may be some with hardware restrictions that prevent a buffer
from being used by more than one endpoint.”h]”hX4  Note that the driver is slightly non-portable in that it assumes
a single memory/DMA buffer will be usable for bulk-in and bulk-out
endpoints.  With most device controllers this is not an issue, but
there may be some with hardware restrictions that prevent a buffer
from being used by more than one endpoint.”…””}”(hhìhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhÊubhÏ)”}”(hX4  This document describes how to use the gadget from user space, its
relation to mass storage function (or MSF) and different gadgets
using it, and how it differs from File Storage Gadget (or FSG)
(which is no longer included in Linux).  It will talk only briefly
about how to use MSF within composite gadgets.”h]”hX4  This document describes how to use the gadget from user space, its
relation to mass storage function (or MSF) and different gadgets
using it, and how it differs from File Storage Gadget (or FSG)
(which is no longer included in Linux).  It will talk only briefly
about how to use MSF within composite gadgets.”…””}”(hhúhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhhÊubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒModule parameters”h]”hŒModule parameters”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h K!ubhÉ)”}”(hX  The mass storage gadget accepts the following mass storage specific
module parameters:

- file=filename[,filename...]

  This parameter lists paths to files or block devices used for
  backing storage for each logical unit.  There may be at most
  FSG_MAX_LUNS (8) LUNs set.  If more files are specified, they will
  be silently ignored.  See also â€œlunsâ€ parameter.

  *BEWARE* that if a file is used as a backing storage, it may not
  be modified by any other process.  This is because the host
  assumes the data does not change without its knowledge.  It may be
  read, but (if the logical unit is writable) due to buffering on
  the host side, the contents are not well defined.

  The size of the logical unit will be rounded down to a full
  logical block.  The logical block size is 2048 bytes for LUNs
  simulating CD-ROM, block size of the device if the backing file is
  a block device, or 512 bytes otherwise.

- removable=b[,b...]

  This parameter specifies whether each logical unit should be
  removable.  â€œbâ€ here is either â€œyâ€, â€œYâ€ or â€œ1â€ for true or â€œnâ€,
  â€œNâ€ or â€œ0â€ for false.

  If this option is set for a logical unit, gadget will accept an
  â€œejectâ€ SCSI request (Start/Stop Unit).  When it is sent, the
  backing file will be closed to simulate ejection and the logical
  unit will not be mountable by the host until a new backing file is
  specified by userspace on the device (see â€œsysfs entriesâ€
  section).

  If a logical unit is not removable (the default), a backing file
  must be specified for it with the â€œfileâ€ parameter as the module
  is loaded.  The same applies if the module is built in, no
  exceptions.

  The default value of the flag is false, *HOWEVER* it used to be
  true.  This has been changed to better match File Storage Gadget
  and because it seems like a saner default after all.  Thus to
  maintain compatibility with older kernels, it's best to specify
  the default values.  Also, if one relied on old default, explicit
  â€œnâ€ needs to be specified now.

  Note that â€œremovableâ€ means the logical unit's media can be
  ejected or removed (as is true for a CD-ROM drive or a card
  reader).  It does *not* mean that the entire gadget can be
  unplugged from the host; the proper term for that is
  â€œhot-unpluggableâ€.

- cdrom=b[,b...]

  This parameter specifies whether each logical unit should simulate
  CD-ROM.  The default is false.

- ro=b[,b...]

  This parameter specifies whether each logical unit should be
  reported as read only.  This will prevent host from modifying the
  backing files.

  Note that if this flag for given logical unit is false but the
  backing file could not be opened in read/write mode, the gadget
  will fall back to read only mode anyway.

  The default value for non-CD-ROM logical units is false; for
  logical units simulating CD-ROM it is forced to true.

- nofua=b[,b...]

  This parameter specifies whether FUA flag should be ignored in SCSI
  Write10 and Write12 commands sent to given logical units.

  MS Windows mounts removable storage in â€œRemoval optimised modeâ€ by
  default.  All the writes to the media are synchronous, which is
  achieved by setting the FUA (Force Unit Access) bit in SCSI
  Write(10,12) commands.  This forces each write to wait until the
  data has actually been written out and prevents I/O requests
  aggregation in block layer dramatically decreasing performance.

  Note that this may mean that if the device is powered from USB and
  the user unplugs the device without unmounting it first (which at
  least some Windows users do), the data may be lost.

  The default value is false.

- luns=N

  This parameter specifies number of logical units the gadget will
  have.  It is limited by FSG_MAX_LUNS (8) and higher value will be
  capped.

  If this parameter is provided, and the number of files specified
  in â€œfileâ€ argument is greater then the value of â€œlunsâ€, all excess
  files will be ignored.

  If this parameter is not present, the number of logical units will
  be deduced from the number of files specified in the â€œfileâ€
  parameter.  If the file parameter is missing as well, one is
  assumed.

- stall=b

  Specifies whether the gadget is allowed to halt bulk endpoints.
  The default is determined according to the type of USB device
  controller, but usually true.

In addition to the above, the gadget also accepts the following
parameters defined by the composite framework (they are common to
all composite gadgets so just a quick listing):

- idVendor      -- USB Vendor ID (16 bit integer)
- idProduct     -- USB Product ID (16 bit integer)
- bcdDevice     -- USB Device version (BCD) (16 bit integer)
- iManufacturer -- USB Manufacturer string (string)
- iProduct      -- USB Product string (string)
- iSerialNumber -- SerialNumber string (string)
”h]”(hÏ)”}”(hŒVThe mass storage gadget accepts the following mass storage specific
module parameters:”h]”hŒVThe mass storage gadget accepts the following mass storage specific
module parameters:”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K#hj'  ubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX)  file=filename[,filename...]

This parameter lists paths to files or block devices used for
backing storage for each logical unit.  There may be at most
FSG_MAX_LUNS (8) LUNs set.  If more files are specified, they will
be silently ignored.  See also â€œlunsâ€ parameter.

*BEWARE* that if a file is used as a backing storage, it may not
be modified by any other process.  This is because the host
assumes the data does not change without its knowledge.  It may be
read, but (if the logical unit is writable) due to buffering on
the host side, the contents are not well defined.

The size of the logical unit will be rounded down to a full
logical block.  The logical block size is 2048 bytes for LUNs
simulating CD-ROM, block size of the device if the backing file is
a block device, or 512 bytes otherwise.
”h]”(hÏ)”}”(hŒfile=filename[,filename...]”h]”hŒfile=filename[,filename...]”…””}”(hjD  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K&hj@  ubhÏ)”}”(hŒòThis parameter lists paths to files or block devices used for
backing storage for each logical unit.  There may be at most
FSG_MAX_LUNS (8) LUNs set.  If more files are specified, they will
be silently ignored.  See also â€œlunsâ€ parameter.”h]”hŒòThis parameter lists paths to files or block devices used for
backing storage for each logical unit.  There may be at most
FSG_MAX_LUNS (8) LUNs set.  If more files are specified, they will
be silently ignored.  See also â€œlunsâ€ parameter.”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K(hj@  ubhÏ)”}”(hX1  *BEWARE* that if a file is used as a backing storage, it may not
be modified by any other process.  This is because the host
assumes the data does not change without its knowledge.  It may be
read, but (if the logical unit is writable) due to buffering on
the host side, the contents are not well defined.”h]”(hŒemphasis”“”)”}”(hŒ*BEWARE*”h]”hŒBEWARE”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  hj`  ubhX)   that if a file is used as a backing storage, it may not
be modified by any other process.  This is because the host
assumes the data does not change without its knowledge.  It may be
read, but (if the logical unit is writable) due to buffering on
the host side, the contents are not well defined.”…””}”(hj`  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K-hj@  ubhÏ)”}”(hŒäThe size of the logical unit will be rounded down to a full
logical block.  The logical block size is 2048 bytes for LUNs
simulating CD-ROM, block size of the device if the backing file is
a block device, or 512 bytes otherwise.”h]”hŒäThe size of the logical unit will be rounded down to a full
logical block.  The logical block size is 2048 bytes for LUNs
simulating CD-ROM, block size of the device if the backing file is
a block device, or 512 bytes otherwise.”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K3hj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hXI  removable=b[,b...]

This parameter specifies whether each logical unit should be
removable.  â€œbâ€ here is either â€œyâ€, â€œYâ€ or â€œ1â€ for true or â€œnâ€,
â€œNâ€ or â€œ0â€ for false.

If this option is set for a logical unit, gadget will accept an
â€œejectâ€ SCSI request (Start/Stop Unit).  When it is sent, the
backing file will be closed to simulate ejection and the logical
unit will not be mountable by the host until a new backing file is
specified by userspace on the device (see â€œsysfs entriesâ€
section).

If a logical unit is not removable (the default), a backing file
must be specified for it with the â€œfileâ€ parameter as the module
is loaded.  The same applies if the module is built in, no
exceptions.

The default value of the flag is false, *HOWEVER* it used to be
true.  This has been changed to better match File Storage Gadget
and because it seems like a saner default after all.  Thus to
maintain compatibility with older kernels, it's best to specify
the default values.  Also, if one relied on old default, explicit
â€œnâ€ needs to be specified now.

Note that â€œremovableâ€ means the logical unit's media can be
ejected or removed (as is true for a CD-ROM drive or a card
reader).  It does *not* mean that the entire gadget can be
unplugged from the host; the proper term for that is
â€œhot-unpluggableâ€.
”h]”(hÏ)”}”(hŒremovable=b[,b...]”h]”hŒremovable=b[,b...]”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K8hj’  ubhÏ)”}”(hŒ®This parameter specifies whether each logical unit should be
removable.  â€œbâ€ here is either â€œyâ€, â€œYâ€ or â€œ1â€ for true or â€œnâ€,
â€œNâ€ or â€œ0â€ for false.”h]”hŒ®This parameter specifies whether each logical unit should be
removable.  â€œbâ€ here is either â€œyâ€, â€œYâ€ or â€œ1â€ for true or â€œnâ€,
â€œNâ€ or â€œ0â€ for false.”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K:hj’  ubhÏ)”}”(hXM  If this option is set for a logical unit, gadget will accept an
â€œejectâ€ SCSI request (Start/Stop Unit).  When it is sent, the
backing file will be closed to simulate ejection and the logical
unit will not be mountable by the host until a new backing file is
specified by userspace on the device (see â€œsysfs entriesâ€
section).”h]”hXM  If this option is set for a logical unit, gadget will accept an
â€œejectâ€ SCSI request (Start/Stop Unit).  When it is sent, the
backing file will be closed to simulate ejection and the logical
unit will not be mountable by the host until a new backing file is
specified by userspace on the device (see â€œsysfs entriesâ€
section).”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K>hj’  ubhÏ)”}”(hŒÌIf a logical unit is not removable (the default), a backing file
must be specified for it with the â€œfileâ€ parameter as the module
is loaded.  The same applies if the module is built in, no
exceptions.”h]”hŒÌIf a logical unit is not removable (the default), a backing file
must be specified for it with the â€œfileâ€ parameter as the module
is loaded.  The same applies if the module is built in, no
exceptions.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KEhj’  ubhÏ)”}”(hXc  The default value of the flag is false, *HOWEVER* it used to be
true.  This has been changed to better match File Storage Gadget
and because it seems like a saner default after all.  Thus to
maintain compatibility with older kernels, it's best to specify
the default values.  Also, if one relied on old default, explicit
â€œnâ€ needs to be specified now.”h]”(hŒ(The default value of the flag is false, ”…””}”(hjÎ  hžhhŸNh Nubje  )”}”(hŒ	*HOWEVER*”h]”hŒHOWEVER”…””}”(hjÖ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  hjÎ  ubhX4   it used to be
true.  This has been changed to better match File Storage Gadget
and because it seems like a saner default after all.  Thus to
maintain compatibility with older kernels, itâ€™s best to specify
the default values.  Also, if one relied on old default, explicit
â€œnâ€ needs to be specified now.”…””}”(hjÎ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KJhj’  ubhÏ)”}”(hX  Note that â€œremovableâ€ means the logical unit's media can be
ejected or removed (as is true for a CD-ROM drive or a card
reader).  It does *not* mean that the entire gadget can be
unplugged from the host; the proper term for that is
â€œhot-unpluggableâ€.”h]”(hŒNote that â€œremovableâ€ means the logical unitâ€™s media can be
ejected or removed (as is true for a CD-ROM drive or a card
reader).  It does ”…””}”(hjî  hžhhŸNh Nubje  )”}”(hŒ*not*”h]”hŒnot”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jd  hjî  ubhŒo mean that the entire gadget can be
unplugged from the host; the proper term for that is
â€œhot-unpluggableâ€.”…””}”(hjî  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KQhj’  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hŒrcdrom=b[,b...]

This parameter specifies whether each logical unit should simulate
CD-ROM.  The default is false.
”h]”(hÏ)”}”(hŒcdrom=b[,b...]”h]”hŒcdrom=b[,b...]”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KWhj  ubhÏ)”}”(hŒaThis parameter specifies whether each logical unit should simulate
CD-ROM.  The default is false.”h]”hŒaThis parameter specifies whether each logical unit should simulate
CD-ROM.  The default is false.”…””}”(hj&  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KYhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hX¸  ro=b[,b...]

This parameter specifies whether each logical unit should be
reported as read only.  This will prevent host from modifying the
backing files.

Note that if this flag for given logical unit is false but the
backing file could not be opened in read/write mode, the gadget
will fall back to read only mode anyway.

The default value for non-CD-ROM logical units is false; for
logical units simulating CD-ROM it is forced to true.
”h]”(hÏ)”}”(hŒro=b[,b...]”h]”hŒro=b[,b...]”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K\hj:  ubhÏ)”}”(hŒThis parameter specifies whether each logical unit should be
reported as read only.  This will prevent host from modifying the
backing files.”h]”hŒThis parameter specifies whether each logical unit should be
reported as read only.  This will prevent host from modifying the
backing files.”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K^hj:  ubhÏ)”}”(hŒ§Note that if this flag for given logical unit is false but the
backing file could not be opened in read/write mode, the gadget
will fall back to read only mode anyway.”h]”hŒ§Note that if this flag for given logical unit is false but the
backing file could not be opened in read/write mode, the gadget
will fall back to read only mode anyway.”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kbhj:  ubhÏ)”}”(hŒrThe default value for non-CD-ROM logical units is false; for
logical units simulating CD-ROM it is forced to true.”h]”hŒrThe default value for non-CD-ROM logical units is false; for
logical units simulating CD-ROM it is forced to true.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kfhj:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hXç  nofua=b[,b...]

This parameter specifies whether FUA flag should be ignored in SCSI
Write10 and Write12 commands sent to given logical units.

MS Windows mounts removable storage in â€œRemoval optimised modeâ€ by
default.  All the writes to the media are synchronous, which is
achieved by setting the FUA (Force Unit Access) bit in SCSI
Write(10,12) commands.  This forces each write to wait until the
data has actually been written out and prevents I/O requests
aggregation in block layer dramatically decreasing performance.

Note that this may mean that if the device is powered from USB and
the user unplugs the device without unmounting it first (which at
least some Windows users do), the data may be lost.

The default value is false.
”h]”(hÏ)”}”(hŒnofua=b[,b...]”h]”hŒnofua=b[,b...]”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kihj|  ubhÏ)”}”(hŒ}This parameter specifies whether FUA flag should be ignored in SCSI
Write10 and Write12 commands sent to given logical units.”h]”hŒ}This parameter specifies whether FUA flag should be ignored in SCSI
Write10 and Write12 commands sent to given logical units.”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kkhj|  ubhÏ)”}”(hX€  MS Windows mounts removable storage in â€œRemoval optimised modeâ€ by
default.  All the writes to the media are synchronous, which is
achieved by setting the FUA (Force Unit Access) bit in SCSI
Write(10,12) commands.  This forces each write to wait until the
data has actually been written out and prevents I/O requests
aggregation in block layer dramatically decreasing performance.”h]”hX€  MS Windows mounts removable storage in â€œRemoval optimised modeâ€ by
default.  All the writes to the media are synchronous, which is
achieved by setting the FUA (Force Unit Access) bit in SCSI
Write(10,12) commands.  This forces each write to wait until the
data has actually been written out and prevents I/O requests
aggregation in block layer dramatically decreasing performance.”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Knhj|  ubhÏ)”}”(hŒ¸Note that this may mean that if the device is powered from USB and
the user unplugs the device without unmounting it first (which at
least some Windows users do), the data may be lost.”h]”hŒ¸Note that this may mean that if the device is powered from USB and
the user unplugs the device without unmounting it first (which at
least some Windows users do), the data may be lost.”…””}”(hjª  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kuhj|  ubhÏ)”}”(hŒThe default value is false.”h]”hŒThe default value is false.”…””}”(hj¸  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kyhj|  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hX  luns=N

This parameter specifies number of logical units the gadget will
have.  It is limited by FSG_MAX_LUNS (8) and higher value will be
capped.

If this parameter is provided, and the number of files specified
in â€œfileâ€ argument is greater then the value of â€œlunsâ€, all excess
files will be ignored.

If this parameter is not present, the number of logical units will
be deduced from the number of files specified in the â€œfileâ€
parameter.  If the file parameter is missing as well, one is
assumed.
”h]”(hÏ)”}”(hŒluns=N”h]”hŒluns=N”…””}”(hjÐ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K{hjÌ  ubhÏ)”}”(hŒŠThis parameter specifies number of logical units the gadget will
have.  It is limited by FSG_MAX_LUNS (8) and higher value will be
capped.”h]”hŒŠThis parameter specifies number of logical units the gadget will
have.  It is limited by FSG_MAX_LUNS (8) and higher value will be
capped.”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K}hjÌ  ubhÏ)”}”(hŒ¢If this parameter is provided, and the number of files specified
in â€œfileâ€ argument is greater then the value of â€œlunsâ€, all excess
files will be ignored.”h]”hŒ¢If this parameter is provided, and the number of files specified
in â€œfileâ€ argument is greater then the value of â€œlunsâ€, all excess
files will be ignored.”…””}”(hjì  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KhjÌ  ubhÏ)”}”(hŒÈIf this parameter is not present, the number of logical units will
be deduced from the number of files specified in the â€œfileâ€
parameter.  If the file parameter is missing as well, one is
assumed.”h]”hŒÈIf this parameter is not present, the number of logical units will
be deduced from the number of files specified in the â€œfileâ€
parameter.  If the file parameter is missing as well, one is
assumed.”…””}”(hjú  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K…hjÌ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubj?  )”}”(hŒ¥stall=b

Specifies whether the gadget is allowed to halt bulk endpoints.
The default is determined according to the type of USB device
controller, but usually true.
”h]”(hÏ)”}”(hŒstall=b”h]”hŒstall=b”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KŠhj  ubhÏ)”}”(hŒ›Specifies whether the gadget is allowed to halt bulk endpoints.
The default is determined according to the type of USB device
controller, but usually true.”h]”hŒ›Specifies whether the gadget is allowed to halt bulk endpoints.
The default is determined according to the type of USB device
controller, but usually true.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KŒhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj;  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1j9  hŸh¶h K&hj'  ubhÏ)”}”(hŒ±In addition to the above, the gadget also accepts the following
parameters defined by the composite framework (they are common to
all composite gadgets so just a quick listing):”h]”hŒ±In addition to the above, the gadget also accepts the following
parameters defined by the composite framework (they are common to
all composite gadgets so just a quick listing):”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Khj'  ubj:  )”}”(hhh]”(j?  )”}”(hŒ/idVendor      -- USB Vendor ID (16 bit integer)”h]”hÏ)”}”(hjO  h]”hŒ/idVendor      -- USB Vendor ID (16 bit integer)”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K”hjM  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubj?  )”}”(hŒ0idProduct     -- USB Product ID (16 bit integer)”h]”hÏ)”}”(hjf  h]”hŒ0idProduct     -- USB Product ID (16 bit integer)”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K•hjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubj?  )”}”(hŒ:bcdDevice     -- USB Device version (BCD) (16 bit integer)”h]”hÏ)”}”(hj}  h]”hŒ:bcdDevice     -- USB Device version (BCD) (16 bit integer)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K–hj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubj?  )”}”(hŒ1iManufacturer -- USB Manufacturer string (string)”h]”hÏ)”}”(hj”  h]”hŒ1iManufacturer -- USB Manufacturer string (string)”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K—hj’  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubj?  )”}”(hŒ,iProduct      -- USB Product string (string)”h]”hÏ)”}”(hj«  h]”hŒ,iProduct      -- USB Product string (string)”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K˜hj©  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubj?  )”}”(hŒ.iSerialNumber -- SerialNumber string (string)
”h]”hÏ)”}”(hŒ-iSerialNumber -- SerialNumber string (string)”h]”hŒ-iSerialNumber -- SerialNumber string (string)”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K™hjÀ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjJ  ubeh}”(h]”h ]”h"]”h$]”h&]”j:  j;  uh1j9  hŸh¶h K”hj'  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K#hj  hžhubeh}”(h]”Œmodule-parameters”ah ]”h"]”Œmodule parameters”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K!ubh¢)”}”(hhh]”(h§)”}”(hŒsysfs entries”h]”hŒsysfs entries”…””}”(hjï  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjì  hžhhŸh¶h KœubhÉ)”}”(hX  For each logical unit, the gadget creates a directory in the sysfs
hierarchy.  Inside of it the following three files are created:

- file

  When read it returns the path to the backing file for the given
  logical unit.  If there is no backing file (possible only if the
  logical unit is removable), the content is empty.

  When written into, it changes the backing file for given logical
  unit.  This change can be performed even if given logical unit is
  not specified as removable (but that may look strange to the
  host).  It may fail, however, if host disallowed medium removal
  with the Prevent-Allow Medium Removal SCSI command.

- ro

  Reflects the state of ro flag for the given logical unit.  It can
  be read any time, and written to when there is no backing file
  open for given logical unit.

- nofua

  Reflects the state of nofua flag for given logical unit.  It can
  be read and written.

- forced_eject

  When written into, it causes the backing file to be forcibly
  detached from the LUN, regardless of whether the host has allowed
  it.  The content doesn't matter, any non-zero number of bytes
  written will result in ejection.

  Can not be read.

Other then those, as usual, the values of module parameters can be
read from /sys/module/g_mass_storage/parameters/* files.
”h]”(hÏ)”}”(hŒ‚For each logical unit, the gadget creates a directory in the sysfs
hierarchy.  Inside of it the following three files are created:”h]”hŒ‚For each logical unit, the gadget creates a directory in the sysfs
hierarchy.  Inside of it the following three files are created:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kžhjý  ubj:  )”}”(hhh]”(j?  )”}”(hXî  file

When read it returns the path to the backing file for the given
logical unit.  If there is no backing file (possible only if the
logical unit is removable), the content is empty.

When written into, it changes the backing file for given logical
unit.  This change can be performed even if given logical unit is
not specified as removable (but that may look strange to the
host).  It may fail, however, if host disallowed medium removal
with the Prevent-Allow Medium Removal SCSI command.
”h]”(hÏ)”}”(hŒfile”h]”hŒfile”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K¡hj  ubhÏ)”}”(hŒ²When read it returns the path to the backing file for the given
logical unit.  If there is no backing file (possible only if the
logical unit is removable), the content is empty.”h]”hŒ²When read it returns the path to the backing file for the given
logical unit.  If there is no backing file (possible only if the
logical unit is removable), the content is empty.”…””}”(hj$  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K£hj  ubhÏ)”}”(hX3  When written into, it changes the backing file for given logical
unit.  This change can be performed even if given logical unit is
not specified as removable (but that may look strange to the
host).  It may fail, however, if host disallowed medium removal
with the Prevent-Allow Medium Removal SCSI command.”h]”hX3  When written into, it changes the backing file for given logical
unit.  This change can be performed even if given logical unit is
not specified as removable (but that may look strange to the
host).  It may fail, however, if host disallowed medium removal
with the Prevent-Allow Medium Removal SCSI command.”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K§hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj  ubj?  )”}”(hŒ¢ro

Reflects the state of ro flag for the given logical unit.  It can
be read any time, and written to when there is no backing file
open for given logical unit.
”h]”(hÏ)”}”(hŒro”h]”hŒro”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K­hjF  ubhÏ)”}”(hŒReflects the state of ro flag for the given logical unit.  It can
be read any time, and written to when there is no backing file
open for given logical unit.”h]”hŒReflects the state of ro flag for the given logical unit.  It can
be read any time, and written to when there is no backing file
open for given logical unit.”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K¯hjF  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj  ubj?  )”}”(hŒ]nofua

Reflects the state of nofua flag for given logical unit.  It can
be read and written.
”h]”(hÏ)”}”(hŒnofua”h]”hŒnofua”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K³hjl  ubhÏ)”}”(hŒUReflects the state of nofua flag for given logical unit.  It can
be read and written.”h]”hŒUReflects the state of nofua flag for given logical unit.  It can
be read and written.”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kµhjl  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj  ubj?  )”}”(hŒþforced_eject

When written into, it causes the backing file to be forcibly
detached from the LUN, regardless of whether the host has allowed
it.  The content doesn't matter, any non-zero number of bytes
written will result in ejection.

Can not be read.
”h]”(hÏ)”}”(hŒforced_eject”h]”hŒforced_eject”…””}”(hj–  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K¸hj’  ubhÏ)”}”(hŒÝWhen written into, it causes the backing file to be forcibly
detached from the LUN, regardless of whether the host has allowed
it.  The content doesn't matter, any non-zero number of bytes
written will result in ejection.”h]”hŒßWhen written into, it causes the backing file to be forcibly
detached from the LUN, regardless of whether the host has allowed
it.  The content doesnâ€™t matter, any non-zero number of bytes
written will result in ejection.”…””}”(hj¤  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kºhj’  ubhÏ)”}”(hŒCan not be read.”h]”hŒCan not be read.”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h K¿hj’  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j>  hj  ubeh}”(h]”h ]”h"]”h$]”h&]”j:  j;  uh1j9  hŸh¶h K¡hjý  ubhÏ)”}”(hŒ{Other then those, as usual, the values of module parameters can be
read from /sys/module/g_mass_storage/parameters/* files.”h]”hŒ{Other then those, as usual, the values of module parameters can be
read from /sys/module/g_mass_storage/parameters/* files.”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KÁhjý  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kžhjì  hžhubeh}”(h]”Œsysfs-entries”ah ]”h"]”Œsysfs entries”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kœubh¢)”}”(hhh]”(h§)”}”(hŒ)Other gadgets using mass storage function”h]”hŒ)Other gadgets using mass storage function”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjè  hžhhŸh¶h KÅubhÉ)”}”(hX‚  The Mass Storage Gadget uses the Mass Storage Function to handle
mass storage protocol.  As a composite function, MSF may be used by
other gadgets as well (eg. g_multi and acm_ms).

All of the information in previous sections are valid for other
gadgets using MSF, except that support for mass storage related
module parameters may be missing, or the parameters may have
a prefix.  To figure out whether any of this is true one needs to
consult the gadget's documentation or its source code.

For examples of how to include mass storage function in gadgets, one
may take a look at mass_storage.c, acm_ms.c and multi.c (sorted by
complexity).
”h]”(hÏ)”}”(hŒ´The Mass Storage Gadget uses the Mass Storage Function to handle
mass storage protocol.  As a composite function, MSF may be used by
other gadgets as well (eg. g_multi and acm_ms).”h]”hŒ´The Mass Storage Gadget uses the Mass Storage Function to handle
mass storage protocol.  As a composite function, MSF may be used by
other gadgets as well (eg. g_multi and acm_ms).”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KÇhjù  ubhÏ)”}”(hX5  All of the information in previous sections are valid for other
gadgets using MSF, except that support for mass storage related
module parameters may be missing, or the parameters may have
a prefix.  To figure out whether any of this is true one needs to
consult the gadget's documentation or its source code.”h]”hX7  All of the information in previous sections are valid for other
gadgets using MSF, except that support for mass storage related
module parameters may be missing, or the parameters may have
a prefix.  To figure out whether any of this is true one needs to
consult the gadgetâ€™s documentation or its source code.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KËhjù  ubhÏ)”}”(hŒ”For examples of how to include mass storage function in gadgets, one
may take a look at mass_storage.c, acm_ms.c and multi.c (sorted by
complexity).”h]”hŒ”For examples of how to include mass storage function in gadgets, one
may take a look at mass_storage.c, acm_ms.c and multi.c (sorted by
complexity).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KÑhjù  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KÇhjè  hžhubeh}”(h]”Œ)other-gadgets-using-mass-storage-function”ah ]”h"]”Œ)other gadgets using mass storage function”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÅubh¢)”}”(hhh]”(h§)”}”(hŒRelation to file storage gadget”h]”hŒRelation to file storage gadget”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj5  hžhhŸh¶h KÖubhÉ)”}”(hXå  The Mass Storage Function and thus the Mass Storage Gadget has been
based on the File Storage Gadget.  The difference between the two is
that MSG is a composite gadget (ie. uses the composite framework)
while file storage gadget was a traditional gadget.  From userspace
point of view this distinction does not really matter, but from
kernel hacker's point of view, this means that (i) MSG does not
duplicate code needed for handling basic USB protocol commands and
(ii) MSF can be used in any other composite gadget.

Because of that, File Storage Gadget has been removed in Linux 3.8.
All users need to transition to the Mass Storage Gadget.  The two
gadgets behave mostly the same from the outside except:

1. In FSG the â€œremovableâ€ and â€œcdromâ€ module parameters set the flag
   for all logical units whereas in MSG they accept a list of y/n
   values for each logical unit.  If one uses only a single logical
   unit this does not matter, but if there are more, the y/n value
   needs to be repeated for each logical unit.

2. FSG's â€œserialâ€, â€œvendorâ€, â€œproductâ€ and â€œreleaseâ€ module
   parameters are handled in MSG by the composite layer's parameters
   named respectively: â€œiSerialnumberâ€, â€œidVendorâ€, â€œidProductâ€ and
   â€œbcdDeviceâ€.

3. MSG does not support FSG's test mode, thus â€œtransportâ€,
   â€œprotocolâ€ and â€œbuflenâ€ FSG's module parameters are not
   supported.  MSG always uses SCSI protocol with bulk only
   transport mode and 16 KiB buffers.”h]”(hÏ)”}”(hX  The Mass Storage Function and thus the Mass Storage Gadget has been
based on the File Storage Gadget.  The difference between the two is
that MSG is a composite gadget (ie. uses the composite framework)
while file storage gadget was a traditional gadget.  From userspace
point of view this distinction does not really matter, but from
kernel hacker's point of view, this means that (i) MSG does not
duplicate code needed for handling basic USB protocol commands and
(ii) MSF can be used in any other composite gadget.”h]”hX  The Mass Storage Function and thus the Mass Storage Gadget has been
based on the File Storage Gadget.  The difference between the two is
that MSG is a composite gadget (ie. uses the composite framework)
while file storage gadget was a traditional gadget.  From userspace
point of view this distinction does not really matter, but from
kernel hackerâ€™s point of view, this means that (i) MSG does not
duplicate code needed for handling basic USB protocol commands and
(ii) MSF can be used in any other composite gadget.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KØhjF  ubhÏ)”}”(hŒ½Because of that, File Storage Gadget has been removed in Linux 3.8.
All users need to transition to the Mass Storage Gadget.  The two
gadgets behave mostly the same from the outside except:”h]”hŒ½Because of that, File Storage Gadget has been removed in Linux 3.8.
All users need to transition to the Mass Storage Gadget.  The two
gadgets behave mostly the same from the outside except:”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h KáhjF  ubhŒenumerated_list”“”)”}”(hhh]”(j?  )”}”(hX6  In FSG the â€œremovableâ€ and â€œcdromâ€ module parameters set the flag
for all logical units whereas in MSG they accept a list of y/n
values for each logical unit.  If one uses only a single logical
unit this does not matter, but if there are more, the y/n value
needs to be repeated for each logical unit.
”h]”hÏ)”}”(hX5  In FSG the â€œremovableâ€ and â€œcdromâ€ module parameters set the flag
for all logical units whereas in MSG they accept a list of y/n
values for each logical unit.  If one uses only a single logical
unit this does not matter, but if there are more, the y/n value
needs to be repeated for each logical unit.”h]”hX5  In FSG the â€œremovableâ€ and â€œcdromâ€ module parameters set the flag
for all logical units whereas in MSG they accept a list of y/n
values for each logical unit.  If one uses only a single logical
unit this does not matter, but if there are more, the y/n value
needs to be repeated for each logical unit.”…””}”(hjo  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kåhjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjh  ubj?  )”}”(hŒéFSG's â€œserialâ€, â€œvendorâ€, â€œproductâ€ and â€œreleaseâ€ module
parameters are handled in MSG by the composite layer's parameters
named respectively: â€œiSerialnumberâ€, â€œidVendorâ€, â€œidProductâ€ and
â€œbcdDeviceâ€.
”h]”hÏ)”}”(hŒèFSG's â€œserialâ€, â€œvendorâ€, â€œproductâ€ and â€œreleaseâ€ module
parameters are handled in MSG by the composite layer's parameters
named respectively: â€œiSerialnumberâ€, â€œidVendorâ€, â€œidProductâ€ and
â€œbcdDeviceâ€.”h]”hŒìFSGâ€™s â€œserialâ€, â€œvendorâ€, â€œproductâ€ and â€œreleaseâ€ module
parameters are handled in MSG by the composite layerâ€™s parameters
named respectively: â€œiSerialnumberâ€, â€œidVendorâ€, â€œidProductâ€ and
â€œbcdDeviceâ€.”…””}”(hj‡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Këhjƒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjh  ubj?  )”}”(hŒ×MSG does not support FSG's test mode, thus â€œtransportâ€,
â€œprotocolâ€ and â€œbuflenâ€ FSG's module parameters are not
supported.  MSG always uses SCSI protocol with bulk only
transport mode and 16 KiB buffers.”h]”hÏ)”}”(hŒ×MSG does not support FSG's test mode, thus â€œtransportâ€,
â€œprotocolâ€ and â€œbuflenâ€ FSG's module parameters are not
supported.  MSG always uses SCSI protocol with bulk only
transport mode and 16 KiB buffers.”h]”hŒÛMSG does not support FSGâ€™s test mode, thus â€œtransportâ€,
â€œprotocolâ€ and â€œbuflenâ€ FSGâ€™s module parameters are not
supported.  MSG always uses SCSI protocol with bulk only
transport mode and 16 KiB buffers.”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÎhŸh¶h Kðhj›  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j>  hjh  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1jf  hjF  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KØhj5  hžhubeh}”(h]”Œrelation-to-file-storage-gadget”ah ]”h"]”Œrelation to file storage gadget”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÖubeh}”(h]”Œmass-storage-gadget-msg”ah ]”h"]”Œmass storage gadget (msg)”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j÷  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jÑ  jÎ  j  j  jé  jæ  jå  jâ  j2  j/  jÉ  jÆ  uŒ	nametypes”}”(jÑ  ‰j  ‰jé  ‰jå  ‰j2  ‰jÉ  ‰uh}”(jÎ  h£j  h·jæ  j  jâ  jì  j/  jè  jÆ  j5  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.