Google Git
Sign in
chromium / chromiumos / platform / bmpblk / refs/heads/stabilize-14588.123.B
commit31a5652b41878a805b35e7ded9734a20d3756743[log] [tgz]
authorReka Norman <[email protected]>Fri Jan 21 07:25:36 2022
committerCommit Bot <[email protected]>Wed Feb 02 21:34:04 2022
tree80c28bef3228391311f3d326dcf05ded796f5a10
parentd1682ce7627db22d6268360497c0573e6b561370 [diff]
bmpblk: Add board config for nissa

BUG=b:216016544
TEST=emerge-nissa chromeos-bmpblk
BRANCH=None

Change-Id: Ia5d3f65c4b0f3fcf34691a7d3e150a3a40a63943
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/3406492
Reviewed-by: Kangheui Won <[email protected]>
Reviewed-by: Tim Wawrzynczak <[email protected]>
Tested-by: Reka Norman <[email protected]>
Reviewed-by: Dossym Nurmukhanov <[email protected]>
Commit-Queue: Reka Norman <[email protected]>
1 file changed
tree: 80c28bef3228391311f3d326dcf05ded796f5a10
  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.