Google Git
Sign in
chromium/chromiumos/platform/bmpblk/refs/heads/main
commit
5d0085ce769330600e32615eb6144bc3c4f1d211
[log]
author
Tomasz Michalec <tmichalec@google.com>
Fri Apr 24 13:23:03 2026
committer
chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Apr 24 17:51:50 2026
tree
39eb0b70b7025367774fc834aa7d819aa01a7eb4
parent
fcebf153b28b9a03f83ad95ec91b889ea0b4f8ed [diff]
bmpblk: Remove unused strings and minor updates

Remove translations that are not longer used from xtb files. Apply minor
updates to hu, ro and tr languages, as it seems that latest change to
rec_disk_step2_desc0 triggered translation for some texts that were
translated before.

To collect comprehensive list of changed IDs following command from
strings/locale/README.md was run for all supported language codes.
python3 $CROS/src/platform/bmpblk/update_xtb.py diff <language_code>

All modified IDs where then merged using
python3 $CROS/src/platform/bmpblk/update_xtb.py merge <ID1> <ID2> ...

BUG=b:488289370
BRANCH=main
TEST=Build FW

Change-Id: Icba50ba8beaf934b2e1a940e99477b3a7fc439d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/7793188
Auto-Submit: Tomasz Michalec <tmichalec@google.com>
Reviewed-by: Konrad Adamczyk <konrada@google.com>
Reviewed-by: Subrata Banik <subratabanik@chromium.org>
Tested-by: Tomasz Michalec <tmichalec@google.com>
Commit-Queue: Subrata Banik <subratabanik@chromium.org>
80 files changed
tree: 39eb0b70b7025367774fc834aa7d819aa01a7eb4
  1. sprite/
  2. strings/
  3. .gitignore
  4. .pylintrc
  5. archive_images.py
  6. boards.yaml
  7. build.py
  8. DIR_METADATA
  9. format.yaml
  10. Makefile
  11. OWNERS
  12. PRESUBMIT.cfg
  13. pyproject.toml
  14. README.md
  15. unblocked_terms.txt
  16. update_xtb.py
README.md

bmpblk: Bitmap sources for firmware UI

Note: Because the bitmaps are stored in RO firmware, back-porting any new bitmaps to already shipped devices is not possible.

Building bitmaps

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.

Adding a new target board

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:
  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:
  dpi: 112  # DO NOT COPY-PASTE -- follow instructions at top of file.

Bitmaps in firmware image

After emerging chromeos-bmpblk, bitmaps will be stored in the following files:

  1. vbgfx.bin: archive of generic (locale-independent) bitmaps
  2. locale_${LOCALE}.bin: archive of bitmaps for locale ${LOCALE}
  3. font.bin: archive of glyph bitmaps

These 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.