Skip to contentSkip to conversation

vboot-utils: new package

PATCH Superseded Alex Suykov 2 participants 4 messages Dec 24, 2015 – Jan 2, 2016

v4 of 5 Superseded Latest is v5 →

lore
Share & tools
lore

Alex Suykov

author
#0 lore raw

PATCH v4 1/2 vboot-utils: new package

Chromium OS verified boot utilities.

Needed for signing kernel images and manipulating bootable partitions on media intended for Chromebooks.

Signed-off-by Alex Suykov <[email protected]>
---
 package/Config.in.host               |  1 +
 package/vboot-utils/Config.in.host   |  6 ++++++
 package/vboot-utils/vboot-utils.hash |  2 ++
 package/vboot-utils/vboot-utils.mk   | 39 ++++++++++++++++++++++++++++++++++++
 4 files changed, 48 insertions(+)
 create mode 100644 package/vboot-utils/Config.in.host
 create mode 100644 package/vboot-utils/vboot-utils.hash
 create mode 100644 package/vboot-utils/vboot-utils.mk
package/Config.in.host +1 -0
index d757316..8e6b870 100644
@@ -30,5 +30,6 @@ menu "Host utilities"
 	source "package/sunxi-tools/Config.in.host"
 	source "package/uboot-tools/Config.in.host"
 	source "package/util-linux/Config.in.host"
+	source "package/vboot-utils/Config.in.host"
 
 endmenu
package/vboot-utils/Config.in.host new file +6 -0
new file mode 100644
index 0000000..5cecef0
@@ -0,0 +1,6 @@
+config BR2_PACKAGE_HOST_VBOOT_UTILS
+	bool "host vboot utils"
+	help
+	  ChromiumOS verified boot utilities: futility and cgpt.
+
+	  https://www.chromium.org/chromium-os/chromiumos-design-docs/verified-boot
package/vboot-utils/vboot-utils.hash new file +2 -0
new file mode 100644
index 0000000..e161423
@@ -0,0 +1,2 @@
+# Git shapshot
+none	xxx	bbdd62f9b030db7ad8eef789aaf58a7ff9a25656.tar.gz
package/vboot-utils/vboot-utils.mk new file +39 -0
new file mode 100644
index 0000000..c595250
@@ -0,0 +1,39 @@
+################################################################################
+#
+# vboot-utils
+#
+################################################################################
+
+VBOOT_UTILS_VERSION = bbdd62f9b030db7ad8eef789aaf58a7ff9a25656
+VBOOT_UTILS_SOURCE = $(VBOOT_UTILS_VERSION).tar.gz
+VBOOT_UTILS_SITE = https://chromium.googlesource.com/chromiumos/platform/vboot_reference/+archive
+VBOOT_UTILS_STRIP_COMPONENTS = 0
+VBOOT_UTILS_LICENSE = BSD-3c
+VBOOT_UTILS_LICENSE_FILES = LICENSE
+
+HOST_VBOOT_UTILS_DEPENDENCIES = host-openssl host-pkgconf
+
+# vboot_reference contains code that goes into bootloaders,
+# utilities intended for the target system, and a bunch of scripts
+# for Chromium OS build system. Most of that does not make sense
+# in a buildroot host-package.
+#
+# We only need futility for signing images, the keys, and cgpt for boot
+# media partitioning.
+#
+# make target for futility is "futil".
+
+define HOST_VBOOT_UTILS_BUILD_CMDS
+	$(HOST_MAKE_ENV) $(MAKE) -C $(@D) \
+		CC="$(HOSTCC)" \
+		CFLAGS="$(HOST_CFLAGS) -D_LARGEFILE64_SOURCE -D_GNU_SOURCE" \
+		LDFLAGS="$(HOST_LDFLAGS)" \
+		futil cgpt
+endef
+
+define HOST_VBOOT_UTILS_INSTALL_CMDS
+	$(HOST_MAKE_ENV) $(MAKE) -C $(@D) DESTDIR=$(HOST_DIR)/usr \
+		futil_install cgpt_install devkeys_install
+endef
+
+$(eval $(host-generic-package))
Signature · 1 line
2.6.4
author
#2 lore raw

PATCH v4 1/2 vboot-utils: new package

Quoted 1 line · Mike Frysinger

this seems to have the same errors i pointed out in the ealier versions

(this message I think:
http://lists.busybox.net/pipermail/buildroot/2015-December/146493.html )

"ChromiumOS" instead of "Chromium OS" in Config.host.in, overlooked that. This is going into v5 patch then.

As for the tarball issue, I don't think there are any better options. It's either that, or a git checkout.
Do you mean it would be better to use git instead?

#3 lore raw

PATCH v4 1/2 vboot-utils: new package

Quoted 7 lines · Alex Suykov
Quoted 1 line · Mike Frysinger

this seems to have the same errors i pointed out in the ealier versions

(this message I think:
http://lists.busybox.net/pipermail/buildroot/2015-December/146493.html )

Quoted 6 lines

"ChromiumOS" instead of "Chromium OS" in Config.host.in, overlooked that. This is going into v5 patch then.

As for the tarball issue, I don't think there are any better options. It's either that, or a git checkout.
Do you mean it would be better to use git instead?

i mean git is the only option. any hash you commit will be invalid for any other user. unless you download that tarball and host it on your own site and list that as the source, but i think that's frowned upon.

run wget multiple times on the archive URI and you should get different results every time.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160102/5f7442eb/attachment.asc>