| commit | b4830566336c67d45510f605c7538d178451fbbb | [log] [tgz] |
|---|---|---|
| author | Yu-Ping Wu <[email protected]> | Mon Aug 28 07:02:40 2023 |
| committer | Chromeos LUCI <[email protected]> | Tue Aug 29 09:00:05 2023 |
| tree | e48bb89ac8cb8ac059556baa403566c5619f29a8 | |
| parent | 5fffbdb3285f25f870befbf631ed1fe10951e1f8 [diff] |
bmpblk: Remove strings for phone recovery The USB AOA driver has been removed in CL:3718621. Therefore, remove the unused strings for phone recovery to save RO CBFS space. The following strings are removed: - btn_rec_by_phone - rec_invalid_desc - rec_phone_step1_desc0 - rec_phone_step1_desc1 - rec_phone_step2_desc - rec_phone_step2_title - rec_sel_desc1 - rec_sel_desc1_no_sd The following strings are renamed: - rec_invalid_disc_desc => rec_invalid_desc - rec_sel_desc1_no_phone => rec_sel_desc1 - rec_sel_desc1_no_phone_no_sd => rec_sel_desc1_no_sd BUG=b:297805271 TEST=make BOARD=geralt LOCALES="en bn" TEST=emerge-geralt chromeos-bmpblk BRANCH=none Cq-Depend: chromium:4816606 Change-Id: Iae97071ee505671a65eda6584ce11ac0c4471534 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/4816309 Reviewed-by: Julius Werner <[email protected]> Tested-by: Yu-Ping Wu <[email protected]> Commit-Queue: Yu-Ping Wu <[email protected]>
Note: Because the bitmaps are stored in RO firmware, back-porting any new bitmaps to already shipped devices is not possible.
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.
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.
After emerging chromeos-bmpblk, bitmaps will be stored in the following files:
vbgfx.bin: archive of generic (locale-independent) bitmapslocale_${LOCALE}.bin: archive of bitmaps for locale ${LOCALE}font.bin: archive of glyph bitmapsThese 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.