On 13.06.2013 03:41, George Chriss wrote: > On Wed, Jun 12, 2013 at 7:16 PM, Vladimir 'φ-coder/phcoder' Serbinenko > <[email protected] <mailto:[email protected]>> wrote: >> >> Hello, all. In order to build X201 rom, you need management engine >> firmware. For chromebook the appropriate blobs are in 3rdparty repo, I >> suppose supplied by Intel. The only place where I could get ME firmware >> for X201 is by dumping chip with external programmer. It's probably not >> appropriate for coreboot to distribute those blobs (I'm unsure on their >> license) and given that it writes a log to its section which may contain >> private data, I don't want to distribute it either. Yet without this >> blob the build legitimately fails. Any suggestions on handling this? > > Are the coreboot dependencies function calls or something > hardware-specific? Coreboot send ME a message to tell it what to use for UMA. ACPI (at least CPU temperature) also goes through ME even if you read it from EC. > Is it possible to build a 'dummy' management engine > that still boots the X201, even with reduced functionality? It will reboot or hard lock after 30 minutes > (Is ME > binary code executed at any point using coreboot?) > No, it's executed on coprocessor, it's in the same flash but coreboot doesn't have to do anything to load it. > Sincerely, > George > > >
signature.asc
Description: OpenPGP digital signature
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
