summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@no-log.org>2016-03-28 20:50:25 +0200
committerPaul Kocialkowski <contact@paulk.fr>2017-06-11 15:34:47 +0300
commit5b373f465551fdd18f3fb17423c735879276b6b4 (patch)
treebcead85befb039a12be44f94743a4385bf7fd2a9
parent21cbcc637cca61f0243fe9d3b0e4cbdc53dabd9a (diff)
downloadreplicant_website-5b373f465551fdd18f3fb17423c735879276b6b4.zip
replicant_website-5b373f465551fdd18f3fb17423c735879276b6b4.tar.gz
replicant_website-5b373f465551fdd18f3fb17423c735879276b6b4.tar.bz2
freedom-privacy-security-issues: Add an example of where the hardware knowledge is
Many people do think that the hardware knowledge is only in the kernel. This is to prevent confusion. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
-rw-r--r--freedom-privacy-security-issues.php2
1 files changed, 2 insertions, 0 deletions
diff --git a/freedom-privacy-security-issues.php b/freedom-privacy-security-issues.php
index 05d9f20..32ec264 100644
--- a/freedom-privacy-security-issues.php
+++ b/freedom-privacy-security-issues.php
@@ -29,6 +29,8 @@
Hardware abstraction layers provide a generic interface for the framework to use.
The framework itself provides an interface for applications that is independent of the device and the hardware.
That way, applications can access hardware features through the generic framework interface, which will call the hardware abstraction layer libraries, ending up with the kernel communicating with the hardware.
+ For instance, when placing a call, the dialer application will communicate with the framework, which in turn will communicate with the hardware abstraction layer.
+ That hardware abstraction layer will implement the protocol to communicate with the modem. The kernel will then forward the communication between the hardware abstraction layer and the modem.
</p>
<p>
Many other components of a mobile device also run software in different forms.