Google Git
Sign in
chromium / chromiumos / platform / bmpblk / refs/heads/stabilize-15888.B
commitac4f12254c7052854f6962dd4152345cdab89df9[log] [tgz]
authorDinesh Gehlot <digehlot@google.com>Thu Apr 04 04:52:14 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 15 07:40:05 2024
treebcfe27f76f715b3228e417af74c810bdfc82c0b5
parentb405acc228612c00b8555400baa62017a65836e8 [diff]
boards.yaml: Add trulo variant

TEST=emerge-trulo coreboot chromeos-bootimage

Change-Id: I72df36b7adcf564385a911252b111fe5bc144762
Signed-off-by: Dinesh Gehlot <digehlot@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/5420551
Reviewed-by: Shelley Chen <shchen@chromium.org>
Reviewed-by: Subrata Banik <subratabanik@chromium.org>
Tested-by: Subrata Banik <subratabanik@chromium.org>
Commit-Queue: Subrata Banik <subratabanik@chromium.org>
(cherry picked from commit 3521082f2bf19a1767f3dc31effbc975e2c46ee9)
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/5446831
Commit-Queue: Kapil Porwal <kapilporwal@chromium.org>
1 file changed
tree: bcfe27f76f715b3228e417af74c810bdfc82c0b5
  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.