Google Git
Sign in
chromium/chromiumos/platform/bmpblk/refs/heads/firmware-ec-R131-16063.2.B
commit
5982ae6275b6b9bdeb0cd5848745ab026f443ad6
[log]
author
Subrata Banik <[email protected]>
Wed Sep 04 14:49:26 2024
committer
Chromeos LUCI <[email protected]>
Thu Sep 05 03:39:49 2024
tree
ac54048daca9d2f8a8f360a985b3a943d9bd3378
parent
680af0e48813e73b7d1a4a6ab1b85dc4ab86fba2 [diff]
trulo: Keep locales in RO firmware

This change ensures that the read-only (RO) firmware only contains
locales, and that locales are not split across RO and read-write
(RW) firmware slots.

We're running low on RW firmware space, so we need to free up some
room in the RW slot. This change helps us to do that.

BUG=b:364574358
TEST=Can build and boot google/trulo.

Change-Id: I03e5885a561c1c1cfa89599ea3c1350f9d23ee4f
Signed-off-by: Subrata Banik <[email protected]>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/5837577
Auto-Submit: Subrata Banik <[email protected]>
Reviewed-by: Hsuan Ting Chen <[email protected]>
Commit-Queue: Subrata Banik <[email protected]>
Reviewed-by: Yu-Ping Wu <[email protected]>
Tested-by: Subrata Banik <[email protected]>
Reviewed-by: Dinesh Gehlot <[email protected]>
1 file changed
tree: ac54048daca9d2f8a8f360a985b3a943d9bd3378
  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:
  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.