Config layout change in bleeding coreboot

[wrobelda]

I am following your instructions, but do not see an option to strip the ME/TXE firmware. All I see is;

[*] Add Intel descriptor.bin file 

[*]   Add Intel ME/TXE firmware  

[*]     Stitch individual ME/CSE components             

[ ]   Allows HOST/CPU read access to ME region                                                                                                                                                                                                                         

[*] Add gigabit ethernet configuration

Any idea how to proceed here? As far as I understand, stripping ME/TXE is important? Meanwhile there's new Stitch individual ME/CSE components

[wrobelda]

I searched for the CONFIG_USE_ME_CLEANER symbol in the config and it indeed is supposed to be in Chipset section, except with following restriction:
Depends on: HAVE_INTEL_FIRMWARE [=y] && HAVE_ME_BIN [=n]

My understading is that HAVE_ME_BIN is true when the ME bin file exists, and it (amongst others) is generated by the ./compile.sh inside mainboard folders (m920q in my case). However I also assume that the ./build.sh chainloads ./compile.sh at buildtime. Therefore it seems there's some loop dependency here? I.e. ./compile.sh depends on toolchain that ./build.sh creates, but ./build.sh cannot be fully configured without running ./compile.sh first?

Or am I missing something here?

[wrobelda]

I added CONFIG_USE_ME_CLEANER by hand to .config, but it did not remove ME, according to intelmetool results.

[Thrilleratplay]

In the README of the M920q there is a note about the version of ME_Cleaner included with coreboot is not compatible with the M920q's version of ME and linked a version to manually use.

[wrobelda]

In the README of the M920q there is a note about the version of ME_Cleaner included with coreboot is not compatible with the M920q's version of ME and linked a version to manually use.

Well, that explains it, don't know how I missed it. Thanks!

BTW. Once I flashed coreboot with a programmer, do you know if I can I re-flash internally the rom with ME disabled?

EDIT: just flashed internally and looks like ME is disabled now.

[Thrilleratplay]

Assuming the IFD write flag is enabled and iomem=relaxed is added to the kernel parameter when booting Linux, you should be able to flash internally but I don't think I have done with with the m920q yet.