[
https://issues.apache.org/jira/browse/MYNEWT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472534#comment-15472534
]
ASF subversion and git services commented on MYNEWT-368:
--------------------------------------------------------
Commit 2d7ed71e48fdbc65034e514238455cd7893de9cb in incubator-mynewt-core's
branch refs/heads/develop from [~peterfs]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=2d7ed71
]
Change logging format to use 16-bit log index.
Change log struct (log_entry_hdr) from using an 8-bit to 16-bit index
(ue_index) and reducing the log module number (ue_module) from 16-bit to 8-bit
preserving the size of the structure. Also removed code which reset the index
every 1ms.
Added a version id in the global log_info structure so the log record format
can be differentiated OTW or from non-volatile storage.
Partial checkin for MYNEWT-368 - remaining work to store record format in FCB.
> Change logging format
> ---------------------
>
> Key: MYNEWT-368
> URL: https://issues.apache.org/jira/browse/MYNEWT-368
> Project: Mynewt
> Issue Type: Bug
> Components: Newtmgr
> Reporter: Sterling Hughes
> Assignee: Peter Snyder
> Fix For: v1_0_0_beta1
>
>
> Right now newtmgr has an 8-bit index which goes along with a 64-bit
> timestamp. We are having trouble querying logs when time moves forward,
> because of the misordering of log entries.
> We should change this such that we have a 16-bit log index, which can be used
> to query logs remotely. A result of this will be to make the module an 8-bit
> value, which it is already assumed to be.
> While doing this change, on the FCB implementation, we should also add a
> short log entry header (4-bytes), that at least contains the version of the
> log format that we are writing, that way when we make changes in the future
> to the log format, the code can automatically wipe this sector and reformat
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
