From: Pen-Yuan Hsing <penyuanhsing@gmail.com>
To: libreplanet-discuss@libreplanet.org
Subject: Does VIA's x86 CPUs have non-free "ME"s?
Date: Mon, 21 Aug 2017 16:30:44 +0100 [thread overview]
Message-ID: <a1d93a29-00f6-047f-60fb-389ecdc992a3@gmail.com> (raw)
Dear Libreplanet,
As we all know, a major problem with Intel (and AMD) x86 CPUs is that
they come with a proprietary "Management Engine (ME)" (or "Platform
Security Processor" for AMD) that is not only non-free but also with
demonstrated security holes.
I just recalled that VIA Technologies also have a line of x86 CPUs [1].
Do VIA CPUs also have the equivalent of the much-maligned ME? Or are VIA
CPUs more freedom-respecting? Would it help software freedom at all (or
not?) to use VIA CPUs instead? I'm curious!
[1]: https://en.wikipedia.org/wiki/VIA_Technologies#Processors
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next reply other threads:[~2017-08-21 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 15:30 Pen-Yuan Hsing [this message]
2017-08-21 18:53 ` Does VIA's x86 CPUs have non-free "ME"s? txt.file
2017-08-21 18:56 ` Pen-Yuan Hsing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1d93a29-00f6-047f-60fb-389ecdc992a3@gmail.com \
--to=penyuanhsing@gmail.com \
--cc=libreplanet-discuss@libreplanet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).