summaryrefslogtreecommitdiff
path: root/src/mainboard/google/smaug/chromeos.c
diff options
context:
space:
mode:
authorPatrick Georgi <pgeorgi@google.com>2019-05-08 18:40:00 +0200
committerPatrick Georgi <pgeorgi@google.com>2019-10-21 14:18:17 +0000
commit91841af6b25c77991fa461b8abbe4717f2de5d3c (patch)
tree96fa8e8123ced79b243436cc642106a716998bc0 /src/mainboard/google/smaug/chromeos.c
parent194422af82ad61bc2870e3db7d1a1e864e5b1ecd (diff)
Documentation: Add proposal for a comprehensive image assembly stage
I originally put up this document for discussion in 2015 (mailing list: https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/message/FXX4V2OSXAQC4B2VUENSFZEWRPPOVRH2/) (doc: https://docs.google.com/document/d/1o2bFl5HCHDFPccQsOwa-75A8TWojjFiGK3r0yeIc7Vo/edit) It may be time to revisit the way we define our image layouts now that there are new fmap schemes for new vboot uses. The approach outlined in this document may or may not be the right one, but it's something we have, so let's discuss. Compared to the doc, this will * be updated (things changed in the last 3.5 yearws) * integrate feedback to the doc and on the mailing list back then Change-Id: Ib40d286e2c9b817f55e58ecc5c9bc8b832ac5783 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/32687 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
Diffstat (limited to 'src/mainboard/google/smaug/chromeos.c')
0 files changed, 0 insertions, 0 deletions