blob: ff5feeac47a9de7b42f388c099f92730a4433b7a [file] [log] [blame]
# Copyright 2016 The Chromium OS Authors. All rights reserved.
# Distributed under the terms of the GNU General Public License v2
EAPI=4
CROS_WORKON_COMMIT="1a2b454f20e92792b9df2d31223ca16a6379557a"
CROS_WORKON_TREE="3484c26a2f8bb9f3d5d7c422c23df1eeae961723"
CROS_WORKON_PROJECT="chromiumos/third_party/kernel"
CROS_WORKON_LOCALNAME="kernel/v4.4"
CHROMEOS_KERNEL_CONFIG="${FILESDIR}/lakitu_kernel_config_4_4"
# This must be inherited *after* EGIT/CROS_WORKON variables defined
inherit cros-workon cros-kernel2 osreleased
STRIP_MASK+=" /usr/src/${P}/build/vmlinux"
DESCRIPTION="Chromium OS Linux Kernel 4.4"
HOMEPAGE="https://www.chromium.org/chromium-os/chromiumos-design-docs/chromium-os-kernel"
KEYWORDS="*"
src_install() {
cros-kernel2_src_install
# VCSID variable is unconditionally set by the cros-workon eclass, and
# is in the form of "<ebuild_revision>-<sha1>".
do_osrelease_field "KERNEL_COMMIT_ID" "${VCSID##*-}"
}
# Change the following (commented out) number to the next prime number
# when you change lakitu_kernel_config_4_4. This workaround will force the
# ChromeOS CQ to uprev sys-kernel/lakitu-kernel-4_4 ebuild and pick up the
# configuration changes. In absence of this workaround the config changes
# would not be picked up unless there was a code change in kernel source tree.
#
# NOTE: There's nothing magic keeping this number prime but you just need to
# make _any_ change to this file. ...so why not keep it prime?
#
# The coolest prime number is: 3