netboot doesn't populate /proc/device-tree/firmware/chromeos/firmware-type |
||
Issue descriptionIn b/79891439 we found a difference in behavior between booting a kernel with netboot and booting it normally. The problem was tracked down to the fact that with netboot the file /proc/device-tree/firmware/chromeos/firmware-type isn't populated. crossystem uses this in the command 'crossystem mainfw_type' and the result of that command apparently changes certain Chrome behaviors. Is there a good reason why firmware-type isn't populated for netboot?
,
Jun 15 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/787d8f6df301f619a15a06583822a2169c6702c7 commit 787d8f6df301f619a15a06583822a2169c6702c7 Author: Julius Werner <jwerner@chromium.org> Date: Fri Jun 15 17:58:05 2018 netboot: Initialize crossystem data for Ctrl+N Some people complained about crossyste mainfw_type and other things not working during netboot. This patch should resolve that problem, although it's not 100% clean (the VbSharedData passed to crossystem will not have all values filled out the same way as a normal boot, since we didn't do the actual kernel selection part). BRANCH=None BUG= chromium:848410 TEST=Netbooted a Cheza, confirmed that 'crossystem mainfw_type' returns 'developer'. Change-Id: I1da99091bdf7931705d2748c9df6745053ccba34 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1094014 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> [modify] https://crrev.com/787d8f6df301f619a15a06583822a2169c6702c7/src/debug/dev.c
,
Jun 15 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by jwer...@chromium.org
, Jun 8 2018