-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
syslog/ramlog: remove magic flag #13686
base: master
Are you sure you want to change the base?
Conversation
[Experimental Bot, please feedback here] This PR appears to mostly meet the NuttX requirements, but is missing some information: What's good:
What needs improvement:
Recommendation: Before merging, expand on the Impact section, even if briefly, to confirm that the potential implications have been considered. Additionally, enhance the Testing section with specifics about the test environment and relevant log snippets. |
1. remove magic flag 2. move g_sysdev to bss 3. clear ramlog buffer only if in custom section Signed-off-by: chao an <[email protected]>
@anchao I think the magic flag is useful to search where the ramlog starts in the memory in case where someone is debug NuttX bringup and doesn't have serial console working. Maybe @patacongo can confirm the reason he included it. |
The flag was used to distinguish between a cold start and a reset. This was added by Xiaomi just a few months ago. See
|
@acassis @patacongo This PR will use the |
but the check doesn't work since g_sysdev is initialized to zero by boot every time. |
{ | ||
priv->rl_header = (FAR void *)g_sysbuffer; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's the benefit to change the static data initialization to the runtime initialization?
Summary
syslog/ramlog: remove magic flag
Signed-off-by: chao an [email protected]
Impact
N/A
Testing
ci-check