summaryrefslogtreecommitdiff
path: root/nuttx
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2015-04-12 09:21:31 -0600
committerGregory Nutt <gnutt@nuttx.org>2015-04-12 09:21:31 -0600
commit425e95e644a65139b5272bd787517df7fa87b4c9 (patch)
treee25b6cfc3230467b2902cb832a7925db8dae05f8 /nuttx
parentd3e8c4c6d6e125f0b6c18ea2a28f4e04b8713704 (diff)
downloadpx4-nuttx-425e95e644a65139b5272bd787517df7fa87b4c9.tar.gz
px4-nuttx-425e95e644a65139b5272bd787517df7fa87b4c9.tar.bz2
px4-nuttx-425e95e644a65139b5272bd787517df7fa87b4c9.zip
Update comments in a Kconfig file
Diffstat (limited to 'nuttx')
-rw-r--r--nuttx/libc/Kconfig13
1 files changed, 8 insertions, 5 deletions
diff --git a/nuttx/libc/Kconfig b/nuttx/libc/Kconfig
index 2ee379ecf..0a7a732ca 100644
--- a/nuttx/libc/Kconfig
+++ b/nuttx/libc/Kconfig
@@ -270,13 +270,16 @@ config LIBC_LOCALTIME
localtime API call support
Logic currently depends on file system support with, at a minimum, these
- files in the zoneinfo directory: GMT and posixrules.
+ files in the zoneinfo directory: GMT and posixrules. An additional
+ timezone file is required for any another time zone and the environment
+ variable TZ must be set to the name of that file.
- There is also an issue with mktime being called very early in
- initialization by the OS before there are any file systems available.
+ There is an issue with mktime being called very early in initialization
+ by the OS before there are any file systems available.
- And finally, the times presented by the NSH date command are wrong with
- this logic is enabled.
+ And finally, the times presented by the NSH date command are wrong when
+ this logic is enabled. I assume that this is due to some inconsistency
+ between the NuttX timing logic and the localtime timing logic.
if LIBC_LOCALTIME