Commit graph

7 commits

Author SHA1 Message Date
Clayton Craft
94de94e598
device-generic-x86_64: install all linux-firmware by default (MR 4794)
This installs all linux-firmware by default (using pmb_recommends) in a
way that allows for users to remove extraneous fw if they want.

The old `nonfree-firmware` packages have been dropped since pmbootstrap
no longer conditionally installs these.
[ci:skip-build]: already built successfully in CI
2024-02-21 22:54:41 -08:00
Clayton Craft
5ef542d70e
device-generic-x86_64: initfs: fix FDE w/ usb keyboard (MR 4829)
- Fixes FDE unlocking on devices with usb keyboards

- Also drops the i915 module from the initfs, this is specified by the
  oem-intel package now

[ci:skip-build] already built successfully in CI
2024-02-16 10:05:29 -08:00
Clayton Craft
c6b6bd45ef
device-generic-x86_64: add non-free fw subpackage (MR 4728) 2024-01-30 12:47:17 -08:00
Pablo Correa Gómez
cf69326222
device/*: rebuild all devices (MR 4551)
[ci:ignore-count]
2024-01-22 19:32:30 +01:00
Oliver Smith
44989cfce7
device-generic-x86_64: modules-initfs: add nvme (MR 4723) 2024-01-14 19:31:06 +00:00
Clayton Craft
d7dbabe46f
device-generic-x86_64: split off oem-specific packages (MR 4673)
This uses oem-specific packages for configuring Intel and AMD systems,
and installs them all by default for new images using pmbootstrap's
pmb_recommends feature.

The intention is to provide pre-built images with support for Intel and
AMD already enabled/configured, and users can remove an unwanted set of
packages (e.g., `apk del device-generic-x86_64-intel` when on an AMD
system) if they want to.

Upgrading existing systems should work, in that I haven't observed any
apk conflicts with it. But you do need to manually install the new
oem-specific package if you need it (e.g. `oem-intel`)

fixes https://gitlab.com/postmarketOS/pmaports/-/issues/2484
2024-01-09 21:56:39 +01:00
Clayton Craft
93b904420a
device-generic-x86_64: new aport (MR 4554)
This device package is intended to replace the tablet-x*uefi device
packages. It was made by basically merging config from those two
packages.

One important change (besides the name, covered later) is that it
replaces grub-efi with sd-boot for these devices.

The pkgver is starting at '8' to get ahead of the packages this is meant
to replace.

Because package names, especially for device packages(!), is important,
here's a long explanation of why the name is "device-generic-x86_64":

"uefi" was excluded from the device package name, because it should (in
theory at least...) be able to simultaneously support EFI and non-EFI
boot in 1 device package. The device-qemu-amd64 package kiiiinda does
this already and could be a useful example for how to do that, though in
this situation we'd need to support syslinux for legacy boot instead of
what qemu does (bypass installed bootloader and directly boot the
kernel). In other words, the packages this one is meant to replace only
support EFI boot, they currently don't support legacy boot. So IF we
need to support legacy boot in the future and IF there's no way to
support both in one package, THEN we can consider changing the name of
this one or calling the other "-legacy" or something.

"x86_64" instead of "amd64" (like the device-qemu-amd64 device package),
because "x86_64" is what Alpine uses to refer to this arch, and it
doesn't have a hw vendor name baked into it.

"tablet" was dropped from the name, because there are many other x86_64 devices
out there that people might want to install pmOS. For example, it might be
confusing if you want to install pmOS on an x86_64 toaster but best
pmOS image for it is named "device-tablet-..."
2023-12-29 21:24:52 +02:00