summaryrefslogtreecommitdiff
path: root/futility
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2014-11-15 03:02:29 +0000
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-11-15 05:59:54 +0000
commit79a9e0e63fd1001a3f9615f96c09acba5f20250d (patch)
treed3743c717ea7f193e4069d91a3a0f18c0426e4db /futility
parent5040a945dfd0dd305d3ca8e923b8bf0bd5c6528e (diff)
downloadvboot-79a9e0e63fd1001a3f9615f96c09acba5f20250d.tar.gz
Revert "vboot: Plumb the two disk sizes and 'gpt on device' param through"stabilize-6480.Bfactory-ryu-6486.Bfactory-ryu-6486.1.B
This reverts commit 5040a945dfd0dd305d3ca8e923b8bf0bd5c6528e. This patch breaks booting any image (both fixed and removable) on Veyron_Pinky (and presumably every other non-NAND board?). By the power vested in me through the office of ChromeOS tree sheriff (well, five hours early but whatever) it is hereby reverted! BUG=chromium:425677 BRANCH=none TEST=Can successfully boot on Veyron_Pinky again. Change-Id: I9323a3d5e34491337fc7eb09dd00d845ac42997d Reviewed-on: https://chromium-review.googlesource.com/229963 Reviewed-by: Julius Werner <jwerner@chromium.org> Commit-Queue: Julius Werner <jwerner@chromium.org> Tested-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'futility')
-rw-r--r--futility/cmd_verify_kernel.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/futility/cmd_verify_kernel.c b/futility/cmd_verify_kernel.c
index 0240ec33..f5ee2e00 100644
--- a/futility/cmd_verify_kernel.c
+++ b/futility/cmd_verify_kernel.c
@@ -96,8 +96,6 @@ static int do_verify_kernel(int argc, char *argv[])
params.disk_handle = (VbExDiskHandle_t)1;
params.bytes_per_lba = 512;
params.ending_lba = disk_bytes / 512 - 1;
- params.gpt_lba_count = params.ending_lba + 1;
- params.external_gpt = 0;
params.kernel_buffer_size = 16 * 1024 * 1024;
params.kernel_buffer = malloc(params.kernel_buffer_size);