commit | b405acc228612c00b8555400baa62017a65836e8 | [log] [tgz] |
---|---|---|
author | Hung-Te Lin <hungte@chromium.org> | Wed Apr 10 14:41:07 2024 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 11 01:20:11 2024 |
tree | c2e10d8f3824bbb002fdeb17c1733d33dab6c145 | |
parent | e613cb9962705a166e29a5c03c2a764c03398547 [diff] |
bmpblk: Explain how to find OS supported locales The bmpblk strings has more than the locales supported by ChromeOS, and the complete list can be found by running platform2/regions.py. BUG=None TEST=make # no error BRANCH=None Change-Id: Id059e862ea1e871186c0211da337b97e15148600 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/5443823 Tested-by: Hung-Te Lin <hungte@chromium.org> Commit-Queue: Yu-Ping Wu <yupingso@chromium.org> Reviewed-by: Yu-Ping Wu <yupingso@chromium.org> Auto-Submit: Hung-Te Lin <hungte@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.