X-Git-Url: http://cloudbase.mooo.com/gitweb/z180-stamp.git/blobdiff_plain/b4e3fab85fcd9f5b1502ec991c81302b910492d3:/fatfs/doc/en/dwrite.html..0f3b947bda5f34662a611272b9f12199e0da9aca:/fatfs/documents/doc/dwrite.html diff --git a/fatfs/doc/en/dwrite.html b/fatfs/documents/doc/dwrite.html similarity index 61% rename from fatfs/doc/en/dwrite.html rename to fatfs/documents/doc/dwrite.html index b97f177..51174f9 100644 --- a/fatfs/doc/en/dwrite.html +++ b/fatfs/documents/doc/dwrite.html @@ -1,7 +1,7 @@ - + @@ -13,10 +13,10 @@

disk_write

-

The disk_write writes sector(s) to the storage device.

+

The disk_write function is called to write data to the sector(s) of storage device.

 DRESULT disk_write (
-  BYTE drv,         /* [IN] Physical drive number */
+  BYTE pdrv,        /* [IN] Physical drive number */
   const BYTE* buff, /* [IN] Pointer to the data to be written */
   DWORD sector,     /* [IN] Sector number to write from */
   UINT count        /* [IN] Number of sectors to write */
@@ -45,7 +45,7 @@ DRESULT disk_write (
 
RES_OK (0)

 
The function succeeded.

 
RES_ERROR

-
Any hard error occured during the write operation and could not recover it.

+
An unrecoverable hard error occured during the write operation.

 
RES_WRPRT

 
The medium is write protected.

 
RES_PARERR

@@ -58,16 +58,16 @@ DRESULT disk_write (
 
 

 
Description

-
The specified memory address is not that always aligned to word boundary because the type of pointer is defined as BYTE*. For more information, refer to the description of disk_read function.

-
Generally, a multiple sector transfer request must not be split into single sector transactions to the storage device, or you will never get good write throughput.

-
FatFs expects delayed write function of the disk control layer. The write operation to the media does not need to be completed when return from this function by what write operation is in progress or data is only stored into the write-back cache. But write data on the buff is invalid after return from this function. The write completion request is done by CTRL_SYNC command of disk_ioctl function. Therefore, if a delayed write function is implemented, the write throughput will be improved.

+
The specified memory address is not that always aligned to word boundary because the argument is defined as BYTE*. For more information, refer to the description of disk_read function.

+
Generally, a multiple sector write request (count > 1) must not be split into single sector transactions to the storage device, or the file write throughput will be drastically decreased.

+
FatFs expects delayed write function of the disk control layer. The write operation to the media does not need to be completed at return from this function by what write operation is in progress or data is only stored into the write-back cache. But write data on the buff is invalid after return from this function. The write completion request is done by CTRL_SYNC command of disk_ioctl function. Therefore, if a delayed write function is implemented, the write throughput of the filesystem will be improved.

 
Remarks: Application program MUST NOT call this function, or FAT structure on the volume can be collapsed.

 

 
 
 

 
QuickInfo

-
This function is not needed when _FS_READONLY == 1.

+
This function is not needed when FF_FS_READONLY == 1.