ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-23 15:32:25 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
9662d89cfb
genode/repos/os/run/loader.run

74 lines
2.0 KiB
Plaintext
Raw Normal View History

Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
create_boot_directory
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
import_from_depot [depot_user]/src/[base_src] \
[depot_user]/pkg/[drivers_interactive_pkg] \
[depot_user]/src/init \
[depot_user]/src/nitpicker
build {
server/loader
test/loader
test/nitpicker
}
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
install_config {
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<config>
<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"/>
</parent-provides>
<default-route>
<any-service> <parent/> <any-child/> </any-service>
Assign cap quotas in run scripts and recipes Issue #2398
2017-05-07 20:36:11 +00:00
</default-route>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
<default caps="100"/>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="timer">
<resource name="RAM" quantum="1M"/>
<provides><service name="Timer"/></provides>
</start>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
Change pixel format to 32 bits per pixel Until now, Genode's framebuffer session interface was based on the RGB565 pixel format. This patch changes the pixel format to 32-bit XRGB where the X part is ignored. It adapts all graphical applications and device drivers accordingly. The patch also adjusts the users of the drivers_interactive packages, assigning 64 MiB RAM and 1500 caps to the drivers subsystem, which is sufficient for covering high resolutions at 32 bits per pixel and to accommodate multi-component USB HID input stacks. Fixes #3784
2020-06-16 13:46:59 +00:00
<start name="drivers" caps="1500">
<resource name="RAM" quantum="64M" constrain_phys="yes"/>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
<binary name="init"/>
<route>
<service name="ROM" label="config"> <parent label="drivers.config"/> </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="Timer"> <child name="timer"/> </service>
<service name="Capture"> <child name="nitpicker"/> </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"> <child name="nitpicker"/> </service>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
<any-service> <parent/> </any-service>
</route>
</start>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="nitpicker">
<resource name="RAM" quantum="1M"/>
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="Gui"/> <service name="Capture"/> <service name="Event"/>
</provides>
<config request_framebuffer="no" request_input="no">
<capture/> <event/>
Ajdust run scenarios for strict policy matching Issue #1901
2016-03-09 14:32:23 +00:00
<domain name="" layer="2" /> <default-policy domain=""/>
Adapt run scripts to nitpicker config changes
2014-07-18 14:12:19 +00:00
</config>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
</start>
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<start name="loader">
<resource name="RAM" quantum="1M"/>
<provides><service name="Loader"/></provides>
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
<config>
Make label prefixing more strict This patch unconditionally applies the labeling of sessions and thereby removes the most common use case of 'Child_policy::filter_session_args'. Furthermore, the patch removes an ambiguity of the session labels of sessions created by the parent of behalf of its child, e.g., the PD session created as part of 'Child' now has the label "<child-name>" whereas an unlabeled PD-session request originating from the child has the label "<child-name> -> ". This way, the routing-policy of 'Child_policy::resolve_session_request' can differentiate both cases. As a consequence, the stricter labeling must now be considered wherever a precise label was specified as a key for a session route or a server- side policy selection. The simplest way to adapt those cases is to use a 'label_prefix' instead of the 'label' attribute. Alternatively, the 'label' attribute may used by appending " -> " (note the whitespace). Fixes #2171
2016-11-24 14:28:32 +00:00
<policy label_prefix="test-loader">
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
<parent-rom name="testnit"/>
Build dynamically linked executables by default Fixes #2184
2016-12-01 18:00:11 +00:00
<parent-rom name="ld.lib.so"/>
Adapt low-level components to new parent interface This patch adjusts the components of the os repository as well as device drivers to the new parent interface. Issue #2120
2016-11-06 13:27:26 +00:00
</policy>
</config>
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
</start>
Assign cap quotas in run scripts and recipes Issue #2398
2017-05-07 20:36:11 +00:00
<start name="test-loader" caps="200">
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
<resource name="RAM" quantum="1G"/>
</start>
</config>}
run: use drivers_interactive-* pkg where possible Ref #2190
2019-05-03 11:19:17 +00:00
build_boot_image { testnit loader test-loader }
Re-implementation of the loader service, ref #187 The original loader service was primarily motivated by the browser-plugin scenario presented on our live CD. The new version implements a more general session interface, which widens the application scope of the service and, at the same time, reduces its implementation complexity. The complexity reduction is achieved by removing the original limitation of supplying the new sub system as a single binary blob only. The server used to implement heuristics and functionality for dealing with different kinds of blobs such as ELF images or TAR archives. This has been replaced by a session-local ROM service, which can be equipped with an arbitrary number of ROM modules supplied by the loader client prior starting the new sub system. Even though the TAR support has been removed, a separate instance of the 'tar_rom' service can be used within the subsystem to provide the formerly built-in functionality.
2012-04-17 16:46:14 +00:00
run_genode_until forever
Reference in New Issue Copy Permalink