Flashmap: Difference between revisions
Jump to navigation
Jump to search
(Summary of ongoing work in the design and implementation of a unified representation for the layout of coreboot flash images) |
m (Clarify that this guide will be referencing the chromiumos master tree) |
||
| Line 2: | Line 2: | ||
=Toward a unified representation for the layout of coreboot flash images= | =Toward a unified representation for the layout of coreboot flash images= | ||
'''N.B.''' The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at [https://chromium.googlesource.com/chromiumos/third_party/coreboot/]. One of the | '''N.B.''' The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at [https://chromium.googlesource.com/chromiumos/third_party/coreboot/]. Unless otherwise noted, the paths and processes described throughout this page are as they exist(ed) in a checkout of the master branch of the Chromium OS sources as they appeared at the beginning of 2015. One of the guiding design principles is to keep the tools general enough that they will be helpful to others, and the resulting work will be upstreamed to the main repository once it has been regression-tested in the context of Chromium OS hardware. | ||
==How it's currently done (how the Chromium OS project presently constructs firmware images)== | ==How it's currently done (how the Chromium OS project presently constructs firmware images)== | ||
Revision as of 00:33, 11 February 2015
or...
Toward a unified representation for the layout of coreboot flash images
N.B. The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at [1]. Unless otherwise noted, the paths and processes described throughout this page are as they exist(ed) in a checkout of the master branch of the Chromium OS sources as they appeared at the beginning of 2015. One of the guiding design principles is to keep the tools general enough that they will be helpful to others, and the resulting work will be upstreamed to the main repository once it has been regression-tested in the context of Chromium OS hardware.