tree 095f1628d3138766c5659f8d35dbfd723881b8a9
parent a3d70a3d2b5c052db039d097aaffa42008da24b5
author Shawn Nematbakhsh <shawnn@chromium.org> 1386974507 -0800
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1387326226 +0000

VbBootRecovery: Make second check for 'remove' devices if none found

There is some inherent latency between the time the USB root hub is
initialized and the time USB devices are detected. This can lead to a
situation where USB media is attached, yet not found when we do our
initial device poll. The device may be detected in subsequent polls, so
the media can be booted and no 'remove' screen will be displayed.

With this change, if no media to remove is initially found, a second
poll will be made after a 500ms delay. This will be enough time for USB
devices to be correctly detected in our test cases.

Also, it is necessary to change the unit test due to the fact that we
now call VbExDiskGetInfo twice before actually displaying any screen.

TEST=Manual on Monroe. Insert USB media and trigger recovery boot.
Verify 'remove' screen is seen, 'insert' screen is seen after removing
media, and system boots after re-inserting media. Also passes
vboot_reference unit tests.
BUG=chrome-os-partner:23840
BRANCH=Panther, Monroe

Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
Change-Id: Ia902c3a126588cd7ea618f2dbbca6b38d35d6ea0
Previous-Reviewed-on: https://chromium-review.googlesource.com/179757
(cherry picked from commit 04171532583052935121a3e33550cc39ef2625ec)
Reviewed-on: https://chromium-review.googlesource.com/180542
Commit-Queue: Mohammed Habibulla <moch@google.com>
Tested-by: Mohammed Habibulla <moch@google.com>