mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 18:17:44 +00:00
Kernel/Graphics: Simplify the feature level of the Graphics subsystem
Instead of letting the user to determine whether framebuffer devices will be created (which is useless because they are gone by now), let's simplify the flow by allowing the user to choose between full, limited or disabled functionality. The determination happens only once, so, if the user decided to disable graphics support, the initialize method exits immediately. If limited functionality is chosen, then a generic DisplayConnector is initialized with the preset framebuffer resolution, if present, and then the initialize method exits. As a default, the code proceeds to initialize all drivers as usual.
This commit is contained in:
parent
e301af8352
commit
d49a35df31
5 changed files with 35 additions and 50 deletions
|
@ -47,7 +47,8 @@ List of options:
|
|||
but only if **`acpi`** is set to **`limited`** or **`on`**, and a `MADT` (APIC) table is available.
|
||||
Otherwise, the kernel will fallback to use the i8259 PICs.
|
||||
|
||||
* **`fbdev`** - This parameter expects one of the following values. **`on`**- Boot into the graphical environment (default). **`off`** - Boot into text mode. **`bootloader`** - Boot into the graphical environment, but only use the frame buffer set up by the bootloader and do not initialize any other graphics cards.
|
||||
* **`graphics_subsystem_mode`** - This parameter expects one of the following values. **`on`**- Boot into the graphical environment if possible (default). **`off`** - Boot into text mode, don't initialize any driver. **`limited`** - Boot into the pre-defined framebuffer that the bootloader
|
||||
has set up before booting the Kernel, don't initialize any driver.
|
||||
|
||||
* **`force_pio`** - If present on the command line, the IDE controllers will be force into PIO mode when initialized IDE Channels on boot.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue