aboutsummaryrefslogtreecommitdiff
path: root/docs/pages
diff options
context:
space:
mode:
authorDario Nieuwenhuis <[email protected]>2025-07-24 23:14:45 +0000
committerGitHub <[email protected]>2025-07-24 23:14:45 +0000
commit996974e313fa5ec2c7c2d9dd0998fab244c0a180 (patch)
treeffd6afabceaa1b4a9fc38500bdc0d537b30a8c8d /docs/pages
parent3842654b2237e31e46a9dd5a4465b3bf1540659b (diff)
parent035040e53cba24d7a15a055b605d50c568eb9e57 (diff)
Merge pull request #4259 from natevw/patch-1
Update layer_by_layer.adoc to clarify PAC limitations
Diffstat (limited to 'docs/pages')
-rw-r--r--docs/pages/layer_by_layer.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/pages/layer_by_layer.adoc b/docs/pages/layer_by_layer.adoc
index 7dba11b5e..0692ee4fa 100644
--- a/docs/pages/layer_by_layer.adoc
+++ b/docs/pages/layer_by_layer.adoc
@@ -8,7 +8,7 @@ The application we'll write is a simple 'push button, blink led' application, wh
8 8
9== PAC version 9== PAC version
10 10
11The PAC is the lowest API for accessing peripherals and registers, if you don't count reading/writing directly to memory addresses. It provides distinct types to make accessing peripheral registers easier, but it does not prevent you from writing unsafe code. 11The PAC is the lowest API for accessing peripherals and registers, if you don't count reading/writing directly to memory addresses. It provides distinct types to make accessing peripheral registers easier, but it does little to prevent you from configuring or coordinating those registers incorrectly.
12 12
13Writing an application using the PAC directly is therefore not recommended, but if the functionality you want to use is not exposed in the upper layers, that's what you need to use. 13Writing an application using the PAC directly is therefore not recommended, but if the functionality you want to use is not exposed in the upper layers, that's what you need to use.
14 14