-
Notifications
You must be signed in to change notification settings - Fork 33
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
Improve documentation #697
Conversation
This last commit fixes a issue when setting the time. This was working:
But not this:
Because the arguments were printed one after the other so the RTC device would not get a buffer containing the whole date and time, instead it would get the date first, then the time, which it couldn't parse to set the date and time. This is an implementation issue and not expected from the user perspective. The solution was to join all the arguments (with a space) before printing them. We couldn't do this in the past because we couldn't allocate memory from userspace but now we can. |
The following command can be used to compare the doc and the high level wrapper of the syscalls:
It's not clear yet how to document both the raw syscalls and their high level wrappers used in the userspace Rust API. |
We can now run the following command to make sure that the syscalls doc is up to date:
|
This commit clarify the code of It also simplify its return type and fix an issue where the return code passed by the child on Here we can see |
No description provided.