summaryrefslogtreecommitdiff
path: root/nuttx/TODO
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2015-03-16 08:49:39 -0600
committerGregory Nutt <gnutt@nuttx.org>2015-03-16 08:49:39 -0600
commitb1d9ef2c195da84f4203fb9d65fb75d70a857a40 (patch)
tree77b6268517956b6c04eb7fa3872fd319df3a6b89 /nuttx/TODO
parent57d2515d4f8237f643ac1ea34c9416fa47b702df (diff)
downloadpx4-nuttx-b1d9ef2c195da84f4203fb9d65fb75d70a857a40.tar.gz
px4-nuttx-b1d9ef2c195da84f4203fb9d65fb75d70a857a40.tar.bz2
px4-nuttx-b1d9ef2c195da84f4203fb9d65fb75d70a857a40.zip
Update TODO list and some comments
Diffstat (limited to 'nuttx/TODO')
-rw-r--r--nuttx/TODO30
1 files changed, 29 insertions, 1 deletions
diff --git a/nuttx/TODO b/nuttx/TODO
index 5ec04619a..d0d4027f3 100644
--- a/nuttx/TODO
+++ b/nuttx/TODO
@@ -1330,7 +1330,35 @@ o File system / Generic drivers (fs/, drivers/)
not understand the pattern. But I have not had the opportunity
to dig into this deeply.
Status: Open
- Priority: Medium-High
+ Priority: Perhaps not a problem??? I have analyzed this problem and
+ I am not sure what to do about it. I am suspected that a
+ fat filesystem was used with a version of NuttX that does
+ not support long file name entries. Here is the failure
+ scenario:
+
+ 1) A file with a long file name is created under Windows.
+ 2) Then the file is deleted. I am not sure if Windows or
+ NuttX deleted the file, but the resulting directory
+ content is not compatible with NuttX with long file
+ name support.
+
+ The file deletion left the full sequence of long
+ file name entries intact but apparently delete only
+ the following short file name entry. I am thinking
+ that this might have happened because a version of NuttX
+ with only short file name support was used to delete
+ the file.
+
+ 3) When a new file with a short file name was created, it
+ re-used the short file name entry that was previously
+ deleted. This makes the new short file name entry
+ look like a part of the long file name.
+
+ 4) When comparing the checksum in the long file name
+ entry with the checksum of the short file name, the
+ checksum fails and the entire directlry sequence is
+ ignored by readder() logic. This the file does not
+ appear in the 'ls'.
o Graphics subsystem (graphics/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^