summaryrefslogtreecommitdiffstats
path: root/bsp-howto/getentropy.rst
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2018-04-26 09:05:20 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2018-04-27 12:49:57 +0200
commitcb0f55a4b829d9f2198b10c224a4ca626de7ded3 (patch)
treed413bafaadcfb8433da155798e1799fd2c1661f3 /bsp-howto/getentropy.rst
parent676d3d5d286a4e6bdcac6cdc840ac1a6e87ae24e (diff)
downloadrtems-docs-cb0f55a4b829d9f2198b10c224a4ca626de7ded3.tar.bz2
Update due to BSP source reorganization
This patch is a part of the BSP source reorganization. Close #3285.
Diffstat (limited to 'bsp-howto/getentropy.rst')
-rw-r--r--bsp-howto/getentropy.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/bsp-howto/getentropy.rst b/bsp-howto/getentropy.rst
index 10303a3..840ba1e 100644
--- a/bsp-howto/getentropy.rst
+++ b/bsp-howto/getentropy.rst
@@ -31,10 +31,10 @@ that can only be reached with some extra hardware support. Some microcontrollers
integrate a true random number generator or something similar for cryptographic
applications. That is the preferred source of entropy for most BSPs. For example
the
-`atsam BSP uses the TRNG for its entropy source <https://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/atsam/startup/getentropy-trng.c>`_.
+`atsam BSP uses the TRNG for its entropy source <https://git.rtems.org/rtems/tree/bsps/arm/atsam/start/getentropy-trng.c>`_.
There is also a quite limited
-`default implementation based on the CPU counter <https://git.rtems.org/rtems/tree/c/src/lib/libbsp/shared/getentropy-cpucounter.c>`_.
+`default implementation based on the CPU counter <https://git.rtems.org/rtems/tree/bsps/shared/dev/getentropy/getentropy-cpucounter.c>`_.
Due to the fact that it is a time based source, the values provided by
:c:func:`getentropy` are quite predictable. This implementation is not
appropriate for any cryptographic applications but it is good enough for some