-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add bcm2711-kernel-bis-bin-4.19.97.20200204.ebuild
- Loading branch information
Showing
2 changed files
with
109 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
108 changes: 108 additions & 0 deletions
108
sys-kernel/bcm2711-kernel-bis-bin/bcm2711-kernel-bis-bin-4.19.97.20200204.ebuild
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,108 @@ | ||
| # Copyright (c) 2019 sakaki <[email protected]> | ||
| # Distributed under the terms of the GNU General Public License v2 | ||
|
|
||
| EAPI="6" | ||
|
|
||
| inherit eutils autotools | ||
|
|
||
| DESCRIPTION="Binary RPi4 64-bit kernel package (bcm2711_defconfig + tweaks)" | ||
| HOMEPAGE="https://github.com/sakaki-/bcm2711-kernel-bis" | ||
|
|
||
| SRC_URI="${HOMEPAGE}/releases/download/${PV}/bcm2711-kernel-bis-${PV}.tar.xz -> ${P}.tar.xz" | ||
|
|
||
| LICENSE="GPL-2 freedist" | ||
| SLOT="0" | ||
| KEYWORDS="~arm64" | ||
| IUSE="+checkboot +with-matching-boot-fw pitop +pi3multiboot" | ||
|
|
||
| RESTRICT="mirror" | ||
|
|
||
| DEPEND=" | ||
| !sys-kernel/bcm2711-kernel-bin" | ||
| # if pi3multiboot is specified, depend upon corresponding-date rpi3-specific | ||
| # kernel package too | ||
| RDEPEND=" | ||
| with-matching-boot-fw? ( ~sys-boot/rpi3-64bit-firmware-1.20200114[pitop(-)?,-dtbo(+)] ) | ||
| pi3multiboot? ( ~sys-kernel/bcmrpi3-kernel-bis-bin-${PV}[checkboot=,with-matching-boot-fw=,pitop=] ) | ||
| !pi3multiboot? ( | ||
| !sys-kernel/bcmrpi3-kernel-bin | ||
| !sys-kernel/bcmrpi3-kernel-bis-bin | ||
| ) | ||
| ${DEPEND}" | ||
|
|
||
| QA_PREBUILT="*" | ||
|
|
||
| S="${WORKDIR}" | ||
|
|
||
| # ebuild function overrides | ||
|
|
||
| pkg_pretend() { | ||
| # check /boot directory is mounted, provided $ROOT is / | ||
| if use checkboot && [[ "${ROOT%/}" == "" ]]; then | ||
| if ! grep -q "^/boot$" <(cut -d " " -f 2 "/proc/mounts") &>/dev/null; then | ||
| die "Your /boot directory does not appear to be mounted" | ||
| fi | ||
| else | ||
| ewarn 'Installing into non-default $ROOT' | ||
| ewarn "Not checking whether /boot is mounted" | ||
| fi | ||
| } | ||
|
|
||
| src_install() { | ||
| local RELEASE_NAME | ||
|
|
||
| # just copy tarball contents into temporary install root | ||
| insinto /boot | ||
| doins -r "${S%/}/boot"/* | ||
| # only copy overlays/ directory if not multibooting with a pi3 kernel | ||
| # (it owns them if this flag is set) | ||
| # also, don't duplicate COPYING.linux in this case | ||
| if use pi3multiboot; then | ||
| rm -rf "${D%/}/boot/overlays" | ||
| rm -f "${D%/}/boot/COPYING.linux" | ||
| fi | ||
| insinto /lib/modules | ||
| doins -r "${S%/}/lib/modules"/* | ||
| # note that we installed the libraries, for future cleanup | ||
| RELEASE_NAME=$(head -n1 <(ls -t1d "${S}/lib/modules"/*)) | ||
| RELEASE_NAME="${RELEASE_NAME##*/}" | ||
| echo "${PF}" > "${D%/}/lib/modules/${RELEASE_NAME}/owning_binpkg" | ||
| } | ||
|
|
||
| pkg_postinst() { | ||
| elog "Your new kernel has been installed." | ||
| elog "Reboot your system to start using it." | ||
| } | ||
|
|
||
| pkg_postrm() { | ||
| # it is possible that if the kernel originally installed by this ebuild | ||
| # is currently running, then its /lib/modules/<release_name> directory | ||
| # will still be present, due to some of the module files therein having | ||
| # been marked as "in use", leading Portage deline to delete them during | ||
| # the default uninstall phase | ||
| # detect if this has happened and, if so, forcibly (and recursively) | ||
| # delete /lib/modules/<release_name>, and print a warning | ||
| local MDIR OWNING_BINPKG | ||
|
|
||
| shopt -s nullglob | ||
| for MDIR in "${ROOT%/}/lib/modules"/*; do | ||
| # was this kernel installed by a binary package? | ||
| if [[ -s "${MDIR}/owning_binpkg" ]]; then | ||
| OWNING_BINPKG="$(<"${MDIR}/owning_binpkg")" | ||
| # was it us? (also check this is not a pure re-install) | ||
| if [[ "${PF}" == "${OWNING_BINPKG}" && "${PVR}" != "${REPLACED_BY_VERSION}" ]]; then | ||
| # yes, we installed it, we need to remove it | ||
| ewarn "Forcibly deleting kernel module directory ${MDIR}" | ||
| rm -rf "${MDIR}" | ||
| # warn user if this is a 'pure' uninstall, | ||
| # rather than an upgrade | ||
| if [[ -z "${REPLACED_BY_VERSION}" ]]; then | ||
| ewarn "Please ensure you have a valid kernel and module set" | ||
| ewarn "in place, before rebooting." | ||
| fi | ||
| fi | ||
| fi | ||
| done | ||
| shopt -u nullglob | ||
| } | ||
|
|