ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-20 14:13:09 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
22852f2e50
genode/repos/gems/recipes/raw/drivers_managed-pc/drivers.config

267 lines
11 KiB
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 11:30:37 +00:00
<config prio_levels="2">
<parent-provides>
<service name="ROM"/>
<service name="IRQ"/>
<service name="IO_MEM"/>
<service name="IO_PORT"/>
<service name="PD"/>
<service name="RM"/>
<service name="CPU"/>
<service name="LOG"/>
<service name="Timer"/>
<service name="Report"/>
Turn framebuffer drivers into capture clients This patch replaces the use of the "Framebuffer" session interface by the new "Capture" session interface in all framebuffer drivers. Thanks to this change, those drivers have become mere clients of the nitpicker GUI server now, and are no longer critical for the liveliness of the GUI server. The patch touches the following areas: - The actual driver components. The new versions of all drivers have been tested on the respective hardware. Generally, the drivers have become simpler. - The drivers_interactive packages for various boards. The drivers subsystem no longer provides a "Framebuffer" service but needs a valid route to the "Capture" service provided by nitpicker. - The driver manager of Sculpt OS. - This patch changes the role of the test-framebuffer component from a framebuffer client to a capture server so that drivers (capture clients) can be directly connected to the test component without the nitpicker server. - Framebuffer driver no longer support the unbuffered mode. - The fb_bench.run script is no longer very meaningful because it interplays solely with nitpicker, not with the driver directly. - All run scripts for graphical scenarios and the related depot archives got adapted to the change. Fixes #3813
2020-07-01 20:26:11 +00:00
<service name="Capture"/>
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 09:28:18 +00:00
<service name="Event"/>
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 11:30:37 +00:00
</parent-provides>
driver_manager: use componentized usb driver Fixes #3943
2020-11-06 12:23:26 +00:00
<report child_caps="true" child_ram="true" init_caps="true" init_ram="true" delay_ms="5000"/>
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 11:30:37 +00:00
<default-route>
<any-service> <parent/> <any-child/> </any-service>
</default-route>
<default caps="100"/>
<service name="Block">
<default-policy> <child name="dynamic"/> </default-policy> </service>
<service name="Usb">
<default-policy> <child name="usb_drv"/> </default-policy> </service>
<service name="Platform">
<default-policy> <child name="platform_drv"/> </default-policy> </service>
sculpt: move pc-specifics away from generic part * Introduce sculpt-[board] specific package * Move rtc driver into managed drivers sub-system * Name nic_drv in a generic fashion in sculpt_manager * Copy over pc-specific config files only when building for PC Ref #3958
2020-11-24 11:24:26 +00:00
<service name="Rtc">
<default-policy> <child name="rtc_drv"/> </default-policy> </service>
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 10:37:46 +00:00
<start name="report_rom">
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 11:30:37 +00:00
<resource name="RAM" quantum="2M"/>
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 10:37:46 +00:00
<provides> <service name="Report"/> <service name="ROM"/> </provides>
<config verbose="no">
<policy label="platform_drv -> acpi" report="acpi_drv -> acpi"/>
<policy label="driver_manager -> pci_devices" report="platform_drv -> pci"/>
<policy label="usb_drv -> config" report="driver_manager -> usb_drv.config"/>
<policy label="driver_manager -> usb_devices" report="usb_drv -> devices"/>
<policy label="dynamic -> config" report="driver_manager -> init.config"/>
<policy label="driver_manager -> ahci_ports" report="dynamic -> ahci_ports"/>
driver_manager: add NVMe block driver Issue #2794.
2018-03-23 15:39:45 +00:00
<policy label="driver_manager -> nvme_ns" report="dynamic -> nvme_ns"/>
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 10:37:46 +00:00
<policy label="rom_reporter -> acpi" report="acpi_drv -> acpi"/>
<policy label="rom_reporter -> pci_devices" report="platform_drv -> pci"/>
<policy label="rom_reporter -> usb_devices" report="usb_drv -> devices"/>
driver_manager: use componentized usb driver Fixes #3943
2020-11-06 12:23:26 +00:00
<policy label="usb_hid_drv -> report" report="usb_drv -> devices"/>
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 10:37:46 +00:00
</config>
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 11:30:37 +00:00
</start>
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 10:37:46 +00:00
<start name="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 11:30:37 +00:00
<resource name="RAM" quantum="1M"/>
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 10:37:46 +00:00
<config>
<rom label="acpi"/>
<rom label="pci_devices"/>
<rom label="usb_devices"/>
</config>
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 11:30:37 +00:00
<route>
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 10:37:46 +00:00
<service name="ROM" label="acpi"> <child name="report_rom"/> </service>
<service name="ROM" label="pci_devices"> <child name="report_rom"/> </service>
<service name="ROM" label="usb_devices"> <child name="report_rom"/> </service>
<service name="Report" label="acpi"> <parent label="acpi"/> </service>
<service name="Report" label="pci_devices"> <parent label="pci_devices"/> </service>
<service name="Report" label="usb_devices"> <parent label="usb_devices"/> </service>
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 11:30:37 +00:00
<service name="LOG"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="ROM"> <parent/> </service>
</route>
</start>
sculpt: increase acpi_drv resources to satisfy T470p
2018-03-23 12:35:24 +00:00
<start name="acpi_drv" caps="350" priority="-1">
<resource name="RAM" quantum="4M"/>
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 11:30:37 +00:00
<route>
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 10:37:46 +00:00
<service name="Report" label="acpi"> <child name="report_rom"/> </service>
drivers_managed-pc: route for smbios_table report
2019-08-27 17:29:19 +00:00
<service name="Report" label="smbios_table"> <parent label="smbios_table"/> </service>
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 11:30:37 +00:00
<service name="IO_MEM"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="RM"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="ROM"> <parent/> </service>
</route>
</start>
base: extend PD session with managing_system call Introduce the managing_system privilege for components like the platform_driver to allow it to call system management functionality that is reserved by kernel or special firmware, e.g., ARM Trusted Firmware. The former RAM resource configuration attribute `constrain_phys`, which enabled to constrain the region of physical RAM to be used, gets replaced by the new, broader managing_system configuration attribute of a `start` node. It gets enforced by the sandbox library. Ref #3816
2020-07-10 11:04:12 +00:00
<start name="platform_drv" caps="400" managing_system="yes">
<resource name="RAM" quantum="4M"/>
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 11:30:37 +00:00
<provides>
<service name="Platform"/>
<service name="Acpi"/>
</provides>
<route>
drivers_managed-pc: support system reset
2017-12-01 14:06:35 +00:00
<service name="ROM" label="system"> <parent label="system"/> </service>
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 10:37:46 +00:00
<service name="ROM" label="acpi"> <child name="report_rom"/> </service>
<service name="Report" label="pci"> <child name="report_rom"/> </service>
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 11:30:37 +00:00
<service name="IRQ"> <parent/> </service>
<service name="IO_MEM"> <parent/> </service>
<service name="IO_PORT"> <parent/> </service>
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
</route>
drivers_managed-pc: support system reset
2017-12-01 14:06:35 +00:00
<config system="yes">
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 11:30:37 +00:00
<report pci="yes"/>
<policy label_prefix="ps2_drv"> <device name="PS2"/> </policy>
<policy label_prefix="dynamic -> vesa_fb_drv"> <pci class="VGA"/> </policy>
<policy label_prefix="dynamic -> ahci_drv"> <pci class="AHCI"/> </policy>
driver_manager: add NVMe block driver Issue #2794.
2018-03-23 15:39:45 +00:00
<policy label_prefix="dynamic -> nvme_drv"> <pci class="NVME"/> </policy>
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 11:30:37 +00:00
<policy label_prefix="usb_drv"> <pci class="USB"/> </policy>
dde_linux: update intel_fb to 4.16.3 Fixes #2736
2018-04-09 21:33:34 +00:00
<policy label_prefix="dynamic -> intel_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 11:30:37 +00:00
<pci class="VGA"/>
<pci bus="0" device="0" function="0"/>
<pci class="ISABRIDGE"/>
</policy>
drivers_managed-pc: support audio, acpica
2017-11-10 14:30:17 +00:00
<policy label_suffix="-> wifi"> <pci class="WIFI"/> </policy>
<policy label_suffix="-> nic"> <pci class="ETHERNET"/> </policy>
<policy label_suffix="-> audio"> <pci class="AUDIO"/> <pci class="HDAUDIO"/> </policy>
<policy label="acpica"> </policy>
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 11:30:37 +00:00
</config>
</start>
drivers_managed-pc: propagate keyboard LEDs This patch supplements the drivers subsystem with the ability to propagate the global capslock and numlock states to PS/2 and USB HID keyboards.
2017-11-08 14:15:24 +00:00
<start name="usb_drv" caps="200" priority="-1">
driver_manager: use componentized usb driver Fixes #3943
2020-11-06 12:23:26 +00:00
<binary name="x86_pc_usb_host_drv"/>
driver manager: increase RAM quota for usb_drv Without this patch, usb_drv would issue a resource request when assigning a USB device to a VM in the sculpt scenario. Furthermore, the patch adjusts the intel_fb quota to enable it on devices where the driver allocates the framebuffer in many 4K pieces.
2017-10-20 05:56:15 +00:00
<resource name="RAM" quantum="16M"/>
Turn USB HID drivers into event-session clients Issue #3845
2020-08-13 14:03:59 +00:00
<provides> <service name="Usb"/> </provides>
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 11:30:37 +00:00
<route>
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 10:37:46 +00:00
<service name="Platform"> <child name="platform_drv"/> </service>
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 11:30:37 +00:00
<service name="ROM" label="config">
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 10:37:46 +00:00
<child name="report_rom"/> </service>
<service name="Report" label="devices"> <child name="report_rom"/> </service>
<service name="Report" label="config"> <parent label="usb_active_config"/> </service>
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 11:30:37 +00:00
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="RM"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
</route>
</start>
driver_manager: use componentized usb driver Fixes #3943
2020-11-06 12:23:26 +00:00
<start name="usb_hid_drv" caps="140" priority="-1">
<resource name="RAM" quantum="11M"/>
<config use_report="yes" capslock_led="rom" numlock_led="rom"/>
<route>
<service name="ROM" label="report"> <child name="report_rom"/> </service>
<service name="ROM" label="capslock"> <parent label="capslock"/> </service>
<service name="ROM" label="numlock"> <parent label="numlock"/> </service>
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="RM"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
<service name="Event"> <child name="event_filter" label="usb"/> </service>
<service name="Usb"> <child name="usb_drv"/> </service>
</route>
</start>
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 11:30:37 +00:00
<start name="ps2_drv" priority="0">
<resource name="RAM" quantum="1M"/>
drivers_managed-pc: propagate keyboard LEDs This patch supplements the drivers subsystem with the ability to propagate the global capslock and numlock states to PS/2 and USB HID keyboards.
2017-11-08 14:15:24 +00:00
<config capslock_led="rom" numlock_led="rom"/>
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 11:30:37 +00:00
<route>
<service name="Platform"> <child name="platform_drv"/> </service>
Turn PS/2 driver into event-session client Issue #3845
2020-08-13 11:39:09 +00:00
<service name="Event"> <child name="event_filter" label="ps2"/> </service>
drivers_managed-pc: propagate keyboard LEDs This patch supplements the drivers subsystem with the ability to propagate the global capslock and numlock states to PS/2 and USB HID keyboards.
2017-11-08 14:15:24 +00:00
<service name="ROM" label="capslock"> <parent label="capslock"/> </service>
<service name="ROM" label="numlock"> <parent label="numlock"/> </service>
input/ps2: poll for mouse-reset results The PS/2 driver retries to get mouse-reset results for 700 ms, sleeping after each attempt for 10 ms. So, the driver needs a Timer session now. Fixes #2713
2018-08-17 15:26:30 +00:00
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
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 11:30:37 +00:00
</route>
</start>
sculpt: move pc-specifics away from generic part * Introduce sculpt-[board] specific package * Move rtc driver into managed drivers sub-system * Name nic_drv in a generic fashion in sculpt_manager * Copy over pc-specific config files only when building for PC Ref #3958
2020-11-24 11:24:26 +00:00
<start name="rtc_drv" priority="-1">
<resource name="RAM" quantum="1M"/>
<provides> <service name="Rtc"/> </provides>
<route>
<service name="IO_PORT"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="RM"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="ROM"> <parent/> </service>
</route>
</start>
driver_manager-pc: numlock handling This patch incorporates key remapping rules for the input filter that depend on the global numlock state.
2017-11-20 20:28:18 +00:00
<!-- toggle key mappings depending on the numlock state -->
<start name="numlock_remap_rom" priority="-1">
<binary name="rom_filter"/>
<resource name="RAM" quantum="1M"/>
<provides> <service name="ROM"/> </provides>
<route>
<service name="ROM" label="config"> <parent label="numlock_remap.config"/> </service>
<service name="ROM" label="numlock"> <parent label="numlock"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
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 09:28:18 +00:00
<start name="event_filter" caps="90" priority="-1">
drivers_managed-pc: propagate keyboard LEDs This patch supplements the drivers subsystem with the ability to propagate the global capslock and numlock states to PS/2 and USB HID keyboards.
2017-11-08 14:15:24 +00:00
<resource name="RAM" quantum="2M"/>
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 09:28:18 +00:00
<provides> <service name="Event"/> </provides>
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 11:30:37 +00:00
<route>
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 09:28:18 +00:00
<service name="ROM" label="config"> <parent label="event_filter.config"/> </service>
driver_manager-pc: numlock handling This patch incorporates key remapping rules for the input filter that depend on the global numlock state.
2017-11-20 20:28:18 +00:00
<service name="ROM" label="numlock.remap"> <child name="numlock_remap_rom"/> </service>
drivers_managed-pc: propagate keyboard LEDs This patch supplements the drivers subsystem with the ability to propagate the global capslock and numlock states to PS/2 and USB HID keyboards.
2017-11-08 14:15:24 +00:00
<service name="ROM" label="capslock"> <parent label="capslock"/> </service>
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 11:30:37 +00:00
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
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 09:28:18 +00:00
<service name="Event"> <parent/> </service>
</route>
</start>
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 11:30:37 +00:00
<start name="driver_manager" priority="-1">
<resource name="RAM" quantum="1M"/>
<route>
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 10:37:46 +00:00
<service name="Report" label="init.config"> <child name="report_rom"/> </service>
<service name="Report" label="usb_drv.config"> <child name="report_rom"/> </service>
<service name="Report" label="block_devices"> <parent label="block_devices"/> </service>
<service name="ROM" label="usb_devices"> <child name="report_rom"/> </service>
<service name="ROM" label="pci_devices"> <child name="report_rom"/> </service>
<service name="ROM" label="ahci_ports"> <child name="report_rom"/> </service>
driver_manager: add NVMe block driver Issue #2794.
2018-03-23 15:39:45 +00:00
<service name="ROM" label="nvme_ns"> <child name="report_rom"/> </service>
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 11:30:37 +00:00
<service name="LOG"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="ROM"> <parent/> </service>
</route>
</start>
drivers.config: accommodate intel_fb_drv CAP quota
2017-11-17 13:51:42 +00:00
<start name="dynamic" caps="1400" priority="0">
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 11:30:37 +00:00
<binary name="init"/>
<resource name="RAM" quantum="1G"/>
<provides>
<service name="Framebuffer"/>
<service name="Block"/>
</provides>
<route>
<service name="Platform"> <child name="platform_drv"/> </service>
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 10:37:46 +00:00
<service name="Report" label="ahci_ports"> <child name="report_rom"/> </service>
driver_manager: add NVMe block driver Issue #2794.
2018-03-23 15:39:45 +00:00
<service name="Report" label="nvme_ns"> <child name="report_rom"/> </service>
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 10:37:46 +00:00
<service name="Report"> <parent/> </service>
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 11:30:37 +00:00
<service name="Usb"> <child name="usb_drv"/> </service>
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 10:37:46 +00:00
<service name="ROM" label="config"> <child name="report_rom"/> </service>
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 11:30:37 +00:00
<service name="LOG"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="RM"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="ROM"> <parent/> </service>
<service name="IO_MEM"> <parent/> </service>
<service name="IO_PORT"> <parent/> </service>
<service name="Timer"> <parent/> </service>
Turn framebuffer drivers into capture clients This patch replaces the use of the "Framebuffer" session interface by the new "Capture" session interface in all framebuffer drivers. Thanks to this change, those drivers have become mere clients of the nitpicker GUI server now, and are no longer critical for the liveliness of the GUI server. The patch touches the following areas: - The actual driver components. The new versions of all drivers have been tested on the respective hardware. Generally, the drivers have become simpler. - The drivers_interactive packages for various boards. The drivers subsystem no longer provides a "Framebuffer" service but needs a valid route to the "Capture" service provided by nitpicker. - The driver manager of Sculpt OS. - This patch changes the role of the test-framebuffer component from a framebuffer client to a capture server so that drivers (capture clients) can be directly connected to the test component without the nitpicker server. - Framebuffer driver no longer support the unbuffered mode. - The fb_bench.run script is no longer very meaningful because it interplays solely with nitpicker, not with the driver directly. - All run scripts for graphical scenarios and the related depot archives got adapted to the change. Fixes #3813
2020-07-01 20:26:11 +00:00
<service name="Capture"> <parent/> </service>
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 11:30:37 +00:00
</route>
</start>
</config>
Reference in New Issue Copy Permalink