Okay. :)
Well, I copied the file into the coreboot root and it built (the full path is not specified in menuconfig unlike me.bin and descriptor.bin, oddly), but I noticed when it does the cbfstool printout at the end that there's no me.bin this time, replaced by mrc.cache and mrc.bin. Should I be worried, and am I on a hiding to another brick in about an hour's time?
On 23/07/2013 22:47, ron minnich wrote:
scream and scream again ... ok I'll look. Just worked for parrot.
This whole experience is convincing me we've screwed up how we deploy chromebook coreboot to upstream ...
speaking for myself, nobody else, and not google :-)
ron
uh, yeah there needs to be an me.bin. mrc.bin is the code that runs on x86 to turn on memory.
mrc != me. mrc is memory reference code and me is management engine, and they are not interchangeable.
Gabe
On Tue, Jul 23, 2013 at 2:53 PM, John Lewis jlewis@johnlewis.ie wrote:
Okay. :)
Well, I copied the file into the coreboot root and it built (the full path is not specified in menuconfig unlike me.bin and descriptor.bin, oddly), but I noticed when it does the cbfstool printout at the end that there's no me.bin this time, replaced by mrc.cache and mrc.bin. Should I be worried, and am I on a hiding to another brick in about an hour's time?
On 23/07/2013 22:47, ron minnich wrote:
scream and scream again ... ok I'll look. Just worked for parrot.
This whole experience is convincing me we've screwed up how we deploy chromebook coreboot to upstream ...
speaking for myself, nobody else, and not google :-)
ron
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/**mailman/listinfo/coreboothttp://www.coreboot.org/mailman/listinfo/coreboot
-
Gabe Black -
John Lewis -
ron minnich