From 5366852335044c1e68a5c32548d3051cc943552f Mon Sep 17 00:00:00 2001 From: Leo C Date: Tue, 19 Aug 2014 15:31:33 +0200 Subject: Import fatfs R0.10b FatFs Module Source Files R0.10b Author: (C)ChaN, 2014 (http://elm-chan.org) URL: http://elm-chan.org/fsw/ff/ff10b.zip --- fatfs/doc/en/dwrite.html | 76 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 fatfs/doc/en/dwrite.html (limited to 'fatfs/doc/en/dwrite.html') diff --git a/fatfs/doc/en/dwrite.html b/fatfs/doc/en/dwrite.html new file mode 100644 index 0000000..67e3310 --- /dev/null +++ b/fatfs/doc/en/dwrite.html @@ -0,0 +1,76 @@ + + +
+ + + + + +The disk_write writes sector(s) to the storage device.
++DRESULT disk_write ( + BYTE drv, /* [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 */ +); ++
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 feature of the disk functions. The write operation to the media need not to be completed due to write operation is in progress or only stored it into the cache buffer when return from this function. But 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 delayed write feature is implemented, the write throughput may be improved.
+Application program MUST NOT call this function, or FAT structure on the volume can be collapsed.
+This function is not needed when _FS_READONLY == 1.
+