Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
RIOT
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cm-projects
RIOT
Commits
0b59372e
Commit
0b59372e
authored
8 years ago
by
Martine Lenders
Browse files
Options
Downloads
Patches
Plain Diff
at86rf2xx: document operation mode concerns for
parent
9b63d5c2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
drivers/at86rf2xx/include/at86rf2xx_internal.h
+9
-1
9 additions, 1 deletion
drivers/at86rf2xx/include/at86rf2xx_internal.h
with
9 additions
and
1 deletion
drivers/at86rf2xx/include/at86rf2xx_internal.h
+
9
−
1
View file @
0b59372e
...
@@ -163,10 +163,18 @@ void at86rf2xx_hardware_reset(at86rf2xx_t *dev);
...
@@ -163,10 +163,18 @@ void at86rf2xx_hardware_reset(at86rf2xx_t *dev);
*/
*/
void
at86rf2xx_configure_phy
(
at86rf2xx_t
*
dev
);
void
at86rf2xx_configure_phy
(
at86rf2xx_t
*
dev
);
#if defined
MODULE_AT86RF233 || defined
MODULE_AT86RF231
#if defined
(
MODULE_AT86RF233
)
|| defined
(
MODULE_AT86RF231
) || defined(DOXYGEN)
/**
/**
* @brief Read random data from the RNG
* @brief Read random data from the RNG
*
*
* @note According to the data sheet this function only works properly in
* Basic Operation Mode. However, sporadic testing has shown that even
* in Extended Operation Mode this returns random enough data to be
* used as a seed for @ref sys_random if no cryptographically secure
* randomness is required.
* Any further use-case needs to be evaluated, especially if
* crypto-relevant randomness is required.
*
* @param[in] dev device to configure
* @param[in] dev device to configure
* @param[out] data buffer to copy the random data to
* @param[out] data buffer to copy the random data to
* @param[in] len number of random bytes to store in data
* @param[in] len number of random bytes to store in data
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment