buildkernel icon indicating copy to clipboard operation
buildkernel copied to clipboard

Chromebook kernels and arm64 support

Open sarnold opened this issue 4 years ago • 1 comments

Hi again: This involves the chromebook signed FIT kernel images (and a few chromebook bootloader unknowns and possible tie-ins with dm-verity) as well as non-chromebook arm64 using UEFI blobs (as arm64 devices can have multiple bootloader options).

BUT, for now I'm mainly looking for an obvious way to short-circuit the luks/EFI settings/checks in buildkernel (which I couldn't really find). I did see the two DISABLE options but there isn't any explicit ARCH support yet. so I was wondering what you might suggest as an approach for now?

At this point I'd just like to test your kernel/initramfs approach as a signed FIT image on arm64 in a semi-automated fashion (note there are also plenty of x86_64 chromebooks this could work on, but I only have arm/arm64 chromebook hardware). I have a (forked) set of chromebook builder scripts but they're stand-alone and not distro-specific and have nothing to do with genkernel/anything, but at least in this context they can be used to make a bootable sdcard/usb-stick for starting the gnome install...

If i didn't mention it yet, the gnome install parts worked great on arm64 chromeobook, so the thinkpad now has a little brother named kevin ;)

sarnold avatar Nov 18 '19 18:11 sarnold