veyepar: Open Source Firmware

Author(s):	Duncan Laurie
Location	MCC2
Date	jan Thu 31	Days Raw Files
Start	13:20	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	14:05	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30310/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Open_Source_Firmware.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Chrome OS is a Linux-based operating system developed by Google that aims to provide a fast, simple, and secure environment for the web.

One of the main goals of the project is security, and in order to provide a secure environment we developed a firmware and kernel solution called Verified Boot that strives to ensure all executed code is known to be safe from the moment the system is powered on.

Another goal of ours is pushing open source wherever possible.  So for our second generation of Chrome OS devices we created a firmware stack based on the open source projects Coreboot and U-boot, paired with our own Verified Boot.

This presentation will discuss our new firmware stack and the reasons behind it, provide detail on what effort was required to support Intel's Sandybridge/Ivybridge architecture in Coreboot, and discuss what portions of the firmware are not yet open and why.

It will also provide detail on our open source Embedded Controller firmware and why that is another important piece of our approach to security and our commitment to open source.

Comment:

production notes