NXFFS is basically functional -- more testing needed

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3565 42af7a65-404d-4744-a932-0658087f49c3

1 files changed, 27 insertions, 1 deletions

diff --git a/nuttx/fs/nxffs/nxffs.h b/nuttx/fs/nxffs/nxffs.h
index 735e4fc0a..262c8577e 100644
--- a/nuttx/fs/nxffs/nxffs.h
+++ b/nuttx/fs/nxffs/nxffs.h
@@ -177,7 +177,6 @@
 
 #define NXFFS_MINDATA             16
 
-
 /* Internal definitions *****************************************************/
 /* If we encounter this number of erased bytes, we assume that all of the
  * flash beyond this point is erased.
@@ -641,6 +640,33 @@ extern int nxffs_findinode(FAR struct nxffs_volume_s *volume,
                            FAR struct nxffs_entry_s *entry);
 
 /****************************************************************************
+ * Name: nxffs_inodeend
+ *
+ * Description:
+ *   Return an *approximiate* FLASH offset to end of the inode data.  The
+ *   returned value is guaranteed to be be less then or equal to the offset
+ *   of the thing-of-interest in FLASH.  Parsing for interesting things
+ *   can begin at that point.
+ *
+ *   Assumption:  The inode header has been verified by the caller and is
+ *   known to contain valid data.
+ *
+ * Input Parameters:
+ *   volume - Describes the NXFFS volume
+ *   entry  - Describes the inode.
+ *
+ * Returned Value:
+ *   A FLASH offset to the (approximate) end of the inode data.  No errors
+ *   are detected.
+ *
+ * Defined in nxffs_inode.c
+ *
+ ****************************************************************************/
+
+extern off_t nxffs_inodeend(FAR struct nxffs_volume_s *volume,
+                            FAR struct nxffs_entry_s *entry);
+
+/****************************************************************************
  * Name: nxffs_verifyblock
  *
  * Description: