Le lundi 28 mars 2016 à 20:50 +0200, Denis 'GNUtoo' Carikli a écrit : > This is to explain why there is a differenciation between > firmwares loaded by the main CPU, and firmwares that aren't.
I think we should drop this altogether (even though I first introduced something like this). This brings a personal and subjective appreciation "we wouldn't be able to tell". I'd like to keep the document objective and avoid addressing readers directly. > Signed-off-by: Denis 'GNUtoo' Carikli <gnu...@no-log.org> > --- > freedom-privacy-security-issues.php | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/freedom-privacy-security-issues.php b/freedom-privacy-security- > issues.php > index 1e0f2c4..f9a2255 100644 > --- a/freedom-privacy-security-issues.php > +++ b/freedom-privacy-security-issues.php > @@ -55,6 +55,7 @@ > Firmwares running inside integrated circuits > are most of the time proprietary. > While free firmwares are hard to write, some > exist for very specific hardware (e.g. <a href="//www.arduino.cc/">Arduino</a> > ;, <a href="//dangerousprototypes.com/docs/Bus_Pirate">Bus Pirate</a>) and > sometimes, manufacturers can liberate firmwares running in their integrated > circuits (e.g. <a href="//github.com/qca/open-ath9k-htc- > firmware">ath9k_htc</a>). > However, it is not always possible to even > replace those firmwares: some are loaded to the integrated circuit by the main > CPU, but some others reside in separate storage from where they are loaded by > that integrated circuit. > + In that case, we wound't be able to tell the > difference with an integrated circuit lacking any storage. > With separate storage, it can be difficult > (to impossible) to update the firmware to a free replacement. > </p> > <p>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Replicant mailing list Replicant@lists.osuosl.org http://lists.osuosl.org/mailman/listinfo/replicant