fatfs v0.14 October 14, 2019:

- Added support for 64-bit LBA and GUID partition table (FF_LBA64 = 1)
- Changed some API functions, f_mkfs() and f_fdisk().
- Fixed f_open() function cannot find the file with file name in length of FF_MAX_LFN characters.
- Fixed f_readdir() function cannot retrieve long file names in length of FF_MAX_LFN - 1 characters.
- Fixed f_readdir() function returns file names with wrong case conversion. (appeared at R0.12)
- Fixed f_mkfs() function can fail to create exFAT volume in the second partition. (appeared at R0.12)

documents/doc/mount.html

@@ -13,7 +13,7 @@
 
 <div class="para func">
 <h2>f_mount</h2>
-<p>The f_mount fucntion registers/unregisters filesystem object to the FatFs module.</p>
+<p>The f_mount fucntion gives work area to the FatFs module.</p>
 <pre>
 FRESULT f_mount (
   FATFS*       <span class="arg">fs</span>,    <span class="c">/* [IN] Filesystem object */</span>
@@ -50,7 +50,7 @@ FRESULT f_mount (
 
 <div class="para desc">
 <h4>Description</h4>
-<p>FatFs requires work area (<em>filesystem object</em>) for each logical drives (FAT volumes). Prior to perform file/directory operations, a filesystem object needs to be registered with <tt>f_mount</tt> function to the logical drive. The file/directory API functions get ready to work after this procedure. If there is any open object of file or directory on the logical drive, the object will be invalidated by this function.</p>
+<p>FatFs requires work area (<em>filesystem object</em>) for each logical drives (FAT volumes). Prior to perform any file/directory operations, a filesystem object needs to be registered with <tt>f_mount</tt> function for the logical drive. The file/directory API functions get ready to work after this procedure. Some volume management functions, <tt>f_mkfs</tt>, <tt>f_fdisk</tt> and <tt>f_setcp</tt>, do not want a filesystem object.</p>
 <p>The <tt>f_mount</tt> function registers/unregisters a filesystem object to the FatFs module as follows:</p>
 <ol>
 <li>Determines the logical drive which specified by <tt class="arg">path</tt>.</li>
@@ -58,6 +58,7 @@ FRESULT f_mount (
 <li>Clears and registers the new work area to the volume if <tt class="arg">fs</tt> is not NULL.</li>
 <li>Performs volume mount process to the volume if forced mounting is specified.</li>
 </ol>
+<p>If there is any open object of file or directory on the logical drive, the object will be invalidated by this function.<p>
 <p>If forced mounting is not specified (<tt>opt = 0</tt>), this function always succeeds regardless of the physical drive status. It only clears (de-initializes) the given work area and registers its address to the internal table and no activity of the physical drive in this function. The volume mount process will be attempted on subsequent file/directroy function if the filesystem object is not initialized. (delayed mounting) The volume mount processes, initialize the corresponding physical drive, find the FAT volume in it and then initialize the work area, is performed in the subsequent file/directory functions when either of following conditions is true.</p>
 <ul>
 <li>Filesystem object has not been initialized. It is de-initialized by <tt>f_mount</tt> function.</li>