ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2025-03-12 15:34:23 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
genode/repos/gems/recipes/pkg/drivers_managed-pc/archives

18 lines
301 B
Plaintext
Raw Normal View History

gems: driver-manager subsystem for PC platforms This is a drivers subsystem that starts the most fundamental (framebuffer, input, block) device drivers dynamically, depending on the runtime-detected devices. The discovered block devices are reported as a "block_devices" report.
2017-06-30 13:30:37 +02:00
_/src/platform_drv
_/src/acpi_drv
_/src/ps2_drv
driver_manager: use componentized usb driver Fixes #3943
2020-11-06 13:23:26 +01:00
_/src/usb_host_drv
_/src/usb_hid_drv
gems: driver-manager subsystem for PC platforms This is a drivers subsystem that starts the most fundamental (framebuffer, input, block) device drivers dynamically, depending on the runtime-detected devices. The discovered block devices are reported as a "block_devices" report.
2017-06-30 13:30:37 +02:00
_/src/usb_block_drv
_/src/vesa_drv
_/src/intel_fb_drv
driver_manager: add fb_boot_drv support
2017-10-25 22:30:32 +02:00
_/src/boot_fb_drv
gems: driver-manager subsystem for PC platforms This is a drivers subsystem that starts the most fundamental (framebuffer, input, block) device drivers dynamically, depending on the runtime-detected devices. The discovered block devices are reported as a "block_devices" report.
2017-06-30 13:30:37 +02:00
_/src/ahci_drv
drivers_managed-pc: simplification This patch removes the former use of ram_fs, fs_rom, and fs_report from the subsystem and uses a report_rom instead. The fs-based reporting was introduced to accommodate automatically instantiated usb_block drivers, which turned out to be impractical for the sculpt scenario.
2017-12-14 11:37:46 +01:00
_/src/report_rom
Replace input filter with event filter This commit applies the transition from the "Input" session to the "Event" session to the event-filtering mechansim. The functionality of the input_filter is now provided by the event_filter. The event filter requests only one "Event" session as destination for the filter result, which is usually routed to the nitpicker GUI server. It provides an "Event" service to which any number of event sources can connect. The configuration of the filter chain remains almost the same. Only the declaration of the <input> nodes is no longer needed. Instead, the configuration must specify <policy> nodes, which define the mapping of "Event" clients (event sources) to the inputs used in the filter chain. The patch adjusts all uses of the nitpicker GUI server accordingly such that the event filter reports events to nitpicker's event service instead of having nitpicker request an "Input" session. This dissolves the dependency of nitpicker from input drivers. Issue #3827
2020-07-16 11:28:18 +02:00
_/src/event_filter
gems: driver-manager subsystem for PC platforms This is a drivers subsystem that starts the most fundamental (framebuffer, input, block) device drivers dynamically, depending on the runtime-detected devices. The discovered block devices are reported as a "block_devices" report.
2017-06-30 13:30:37 +02:00
_/src/init
_/src/driver_manager
drivers_managed-pc: simplification This patch removes the former use of ram_fs, fs_rom, and fs_report from the subsystem and uses a report_rom instead. The fs-based reporting was introduced to accommodate automatically instantiated usb_block drivers, which turned out to be impractical for the sculpt scenario.
2017-12-14 11:37:46 +01:00
_/src/rom_filter
_/src/rom_reporter
gems: driver-manager subsystem for PC platforms This is a drivers subsystem that starts the most fundamental (framebuffer, input, block) device drivers dynamically, depending on the runtime-detected devices. The discovered block devices are reported as a "block_devices" report.
2017-06-30 13:30:37 +02:00
_/raw/drivers_managed-pc
Reference in New Issue Copy Permalink