4 ms·
Doesn't the management engine exist as part of the BIOS on the same NAND? Couldn't Apple simply have Intel give them a custom BIOS that is signed?
by bogomipz 11y ago
Doesn't the management engine exist as part of the BIOS on the same NAND? Couldn't Apple simply have Intel give them a custom BIOS that is signed?
- pgeorgi 11y agoGroups more powerful than Apple tried to convince Intel to give them the opportunity to run only their own custom code on those Intel-signed areas of the processors they buy. What seems possible is running code on top of and in addition to the existing system, see CompuTrace. This isn't "simple" except perhaps for some US (and US only, by virtue of Intel being head-quartered there) agency with huge procurement budgets and persuasive legal instruments, and I'd expect push-back even then.
- ryao 11y agoWhy would they need to convince Intel when they could infiltrate them for what they want?
- pgeorgi 11y agoIf you infiltrate, with luck you get a half-assed data sheet. If you coerce them (with those persuasive legal instruments) you get minimum compliance to keep people out of jail. If you actually get some cooperation established, I'll guess that gives a much better support experience.
- ryao 11y agoIf you are willing to throw resources at deciphering things, infiltration could be all you need.
- ryao 11y agoI have been told by the CoreBoot developers that it has its own separate flash inside the chipset. There is definitely something loaded by the BIOS though.
- pgeorgi 11y agoME firmware is on the same SPI flash part as the host firmware[0] The BIOS doesn't need to load the ME firmware - that wouldn't be very useful since the ME is what gets the CPU out of reset these days. However, there are more binary components on a contemporary Intel device (listing the variants used with coreboot. other firmware may look slightly different, but the parts are pretty much the same internally): CPU microcode updates (useful because they can't manage to ship CPUs that work correctly on the first try); FSP (memory initialization code that's totally boring but guarded like a state secret); graphics initialization code (VGA BIOS or GOP driver. likewise boring-but-secret); sometimes some more hardware initialization, but we try to get most of that opened up (with varying success). And then there are some more signed binary components that aren't directly related to host firmware: TXT and SGX require intel-signed code, and - newest addition, I think - GPU firmware binaries. Because they were so well received with AMD and nVidia hardware. source: am a coreboot developer. [0] It's also a NOR part, not NAND, and it may be multiple SPI devices that the firmware hub exposes like a single one, but either detail is beyond nit-picking for the current discussion.
- ryao 11y agoI had talked to tpearson about the ME. He left me with the impression that there is flash memory inside the chipset that is separate from the BIOS chip. Maybe I had misunderstood as I can find no reference to substantiate that.