ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-19 05:37:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Minor corrections in the 16.11 release notes

Browse Source
This commit is contained in:
Josef Söntgen 2016-12-02 13:16:40 +01:00 committed by Norman Feske
parent 25a7ea3d40
commit ecff6f7375
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/release_notes-16-11.txt
View File

@ -18,7 +18,7 @@ certain style of programming. Over the years, the drawbacks inherent in our
original design became more and more clear and we drafted rough plans to original design became more and more clear and we drafted rough plans to
overcome them. However, reworking the fundamental protocols of a system that overcome them. However, reworking the fundamental protocols of a system that
already accommodates hundreds of component implementations cannot be taken already accommodates hundreds of component implementations cannot be taken
light-handily. Because of this discomfort, we repeatedly deferred the topic - lightly. Because of this discomfort, we repeatedly deferred the topic -
until now. With the rapidly growing workloads carried by Genode, we until now. With the rapidly growing workloads carried by Genode, we
deliberately decided to address long-standing deficiencies rather than adding deliberately decided to address long-standing deficiencies rather than adding
the features we originally planned according to the the features we originally planned according to the
@ -46,9 +46,7 @@ Further topics of the current release range from added smart-card support,
over a new timeout API, to a VFS-based time-based password generator. With over a new timeout API, to a VFS-based time-based password generator. With
respect to the road map, we postponed most topics originally planned. In respect to the road map, we postponed most topics originally planned. In
particular, we intended to enable the use of Genode on top of Xen by following particular, we intended to enable the use of Genode on top of Xen by following
With respect to the road map, we postponed most topics originally planned for the footsteps of the existing Muen support - using our custom
this release. Originally, we intended to enable the use of Genode on top of
Xen by following the footsteps of the existing Muen support - using our custom
base-hw kernel within a Xen DomU domain. However, before proceeding this base-hw kernel within a Xen DomU domain. However, before proceeding this
route, we decided to modernize the kernel design, in particular with respect route, we decided to modernize the kernel design, in particular with respect
to bootstrapping and address-space management. Some parts of this line of work to bootstrapping and address-space management. Some parts of this line of work
@ -169,7 +167,7 @@ are twofold. First, our workaround for realizing runtime environments in a
multi-threaded way worked too well. So we were not constantly bothered by this multi-threaded way worked too well. So we were not constantly bothered by this
design problem. Second and more importantly, redesigning the fundamental design problem. Second and more importantly, redesigning the fundamental
mechanism of the framework while not breaking the more than 300 existing mechanism of the framework while not breaking the more than 300 existing
components is quite scary. But in anticipation to the rapidly scaling components is quite scary. But in anticipation of the rapidly scaling
workloads imposed on Genode, we had to take on the problem sooner or later. workloads imposed on Genode, we had to take on the problem sooner or later.
We figured that now - with the modernized framework API in place - it's the We figured that now - with the modernized framework API in place - it's the
right time. From redesigning the interplay of parent and child components, we right time. From redesigning the interplay of parent and child components, we