On Thu, Dec 5, 2013 at 2:16 PM, Paul Menzel < paulepan...@users.sourceforge.net> wrote:
> Dear Aaron, > > > thanks a lot for your quick and interesting reply! > > > Am Mittwoch, den 04.12.2013, 17:49 -0600 schrieb Aaron Durbin: > > On Wed, Dec 4, 2013 at 4:25 PM, Paul Menzel wrote: > > > > developers at Google started upstreaming their patches for their new > > > devices. For example the boards Falco, Peppy, Pit and Slippy are now in > > > the coreboot repository. Big thanks for that. > > > > Slippy is a reference board that can't be bought. > > Peppy is the Acer C720 > > Falco is the HP Chromebook 14. > > > > Those 3 are all haswell. > > So what are Pit and Bolt? Can those be bought? > Pit is yet-to-be-released and uses the Samsung Exynos5420 octa-core (big.LITTLE) SoC. I should note that although coreboot works quite well on this platform, the product itself will ship with u-boot. > > If you have questions about anything in particular can provide more > > insight. > > I’d be very much interested in timing data and comparison to older > systems. > About 210ms for coreboot alone, another 330ms for the whole verified boot stuff (~540ms total). This is slightly misleading since there is a small binary blob (which is in the blobs repo) that is run before coreboot. We can only use a timer which is initialized in coreboot's bootblock on this SoC, so counting begins a few microseconds after coreboot begins. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
