-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CFE_PSP_MemRangeSet() description error #38
Comments
Imported from trac issue 34. Created by abrown4 on 2015-08-11T17:49:27, last modified: 2019-04-02T14:49:34 |
Trac comment by sduran on 2015-08-17 15:32:54: These are the valid values for MemoryType: The last 2 are not valid for this function, so it does look like an incorrect comment.
|
Trac comment by abrown4 on 2015-08-17 15:51:39: commit: [changeset:1868407] Trac #38 Updated CFE_PSP_MemRangeSet() comments. |
Trac comment by jphickey on 2015-12-07 12:58:29: CCB Review: extracted from trac #14 branch and rebased to Commit [changeset:b3f19ff] contains the final fix, in branch |
Trac comment by jphickey on 2015-12-07 13:00:01: Review comments: This changes a comment so it has no impact on function, but it does not fix the obvious typo within the same line (CFE_PSP_MRM_EEPROM) |
Trac comment by sstrege on 2015-12-07 22:00:47: I'm OK with this change for the next release however, this points to a larger issue of having a PSP support memory ranges that are outside of RAM and EEPROM. |
Trac comment by jphickey on 2015-12-15 14:05:09: Commit [changeset:5f281c4] pushed with CCB updates from 2015-12-15 |
Trac comment by glimes on 2015-12-22 15:51:13: 2015-12-28 merged to development. |
Trac comment by glimes on 2016-01-11 10:42:10: Mark for PSP 1.3 per email from sstrege |
Trac comment by jhageman on 2019-04-02 14:49:34: Milestone renamed |
CFE_PSP_MemRangeSet() in cfe_psp_memrange.c has a comment error on the MemoryType argument that could be misleading.
CFE_PSP_MemRangeSet() validates against CFE_PSP_MEM_RAM and CFE_PSP_MEM_EEPROM types and errors out with any other type. (This is consistent with the CFE_PSP_MemValidateRange() implementation.) But the source file comments for CFE_PSP_MemRangeSet() have (cfe_psp_memrange.c, line 188):
{{{
<...snip...>
**
** Parameters:
** RangeNum -- A 32 bit integer ( starting with 0 ) specifying the MemoryTable entry.
** MemoryType -- The memory type to validate: CFE_PSP_MEM_RAM, CFE_PSP_MRM_EEPROM, or CFE_PSP_MEM_ANY
** Address -- A 32 bit starting address of the memory range
<...snip...>
}}}
That last "or CFE_PSP_MEM_ANY" is incorrect.
The text was updated successfully, but these errors were encountered: