uefi-x86_64: introduce generic "device" and system type #253
Conversation
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
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
from
e6b0f45
to
7fb5dcc
Compare
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
from
7fb5dcc
to
0f14c8a
Compare
1 task
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
4 times, most recently
from
e54f64f
to
a21dbfb
Compare
The same changes have been made in the upcoming UEFI equivalent file.
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
from
a21dbfb
to
615de0a
Compare
Fixes menuconfig for 5.10 for chuwi hi10 pro
Like intel-based hardware
Will be used to pass along extra properties for devies, e.g. libinput calibration matrix.
This is the minimum viable product. This builds a disk image that can be booted.
For the time being, this is mostly a copy of the QEMU system. The QEMU system is slated to be removed, once the UEFI system provides the necessary tooling to get a VM going easily. We'll probably want to add other generically-useful modules to that system. We'll have to look at NixOS's boot.initrd.availableKernelModules and boot.initrd.kernelModules options.
This is basically what I think are the minimum requirements for support. 720p display, 2GB of RAM. Not that it will be a great experience.
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
from
615de0a
to
ebf3d3a
Compare
This results in a script that launches a QEMU VM.
It is incomplete because it does not use the (not implemented) VM attribute.
It's being replaced by the generic uefi-x86_64 device. Basically, replace the QEMU-specific system type by the totally standard UEFI system type. This way we're dogfooding it way better!
samueldr
force-pushed
the
feature/uefi-generic-x86_64
branch
from
ebf3d3a
to
04b8e4c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Built on top of #262)
This replaces the too-specific QEMU system type and device.
The image this produce has not yet been tested on a real-world device. It's probably somewhat wrong because it uses a hapazard collection of kernel modules coming from the previous QEMU device build.
While this introduces the ability to bring-in generic hardware, it's not really the purpose of this PR. We're not going to add every computer under the sun in this project. The goal is to (1) add UEFI support and (2) revisit the QEMU VM.
Any extra device can be added to an "extra-devices" type of repository. I will be doing it soon for the CHUWI Hi10 Pro HQ64, at the very least, as it is a tablet, and it requires a custom-enough kernel that it is worth it to do a custom build.
Fixes #8.
TODO
In the future, a generic AArch64 UEFI device should be added too, where the
.vmwork as expected, with KVM on AArch64.