commit | 8067d11403aa8205b9fd250f1dfb785ec1b490ae | [log] [tgz] |
---|---|---|
author | Yu-Ping Wu <[email protected]> | Mon Jun 02 06:35:37 2025 |
committer | Chromeos LUCI <[email protected]> | Mon Jun 02 09:25:08 2025 |
tree | 2887f03b9a36e42dff934fb6aebc34c9402e11c4 | |
parent | 05ff4e2d90fd118c5aed7a25eaf1bc791dd7aa30 [diff] |
skywalker: Reduce dpi from 112 to 96 The RO CBFS space is insufficient for obiwan (skywalker), so reduce the usage of bitmaps. FIXED=b:421801808 TEST=emerge-skywalker chromeos-bmpblk chromeos-bootimage BRANCH=none Change-Id: I939e428e8809a743d5e2ef2f82ed4f1f80dceca6 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/bmpblk/+/6607044 Commit-Queue: Yu-Ping Wu <[email protected]> Commit-Queue: Yidi Lin <[email protected]> Reviewed-by: Yidi Lin <[email protected]> Auto-Submit: Yu-Ping Wu <[email protected]> Tested-by: 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: 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: 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.