Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / platform / bmpblk / 4c723ea3cadb8c2da1f81a5ec1593a48b3bf0151
commit4c723ea3cadb8c2da1f81a5ec1593a48b3bf0151[log] [tgz]
authorYu-Ping Wu <yupingso@chromium.org>Tue Apr 20 13:20:35 2021 +0800
committerCommit Bot <commit-bot@chromium.org>Fri Apr 30 16:51:45 2021 +0000
tree1cb51b9bd33299095eaf647da0bc7868d98f7726
parent14b01173873965e3c478c075dfc3ce09e0d648ad [diff]
bmpblk: Move glyph style constants to format.yaml

All the styles for generic strings, localized strings and sprites are
specified in format.yaml. Therefore, for consistency, move styles
constants for glyphs to format.yaml as well.

Also move SCALE_BASE back within the Converter class, which was moved
out of the class in CL:2649672 as an intermediate step towards
centralizing functions in the class.

BUG=b:178458718
TEST=make BOARD=asurada
BRANCH=none

Change-Id: I39cfea639fd3df93e6e164251f1969babaccbc43
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/2837201
Tested-by: Yu-Ping Wu <yupingso@chromium.org>
Reviewed-by: Joel Kitching <kitching@chromium.org>
Commit-Queue: Yu-Ping Wu <yupingso@chromium.org>
2 files changed
tree: 1cb51b9bd33299095eaf647da0bc7868d98f7726
  1. sprite/
  2. strings/
  3. .gitignore
  4. .pylintrc
  5. archive_images.py
  6. boards.yaml
  7. build.py
  8. format.yaml
  9. Makefile
  10. OWNERS
  11. PRESUBMIT.cfg
  12. README.md
  13. unblocked_terms.txt
  14. 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:
  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.

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.