Le lundi 28 mars 2016 à 20:50 +0200, Denis 'GNUtoo' Carikli a écrit : > Signed-off-by: Denis 'GNUtoo' Carikli <gnu...@no-log.org> > --- > freedom-privacy-security-issues.php | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/freedom-privacy-security-issues.php b/freedom-privacy-security- > issues.php > index 8fba5fb..775ed7f 100644 > --- a/freedom-privacy-security-issues.php > +++ b/freedom-privacy-security-issues.php > @@ -18,8 +18,11 @@ > Its firmware runs on a dedicated processor, > with dedicated memory and sometimes storage. > </p> > <p> > - Regarding the software side of things on > mobile devices, the main CPU (inside the SoC) starts by executing initial boot > code, often known as the bootrom. > - This code will look up various places such as > NAND, eMMC or MMC (sd/micro sd card) storage, depending on the hardware > configuration, to load a bootloader. > + Regarding the software side of things on > mobile devices, the main CPU (inside the SoC) starts by executing code burned > inside its silicon.
I'd like to keep "initial boot code" as it clearly shows what this code is supposed to do, instead of talking about "code" and later explaining what it does. Also, "burned inside its silicon" is fine but may not be the most evocative phrasing for the mass. How about: Regarding the software side of things on mobile devices, the main CPU (inside the SOC) starts by executing initial boot code, that is hard-wired inside the chip's silicon. > + That code cannot be changed without > fabricating a new chip. "fabricating" sound a bit too Frenchy IMO. How about "producing" instead? > + If this is an ARM CPU, that code will be ARM > instructions. I don't really see why we need this precision. At least, it should be made more generic, like: This code contains instructions in the CPU's instruction set and is directly executed by the main processor at reset. > + This code is known as the > bootrom. > + It will look up various places such as NAND, > eMMC or MMC (sd/micro sd card) storage, depending on the hardware > configuration, to load a bootloader. The rest looks good to me. > The bootloader, which is in fact often split > in different stages, is in charge of bringing up and configuring various > aspects of the hardware and eventually starting the operating system by > loading and running its kernel.<br /> > <a href="images/freedom-privacy-security- > issues/software.png" data-lightbox="overview" data-title="Software-side > overview"><img src="images/freedom-privacy-security-issues/software.png" > alt="Software-side overview" style="width: 250px; float: right;"/></a> > The kernel itself, among other things, deals > with the hardware directly and provides ways for other programs (running in > user-space) to access it.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Replicant mailing list Replicant@lists.osuosl.org http://lists.osuosl.org/mailman/listinfo/replicant
