[Replicant] [PATCH v2][ 05/11] freedom-privacy-security-issues: Add an example of where the hardware knowledge is
Paul Kocialkowski
contact at paulk.fr
Sun Jun 11 12:35:04 UTC 2017
Le lundi 28 mars 2016 à 20:50 +0200, Denis 'GNUtoo' Carikli a écrit :
> 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 at no-log.org>
> ---
> freedom-privacy-security-issues.php | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/freedom-privacy-security-issues.php b/freedom-privacy-security-
> issues.php
> index 775ed7f..2e4afe8 100644
> --- a/freedom-privacy-security-issues.php
> +++ b/freedom-privacy-security-issues.php
> @@ -32,6 +32,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 Linux kernel will
> then forward the communication between the hardware abstraction layer and the
> modem CPU.
Let's remove "Linux" because we're talking about kernels in general and "CPU"
after modem for consistency with what preceds.
Going with: " 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.
--
Paul Kocialkowski, developer of free digital technology and hardware support
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20170611/ba4eabd4/attachment.asc>
More information about the Replicant
mailing list