Google Git
Sign in
chromium / chromiumos / platform / initramfs / 89b98139a1820ad198176fba92f39c4e6f5bc6e5
commit89b98139a1820ad198176fba92f39c4e6f5bc6e5[log] [tgz]
authorSean Paul <seanpaul@chromium.org>Mon Jun 01 16:17:01 2020
committerCommit Bot <commit-bot@chromium.org>Wed Jun 03 20:27:29 2020
treed82b307ca617db95671159525de973f93a1f38be
parente466a44057a74d9515858961e23490f3e2100a8f [diff]
Make backlight enable more robust

This patch makes the backlight enable more robust by doing the
following:

-Turn backlight hw on before updating the brightness
-Check the actual_brightness has been set to our desired level
-If brightness is not set, try up to 5 times with a 500ms sleep in between

BUG=chromium:1074427
TEST=Tested on eve, ensured backlight was set properly when booting recovery

Change-Id: I84bf7e05b79bab77d96788e7535eca665f6a3777
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2223818
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Commit-Queue: Sean Paul <seanpaul@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
1 file changed
tree: d82b307ca617db95671159525de973f93a1f38be
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. recovery/
  6. test/
  7. .gitignore
  8. LICENSE
  9. Makefile
  10. OWNERS
  11. README.md
README.md

Chromium OS initramfs

Build logic for creating standalone initramfs environments.

See the README files in the respective subdirs for more details.

To Use

Normally you wouldn't build in this directory directly. Instead, you would build the chromeos-initramfs package with the right USE flags. e.g.:

$ USE=recovery_ramfs emerge-$BOARD chromeos-initramfs

That will install the cpio initramfs files into the sysroot for you to build into a kernel directly. The various build scripts would then be used to make the right kernel/image using those (e.g. mod_image_for_recovery.sh).

To Make

You could build these by hand for quick testing. Inside the chroot:

$ make SYSROOT=/build/$BOARD BOARD=$BOARD <target>

That will create the cpio archives for you.

To Debug

It is possible to debug few of the initramfs targets in QEMU. Read test/README.md for more information.

Also, here is a shortcut for developing/debugging graphical bits in initramfs, without having to create a full image for every iteration.

After emerge-$BOARD, find your initramfs package from chroot /build/$BOARD/var/lib/initramfs and copy to a running DUT, for example /tmp/recovery_ramfs.cpio.xz, then do followings on DUT:

  1. mount -o remount,exec /mnt/stateful_partition
  2. mkdir /mnt/stateful_partition/test; cd /mnt/stateful_partition/test
  3. xzcat /tmp/XXXXXX_ramfs.cpio.xz | cpio -iv
  4. stop ui; kill $(pidof frecon)
  5. bind mount /dev, /proc, /sys and /tmp in /mnt/stateful_partition/test
  6. chroot /mnt/stateful_partition/test/init
  7. Iterate.