In my opinion, the ME is indeed disabled because the entire ME
functionality is disabled, no ME processes are running, and the kernel
on its own is irrelevant, even if it keeps running.
However, I do not have anymore a strong counter opinion to your
statement that you don't consider the ME to be di
Hey Piotr,
I'm glad to read that somebody else is working on the Atoms as well.
I'm not sure about my ucode config. At the moment I'm using 5 include files:
M0130673322.h
M0130678806.h
M0130678817.h
M0130679901.h and
M0230672228.h
for a E3845 Family: 0x06 Model:0x37 Stepping: 0x09.
I copied the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you for the detailed response; I figured there had to be some
basic miscommunication somewhere. :-) So I assume we now agree that the
ME on Sylake + is not disabled, merely limited?
On 12/14/2017 01:20 AM, Youness Alaoui wrote:
> Hi,
>
> From
Hello Everyone,
As a result of incoming 4.7 release many boards are going to be
deprecated. We would like to support alix platforms which are based on
Geode LX and yet not EARLY_CBMEM_INIT enabled. We have all hardware at
hand and would gladly bring these platforms up to current standards.
We saw
> According to Positive Technologies, on Skylake and higher (like the
> Purism machines) the kernel loads the BUP, and the HAP bit only disables
> the normal userspace processes
This is very good observation. Let us look again into the unknown code,
compressed by Huffman (unknown tables):
[image:
Thanks for elaborating and shedding light on this for some of us
non-experts who are just lurking around.
On Thu, Dec 14, 2017 at 2:20 AM, Youness Alaoui <
kakar...@kakaroto.homelinux.net> wrote:
> Hi,
>
> From the PT article you linked to, after the stage 5 of BUP execution :
> "It is at this st
6 matches
Mail list logo
