commit | 72b65a0e53acab8eb3d7fa3cb5deee8b5f723049 | [log] [tgz] |
---|---|---|
author | Shelley Chen <shchen@google.com> | Wed May 25 17:10:22 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 26 05:26:48 2022 |
tree | bcf83fdc7f8f68561cfcd7febe464f2f91df79a4 | |
parent | daf5d7a21d17594d789e2ec2786e66fd58fc7335 [diff] |
herobrine: Update herobrine_villager to villager BUG=b:216301615 BRANCH=None TEST=FW_NAME=villager emerge-herorine chromeos-bmpblk Cq-Depend: chrome-internal:4779535 Change-Id: Ie655481abd1778582a59a96c723f60587c85d372 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/3668329 Tested-by: Bob Moragues <moragues@chromium.org> Commit-Queue: Bob Moragues <moragues@chromium.org> Reviewed-by: Dossym Nurmukhanov <dossym@chromium.org> Reviewed-by: Bob Moragues <moragues@chromium.org> Tested-by: Shelley Chen <shchen@chromium.org>
Note: Because the bitmaps are stored in RO firmware, back-porting any new bitmaps to already shipped devices is not possible.
To build images for board $BOARD with default locales, do:
(chroot) cd ~/trunk/src/platform/bmpblk (chroot) BOARD="$BOARD" make
To override the locale list defined in boards.yaml
(for instance, to build with only English locale to speed up testing flow), pass LOCALES=<locale-list>
as an environment variable. For example,
(chroot) LOCALES="en ja es" BOARD="$BOARD" make
The default output folder is ./build/$BOARD
. To override output folder, specify OUTPUT=<path_to_output>
as an environment variable.
Add an entry for the new board in boards.yaml
. See the description at the top of boards.yaml
. For example, add the following for board link
:
link: screen: [1920, 1080] dpi: 112 # List of locales to include. locales: [en, es-419, pt-BR, fr, es, it, de, nl, da, 'no', sv, ko, he] # Right-to-left locales. rtl: [he]
Note: The locale no
will be interpreted as boolean False in YAML, so we need to quote it as 'no'
.
If your configuration is exactly the same as existing ones, add your new board into the existing entry. For example:
asurada,link: screen: [1920, 1080] dpi: 112 # DO NOT COPY-PASTE -- follow instructions at top of file.
After emerging chromeos-bmpblk
, bitmaps will be stored in the following files:
vbgfx.bin
: archive of generic (locale-independent) bitmapslocale_${LOCALE}.bin
: archive of bitmaps for locale ${LOCALE}
font.bin
: archive of glyph bitmapsThese archive files for Chromium OS firmware will be created using the archive
command from coreboot utils (src/third_party/coreboot/util/archive
). These files will end up being stored in the FMAP region COREBOOT in the image.
To show these files in an image $IMAGE, run:
cbfstool $IMAGE print -r COREBOOT
To extract an archive $NAME from an image as $FILE, run:
cbfstool $IMAGE extract -r COREBOOT -n $NAME -f $FILE
Also see the firmware UI troubleshooting doc for bitmap-related issues.