version: 17.02

It seems the download site vanished. Also, the utility remained unused
since years now.

LICENSE

@@ -1,280 +1,701 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 2, June 1991
 
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+                        Linking exception clause
+
+
+  The Genode OS Framework (Genode) is licensed under the terms of the
+  GNU Affero General Public License version 3 (AGPLv3).
+
+  Linking Genode code statically or dynamically with other modules
+  is making a combined work based on Genode. Thus, the terms and
+  conditions of the AGPLv3 cover the whole combination.
+
+  As an "additional permission" as defined by Section 7 of the
+  AGPLv3, Genode Labs as the copyright holder of Genode gives you
+  permission to link Genode source code with "independent modules"
+  to produce an executable if the independent modules are licensed
+  under an "approved license", and to copy and distribute the
+  resulting executable under terms of your choice, provided that you
+  also meet, for each linked independent module, the terms and
+  conditions of the license of that module.
+
+  An "approved license" is a license that is officially approved as
+  an Open-Source license by the Open Source Initiative [1], or
+  listed as a Free-Software license by the Free Software Foundation
+  [2], or explicitly approved by Genode Labs.
+
+  An "independent module" is a module which is not derived from or
+  based on Genode, or merely uses the Genode API as defined in the
+  official documentation.
+
+  If you modify Genode, you may extend this exception to your
+  version of Genode, but you are not obliged to do so. If you do not
+  wish to do so, delete this exception statement from your version.
+
+  [1] https://opensource.org/licenses
+  [2] https://www.gnu.org/licenses/license-list.en.html
+
+
+------------------------------------------------------------------------------
+
+
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
                             Preamble
 
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.)  You can apply it to
-your programs, too.
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
 
   When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
 have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
 
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
 
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
 
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
 
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
 
   The precise terms and conditions for copying, distribution and
 modification follow.
 
-                    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+                       TERMS AND CONDITIONS
 
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
+  0. Definitions.
 
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
+  "This License" refers to version 3 of the GNU Affero General Public License.
 
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
 
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
 
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
 
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
 
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
 
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
 
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
 
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
+  1. Source Code.
 
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
 
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
 
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
 
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
 
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
 
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
+  The Corresponding Source for a work in source code form is that
+same work.
 
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
+  2. Basic Permissions.
 
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
 
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
 
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
 this License.
 
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
 otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
 
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
+  13. Remote Network Interaction; Use with the GNU General Public License.
 
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
 
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
 
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
+  14. Revised Versions of this License.
 
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time.  Such new versions
+will be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
 
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
 
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
+  If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
 
-                            NO WARRANTY
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
 
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
+  15. Disclaimer of Warranty.
 
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
 
                      END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+<http://www.gnu.org/licenses/>.

VERSION

@@ -1 +1 @@
-16.11
+17.02

doc/challenges.txt

@@ -16,18 +16,16 @@ research projects on Genode.
 Applications and library infrastructure
 #######################################
 
-:Chrome web browser:
+:GNU Privacy Guard:
 
-  The Chrome web browser promises to address the most pressing security
-  concerns of web application by isolation measures, in particular the
-  sandboxing of plugins and the confinement of individual web applications. As
-  we demonstrated with the Genode Live CD 10.11, Genode facilitates a more
-  natural way to pursue such techniques compared with current commodity
-  operating systems. Furthermore, the use of Genode as base platform for Chrome
-  would strengthen the web-browser security by dwarfing its trusted computing
-  base by two orders of magnitude compared to the use of Linux as base
-  platform. This would allow Chrome to be considered as a secure interface to
-  the web for use cases in the high-assurance domain.
+  The [https://gnupg.org/ - GNU Privacy Guard] (GNUPG) is the most widely
+  used Free-Software implementation of the OpenGPG standard. It comprises a
+  rich set of tools for encryption and key management. For many forthcoming
+  application scenarios of Genode such as package management and email
+  communication, GNUPG is crucial. Hence, it should be ported to Genode. Such
+  a port may leverage Genode's fine-grained component architecture to strongly
+  separate network-exposed functionality, the storage of key material, and the
+  cryptographic functions.
 
 :VNC server implementing Genode's framebuffer session interface:
 
@@ -41,6 +39,17 @@ Applications and library infrastructure
   the network. One immediate application of this implementation is the remote
   testing of graphical Genode applications running on a headless server.
 
+:Interfacing with the SAFE network:
+
+  The [https://safenetwork.org/ - SAFE network] is an attempt to fix many
+  shortcomings of the internet - in particular with respect to privacy and
+  freedom - at an architectural level. It is a peer-to-peer communication
+  and storage network that does not depend on single point of
+  failure or control. It is intriguing to explore the opportunity of
+  integrating support for the SAFE network not merely as an application but
+  integrated in the operating system, i.e., in the form of Genode components
+  or a set of Genode VFS plugins.
+
 :Tiled window manager:
 
   At Genode Labs, we pursue the goal to shape Genode into an general-purpose
@@ -73,33 +82,11 @@ Applications and library infrastructure
   support for real-time priorities, this base techniques enable the creation of
   flexible audio mixer / switchboard applications, which require dedicated
   frameworks (e.g., Jack audio) on traditional operating systems. The goal of
-  this project is to create a show case implementation demonstrating the
+  this project is to create a showcase implementation demonstrating the
   feasibility for creating high-quality audio applications on Genode.
   Furthermore, we wish for feedback regarding the current design of our bulk
   streaming interface when used for low-latency applications.
 
-:PDF reader for E-Government use:
-
-  A facility for reading PDF and E-Book documents is one of the indispensable
-  features Genode has to provide to be considered for general-purpose
-  computing. The goal of this work is to identify a suitable open-source PDF
-  engine and port it as native application to Genode. The challenging part is
-  to keep the complexity of this application as low as possible in order to
-  enable the use of this application as a trusted document reader. Further
-  ideas envision the use of PDF files as medium for sensitive documents
-  combined with measures for protecting the integrity of the displayed
-  information. For example, when processing contracts or similar sensitive
-  documents in E-Government scenarios, the consumer of such documents expects
-  the correct display of all the information as expressed by the creator of the
-  document. In the event of a compromised PDF engine or a man-in-the middle
-  attacker manipulating the PDF file, the consumer of the document requires a
-  way to identify such security breaches. In this context, running the PDF
-  engine in a sandboxed Genode subsystem has two incentives. First, the attack
-  surface for manipulating the PDF engine gets dramatically reduced, and
-  second, the integrity of the result of the PDF engine can be measured by an
-  independent trusted component facilitating Genode secure GUI server
-  (Nitpicker).
-
 :Graphical on-target IPC tracing tool using Qt:
 
   Analysing the interaction of components of a multi-server operating system
@@ -129,180 +116,86 @@ Applications and library infrastructure
   of communicating threads as captured on the running system. The tool should
   work on a selected kernel that provides a facility for tracing IPC messages.
 
+:Ports of popular software:
 
-Application frameworks
-######################
-
-:Running the Meego application stack on Genode using Qt:
-
-  With Genode 11.02, Qt has become available. The most prominent feature
-  of this version is the new QML language to design GUIs using a declarative
-  language. This technique is targeted specifically to mobile applications and
-  other touch-based devices. The goal of this project is to run the Meego
-  application stack natively on Genode. First, the software components and
-  Meego-specific Linux customizations must be identified. For each such
-  component, it must be decided whether to port its code or to reimplement its
-  interface. The immediate goal of the first step is running one Meego example
-  application natively on Genode.
-
-:Python Qt bindings:
-
-  With the Python interpreter and the port of the Qt framework, the principle
-  components for Python-based GUIs on Genode are available. However, the glue
-  between both components is missing. The incentive of this work is supplementing
-  our Python port with the modules needed for real applications and porting the
-  Qt bindings to Genode. This would bring Genode one step closer to executing
-  modern Python-based GUI applications (in particular KDE4 applications).
-
-:Evaluation of porting GTK+ to Genode:
-
-  With Qt, we have demonstrated the feasibility to run a highly-complex
-  application framework via Genode on a wide range of microkernels. That leaves
-  the question of looking into the other major toolkit in town, namely GTK+ as
-  used by Firefox and the Gnome desktop.
-
-:Cairographics:
-
-  Cairo is a high-quality 2D vector graphics engine used by a large number of
-  open-source projects, in particular GTK+. Hence the port of Cairo is a
-  prerequisite for the GTK+ challenge. In addition, it would enable the
-  use of further libraries such as Poppler.
+  Genode features a ports mechanism to cleanly integrate 3rd-party software.
+  Thanks to the C runtime, the flexible per-component VFS, the standard
+  C++ library, and the Noux runtime (for UNIX software), porting software
+  to Genode is relatively straight forward. The
+  [http://genode.org/documentation/developer-resources/porting - porting guide]
+  explains the typical steps. A wish list of software that we'd like to
+  have available on Genode is available at
+  [http://usr.sysret.de/jws/genode/porting_wishlist.html].
 
 
-Device drivers
-##############
+Application frameworks and runtime environments
+###############################################
 
-:Enhancing Gallium3D support:
+:OpenJDK:
 
-  Genode 10.08 introduced Gallium3D including the GPU driver for Intel GMA
-  CPUs. With this initial version, we demonstrated that the powerful software
-  stack for running hardware-accelerated 3D applications can be deployed on
-  Genode. At the same time, it motivates us to reach out for even more
-  ambitious goals:
+  [http://openjdk.java.net/ - OpenJDK] is the reference implementation of the
+  Java programming language and hosts an enormous ecosystem of application
+  software. The goal of this line of work is the ability to run this
+  software directly on Genode. The centerpiece of OpenJDK is Hotspot - the
+  Java virtual machine implementation, which must be ported to Genode.
+  The initial port should suffice to execute simple example programs that
+  operate on textual input. Since Genode has the FreeBSD libc readily
+  available, OpenJDK's existing POSIX backends can be reused. The next step
+  is the creation of Genode-specific native classes that bridge the gap
+  between the Java world and Genode, in particular the glue code to
+  run graphical applications as clients of Genode's GUI server. Since
+  OpenJDK has been ported to numerous platforms (such as Haiku), there
+  exists a comforting number of implementations that can be taken as
+  reference.
 
-  First, the current approach executes the GPU driver alongside the complete
-  Gallium3D software stack and the application code in one address space. To
-  enable the use of multiple hardware-accelerated applications running at the
-  same time, the GPU driver must run separated from the Gallium3D code as done
-  on Linux. The preliminary interfaces for this decomposition are already in
-  place but there are several open questions. Most importantly, the page-fault
-  handling of buffer objects mapped in the application's address space.
+:Android's ART VM natively on Genode:
 
-  Second, we'd like to complement our current Intel GMA GPU driver with
-  interrupt-based synchronization, namely vblank handling. This requires an
-  understanding of the Intel GMA interrupt code and the enhancement of our
-  driver environment.
-
-  Third, we desire the use of further Gallium3D drivers, in particular the
-  Nouveau and r300 drivers. The basic approach to bring these drivers to Genode
-  is the same as for Intel GMA but the respective driver environments are yet
-  to be developed.
-
-  If you are interested in low-level graphics hacking, GPUs, and
-  high-performance graphics, this project is ideal to get you on track.
-
-:Split USB core from USB device drivers:
-
-  Genode's current USB support is based on the Linux USB stack running as a
-  single process on Genode. This process includes the USB core logic, USB host
-  controller driver as well as the USB device drivers such as HID or USB
-  storage. This monolithic USB process is rather inflexible. Hence, we desire a
-  decomposition of this solution such that the USB host driver and each USB
-  device driver runs in a separate process.
-
-:I/O Kit:
-
-  I/O Kit is the device-driver framework as used by the Darwin operating
-  system, which forms the basis for Mac OS X. The port of I/O Kit would enable
-  the easy re-use of the library of I/O-Kit-based device drivers on Genode. As
-  foundation of this project, we recommend to use the DDE Kit API featured by
-  Genode.
-
-:Support for multi-touch input devices:
-
-  The efforts towards enabling mobile application stacks such as Meego and
-  Android on Genode must be accompanied by a revision of Genode's 'Input'
-  session interface to accommodate multi-touch input devices. First, existing
-  APIs such as multi-touch support in X11, Qt, and Android should be analysed.
-  Based on these findings, we expect a proposal for changing Genode's input
-  interface. The interface extension should be validated by a example driver
-  implementing the interface as well as an example applications.
-
-
-System services
-###############
-
-:Copy-on-write memory manager:
-
-  Genode's managed dataspaces provide a generalized page-table concept,
-  enabling servers to provide on-demand paged memory objects (dataspaces) to
-  clients. This concept is showcased by the ISO9660 driver, which provides
-  on-demand paged ROM dataspaces to its clients. Depending on the access
-  pattern of the client, the ISO9660 server loads the used parts of the ROM
-  file from CDROM. Managed dataspaces principally allow for a wide variety of
-  interesting applications such as the transparent migration of non-local and
-  local memory in a NUMA system, sparse dataspaces, swapping, and copy-on-write
-  dataspaces. The goal of this project is a dataspace manager that implements
-  copy-on-write semantics combined with a merging technique optimizing the
-  memory footprint at runtime. Pages of two managed dataspaces that share the
-  same content should be provided via read-only page sharing. If one client
-  attempts to change the content of a shared page, a new physical copy of the
-  page get created. Vice versa, if the content of different pages converge, the
-  sharing should be re-established. This work is a follow-up of the diploma
-  thesis of Sebastian Sumpf
-  [http://os.inf.tu-dresden.de/papers_ps/sumpf-diplom.pdf - Cloning L4Linux].
-  On the course of this project, the managed dataspace concept of Genode
-  will be refined, in particular regarding the creation of read-only
-  dataspaces from read-write dataspaces.
-
-:Using Haskell as systems-development language:
-
-  The goal of this project is the application of functional programming
-  i.e., Haskell, for the implementation of low-level Genode components.
-  Implementing critical functionalities in such a high-level language instead
-  of a classical systems language such as C or C++ would pave the way towards
-  analyzing such components with formal methods.
-
-  The use of Haskell for systems development was pioneered by the
-  [http://programatica.cs.pdx.edu/House/ - House Project]. A more recent
-  development is [http://halvm.org - HalVM] - a light-weight OS runtime for
-  Xen that is based on Haskell.
-
-:Dbus emulation:
-
-  Dbus is a popular inter-process communication mechanism on Linux, which
-  enables user applications to respond to global system events and announce
-  state changes to other applications. It is extensively used by modern desktop
-  environments. To enable such applications to integrate well with Genode, a
-  Dbus emulation solution has to be developed.
-
-:Wayland:
-
-  With the availability of Gallium3D on Genode, the prospect for incorporating
-  further projects of the Linux graphics ecosystem into Genode arises.
-  [http://wayland.freedesktop.org - Wayland] is a window server especially
-  designed to be used with Gallium3D. Its design has many similarities with
-  Genode's Nitpicker GUI server, in particular the decision to move window
-  handling policies to the client and thereby minimize the complexity of the
-  GUI server. Whereas Nitpicker was designed for high security, Wayland is
-  targeted to creating GUIs with fluid and tearless animations using
-  hardware-accelerated graphics. We believe that because of the many conceptual
-  parallels with Nitpicker, Wayland would fit very well into the Genode system.
-  However, as a prerequisite for this project, Genode's Gallium3D support must
-  be decomposed first. See the challenges regarding our Gallium3D support for
-  further information.
-
-
-Runtime environments
-####################
-
-:Android's Dalvik VM natively on Genode:
-
-  Dalvik is a Java virtual machine that is used for executing applications on
-  Android. By running Dalvik directly on Genode, the Linux kernel could be
+  ART is a Java virtual machine that is used for executing applications on
+  Android. By running ART directly on Genode, the Linux kernel could be
   removed from the trusted computing base of Android, facilitating the use of
   this mobile OS in high-assurance settings.
 
+:Rust bindings for the Genode API:
+
+  Rust is a low-level systems programming language that ensures memory
+  safety without employing a garbage collector. It thereby challenges C++
+  as the go-to programming language for high-performance and low-level code.
+  Since
+  [http://genode.org/documentation/release-notes/16.05#New_support_for_the_Rust_programming_language - version 16.05],
+  Genode supports the use of the Rust programming language within
+  components. However, to unleash the potential of this combination,
+  Genode's API must become available to native Rust code. The intermediate goal
+  of this project is the implementation of an example server, e.g., a
+  component that provides a terminal-session interface. Thereby, we
+  will encounter the problems of bootstrapping and configuration of the
+  component, the provisioning of signal handlers and session objects, and
+  memory management.
+
+:Go language runtime:
+
+  Go is a popular language in particular for web applications. In the past,
+  there were numerous attempts to make the Go runtime available on Genode
+  but so far, none of those undertakings have landed in the official
+  Genode source tree. To goal of this project is the hosting of
+  Go-written applications - in particular networking applications - as
+  Genode components. The topic comprises work on the tool-chain
+  and build-system integration, the porting the runtime libraries, and
+  the glue between the Go and Genode environments.
+
+:Combination of CAmkES with Genode:
+
+  [https://wiki.sel4.systems/CAmkES - CAmkES] is a component framework for
+  seL4. In contrast to Genode, which is a dynamic system, CAmkES-based systems
+  are defined at design time and remain fixed at runtime. Hence, CAmkES and
+  Genode can be seen as the opposite ends of component-based used-land
+  architectures. The goal of this project is to build a bridge between
+  both projects with the potential to cross-pollinate the respective communities.
+  Among the principal approaches are embedding of a single CAmkES
+  component as a Genode component (e.g., an individual device driver),
+  the hosting of a dynamic Genode system as a component within a
+  CAmkES system, or the hosting of a CAmkES system composition as a Genode
+  subsystem.
+
 :Runtime for the D programming language:
 
   The D systems programming language was designed to overcome many gripes that
@@ -316,23 +209,141 @@ Runtime environments
   programs, and interfacing D programs with other Genode components written in
   C++.
 
+:Using Haskell as systems-development language:
+
+  The goal of this project is the application of functional programming
+  i.e., Haskell, for the implementation of low-level Genode components.
+  Implementing critical functionalities in such a high-level language instead
+  of a classical systems language such as C or C++ would pave the way towards
+  analyzing such components with formal methods.
+
+  The use of Haskell for systems development was pioneered by the
+  [http://programatica.cs.pdx.edu/House/ - House Project]. A more recent
+  development is [http://halvm.org - HalVM] - a light-weight OS runtime for
+  Xen that is based on Haskell.
+
+
+Virtualization
+##############
+
+:VirtualBox on top of KVM on Linux:
+
+  Genode's version of VirtualBox replaces the original in-kernel VirtualBox
+  hypervisor by the virtualization mechanism of the NOVA hypervisor or the
+  Muen separation kernel. Those mechanisms look very similar the KVM
+  interface of the Linux kernel. It should in principle be possible to
+  re-target Genode's version of VirtualBox to KVM. This way, VirtualBox and
+  Qemu/KVM-based virtual machines could co-exist on the same system, which
+  is normally not possible. Also, complex Genode scenarios (like Turmvilla)
+  could be prototyped on GNU/Linux.
+
+:VirtualBox on top of seL4:
+
+  The [https://sel4.systems - seL4 microkernel] is a modern microkernel that
+  undergoes formal verification to prove the absence of bugs. Since version
+  4.0, the kernel supports virtualization support on x86-based hardware.
+  Genode has experimental support for seL4 that allows almost all Genode
+  components to be used on top of this kernel. VirtualBox is an exception
+  because it closely interacts with the underlying kernel (like NOVA) to
+  attain good performance. We have shown that VirtualBox can be executed
+  within a protection domain of the NOVA microhypervisor. The goal of this
+  project is the application of this approach to the virtualization
+  interface of seL4. The result will be a VM hosting environment that
+  ensures the separation of virtual machines via the formally verified
+  seL4 kernel.
+
+:Xen as kernel for Genode:
+
+  Using Xen as kernel for Genode would clear the way to remove the
+  overly complex Linux OS from the trusted computing base of Xen
+  guests OSes.
+
+  Xen is a hypervisor that can host multiple virtual machines on one physical
+  machine. For driving physical devices and for virtual-machine management, Xen
+  relies on a privileged guest OS called Dom0. Currently, Linux is the
+  predominant choice to be used as Dom0, which implicates a trusted computing
+  base of millions of lines of code for the other guest OSes.
+
+  Even though Xen was designed as hypervisor, a thorough analysis done by Julian
+  Stecklina concludes that Xen qualifies well as a kernel for Genode. For
+  example, Julian implemented a version of Genode's IPC framework that utilizes
+  Xen's communication mechanisms (event channels and shared memory).
+
+:Genode as virtualization layer for Qubes OS:
+
+  [https://www.qubes-os.org/ - Qubes OS] is a desktop operating system
+  that follows the principle of security through compartmentalization.
+  In spirit, it is closely related to Genode. In contrast Genode's
+  clean-slate approach of building a fine-grained multi-component system,
+  Qubes employs Xen-based virtual machines as sandboxing mechanism. In
+  [https://blog.invisiblethings.org/2015/10/01/qubes-30.html - version 3.0],
+  Qubes introduced a Hypervisor Abstraction Layer, which decouples Qubes
+  from the underlying virtualization platform. This exploration project
+  pursues the goal of replacing Xen by Genode as virtualization layer
+  for Qubes.
+
+:Qemu:
+
+  As we use Qemu as primary testing platform for most of the kernels, a port
+  of Qemu to Genode is needed in order to move our regular work flows to
+  Genode as development platform. The basic prerequisites namely libSDL and a
+  C runtime are already available such that this porting work seems to be
+  feasible. In our context, the ia32, amd64, and ARM platforms are of most
+  interest. Note that the project does not have the immediate goal of
+  using hardware-based virtualization. However, if there is interest,
+  the project bears the opportunity to explore the provisioning of the
+  KVM interface based on Genode's VFS plugin concept.
+
+
+Device drivers
+##############
+
+:Isochronous USB devices:
+
+  Genode's USB driver supports bulk and interrupt endpoints. Thereby, most
+  USB devices like USB storage, user input, printers, and networking devices
+  can be used. However, multi-media devices such as cameras or audio
+  equipment use isochronous endpoints, which are not supported. The goal
+  of this line of work is the support of these devices in Genode. The topic
+  touches the USB driver, the USB session interface, an example implementation
+  of a USB client driver (using the session interface) for a device of choice,
+  and - potentially - the enhancement of Genode's USB-pass-through mechanism
+  for VirtualBox.
+
+:Sound on the Raspberry Pi:
+
+  The goal of this project is a component that uses the Raspberry Pi's
+  PWM device to implement Genode's audio-out-session interface. Since
+  Genode's version of libSDL already supports this interface as audio
+  backend, the new driver will make the sound of all SDL-based games
+  available on the Raspberry Pi.
+
+:Framebuffer for UEFI and Coreboot:
+
+  By moving away from the legacy BIOS boot mechanism, it is time to
+  reconsider closely related traditional approaches such as the use of
+  the VESA BIOS extensions for accessing the frame buffer. On UEFI or
+  Coreboot systems, there exist alternative ways to initialize and
+  access the framebuffer in a hardware-independent way. On the course of
+  this project, we will explore the available options and create dedicated
+  Genode driver components that use the modern mechanisms.
+  For reference, the current state of Genode's UEFI support is documented
+  in [https://github.com/genodelabs/genode/issues/2242 - Issue 2242].
+
+:Data Plane Development Kit (DPDK):
+
+  Genode utilizes the network device drivers of the iPXE project, which
+  perform reasonably well for everyday use cases but are obviously not
+  designated for high-performance networking.
+  The [http://dpdk.org/ - DPDK] is a vendor-supported suite of network device
+  drivers that is specifically developed for high-performance applications.
+  It presents an attractive alternative to iPXE-based drivers. This project
+  has the goal to make DPDK drivers available as a Genode component.
+
 
 Platforms
 #########
 
-:Evaluation of MP scheduling models on different Genode base platforms:
-
-  Several of Genode's supported base platforms come with multi-processor
-  support, i.e., Linux, NOVA, L4ka::Pistachio, and Fiasco.OC. Each of
-  these kernels follows a different approach for utilizing multiple CPUs. For
-  example, Linux manages the association of threads with CPUs largely
-  transparent for user-level programs - not so for the available microkernels.
-  Furthermore, microkernels differ with reagrd to
-  thread migration and scheduling. The goal of this project is to identify ways
-  to support the SMP features of the respective kernels at Genode's API level
-  such that SMP can be easily utilized by Genode programs in a largely kernel
-  agnostic way.
-
 :Microkernelizing Linux:
 
   Thanks to Genode's generic interfaces for I/O access as provided by core, all
@@ -363,17 +374,6 @@ Platforms
   Finally, this project has the potential to ignite a further collaboration
   between the HelenOS and Genode communities.
 
-:Support for the Barrelfish kernel:
-
-  [http://barrelfish.org - `Barrelfish] is a so-called multi-kernel OS designed
-  for heterogeneous multi-processor systems. At its heart, it is a
-  microkernel-based multi-server OS. Its kernel provides different mechanisms
-  than L4-based kernels. Instead of managing threads in the kernel, there is a
-  mechanism for implementing preemptive multi-threading at user level.
-  Consequently, inter-process communication does not address threads but
-  protection domains. This makes the Barrelfish kernel a very interesting and
-  challenging target for running Genode.
-
 :Support for the XNU kernel (Darwin):
 
   XNU is the kernel used by Darwin and Mac OS X. It is derived from the
@@ -381,22 +381,6 @@ Platforms
   kernel is used for Mac OS X, it could represent an industry-strength
   base platform for Genode supporting all CPU features as used by Mac OS X.
 
-:Xen as kernel for Genode:
-  Using Xen as kernel for Genode would clear the way to remove the
-  overly complex Linux OS from the trusted computing base of Xen
-  guests OSes.
-
-  Xen is a hypervisor that can host multiple virtual machines on one physical
-  machine. For driving physical devices and for virtual-machine management, Xen
-  relies on a privileged guest OS called Dom0. Currently, Linux is the
-  predominant choice to be used as Dom0, which implicates a trusted computing
-  base of millions of lines of code for the other guest OSes.
-
-  Even though Xen was designed as hypervisor, a thorough analysis done by Julian
-  Stecklina concludes that Xen qualifies well as a kernel for Genode. For
-  example, Julian implemented a version of Genode's IPC framework that utilizes
-  Xen's communication mechanisms (event channels and shared memory).
-
 :Linux process containers for supporting Genode`s resource trading:
 
   Even though the Linux version of Genode is primarily meant as a development

doc/components.txt

@@ -584,13 +584,6 @@ Runtime environments
   that enables the use of unmodified command-line based GNU software. For using
   noux, refer to the run script 'ports/run/noux.run'.
 
-:'ports-foc/src/l4linux': L4Linux is a paravirtualized Linux kernel that
-  enables the use of Linux-based OSes as subsystems on the Fiasco.OC kernel.
-  For using L4Linux, refer to the run script 'ports-foc/run/l4linux.run'.
-
-:'ports-foc/src/l4android': L4Android is a variant of L4Linux that is able
-  to execute the Android software stack on top of the Fiasco.OC kernel.
-
 :'ports/src/app/seoul': Seoul is a virtual-machine monitor developed for
   the use with the NOVA platform. It virtualizes 32bit x86 PC hardware
   including various peripherals.

doc/news.txt

@@ -4,6 +4,136 @@
                                ===========
 
 
+Genode OS Framework release 17.02 | 2017-02-28
+##############################################
+
+| By introducing application binary interfaces, version 17.02 cultivates
+| the cross-kernel binary compatibility of components. Furthermore, the
+| new version comes with a vastly improved VFS infrastructure, new input-event
+| processing capabilities, and a dynamic component-composition engine.
+
+On the long road towards binary compatibility of Genode components across OS
+kernels as different as L4, NOVA, seL4, or Linux, we reached a breakthrough by
+mid of 2016. It took us another six months to fully cultivate this unique
+feature and to integrate it seamlessly into our development work flows. With
+the current version, we have ultimately reached the point where one can move
+entire system scenarios from one kernel to another in just a few seconds.
+
+With the improved virtual file-system (VFS) infrastructure that comes with the
+new version, such system scenarios can become more and more sophisticated.
+Genode takes the meaning of _virtual_ file systems to an entirely new level.
+Not only does Genode virtualize the physical location of files but each
+component can have its own VFS whereby the supported file-system types are
+provided by VFS plugins. Those plugins can go as far as providing a TCP/IP
+stack as showcased by Genode's use of the Linux TCP/IP stack as VFS plugin.
+
+The composition of subsystems out of Genode components is another highlight of
+the current release. In each Genode-based system, the init component already
+plays a central role as it bootstraps the initial system components. Thanks to
+Genode's recursive system structure, init can easily be nested. With the
+improvements of the new version, such a nested init becomes a dynamic
+system-composition engine that responds to configuration updates and applies
+changes to its subsystem in a differential way.
+
+These and many more improvements are covered in full detail in the
+[https:/documentation/release-notes/17.02 - release documentation of version 17.02...]
+
+
+Open-source license update | 2017-02-21
+#######################################
+
+| With the upcoming version 17.02, Genode will adopt the GNU Affero General
+| Public License (AGPLv3) as its regular open-source license.
+
+Since our first release in 2008, Genode has been available under two flavors
+of licenses addressing different user bases. With Genode's regular open-source
+license, we address the Free-Software community, researchers, and technology
+enthusiasts. With the commercial license, Genode Labs enables product vendors
+to leverage Genode's technology for their businesses.
+
+For our open-source license, we originally picked the time-tested GNU General
+Public License version 2 (GPLv2). However, the time did not stand still. After
+9 years, it is time to update the license to a more recent version. After
+careful review of the open-source licensing landscape, we settled on the GNU
+Affero General Public License (AGPLv3), which is based on the GNU GPLv3 and
+thereby rectifies several shortcomings of the GPLv2. Furthermore, it closes
+loopholes of the GPLv3 license with respect to web applications. Unlike 2008
+when most applications were programs executed directly on the end user's
+computer, web applications have become predominant by now.
+
+To address possible concerns about the interoperability of the AGPLv3 with
+other open-source licenses, Genode's license will be accompanied with a
+linking-exception clause that clarifies our consent to link Genode with all
+commonly established open-source licenses.
+
+In December, we presented our plan of the license change to the subscribers of
+Genode's mailing list. The following constructive
+[https://sourceforge.net/p/genode/mailman/genode-main/thread/585116C8.2020607%40genode-labs.com/#msg35550569 - discussion]
+within the community helped us to refine our linking clause and to create a
+common understanding of the rationale behind our licensing choice. Thanks to
+everyone who participated in this discussion!
+
+
+Road Map for 2017 | 2017-01-17
+##############################
+
+| The year 2017 will be overall focused on stressing the scalability and
+| stability of the framework.
+
+After wrapping up the revision of Genode's architectural underpinnings and its
+API in 2016, it is time to push the scalability of the framework further.
+Over the course of 2017, we plan to greatly ease the creation of Genode
+systems out of packages, enable automated system updates, move our regular
+work flows from GNU/Linux to the Genode world, and extend the application
+scope of Genode systems to cloud-based appliances.
+
+The new road map is available at the [https:/about/road-map - road-map page].
+
+
+Genode at FOSDEM 2017 | 2017-01-11
+##################################
+
+| The microkernel developer room at this year's FOSDEM will host four
+| Genode-related talks, ranging from our custom kernel, over
+| kernel-independent binaries, execution replay, to Genode's VFS
+| infrastructure.
+
+To us, the microkernel developer room at FOSDEM in Brussels has become
+the most anticipated joint event of the open-source microkernel world.
+The developer room is part of FOSDEM, which is the world's largest
+event of the Free-Software and Open-Source community. The upcoming
+FOSDEM will be held on 4th - 5th of February in Brussels:
+
+FOSDEM 2017: [https://fosdem.org/2017/]
+
+Originally initiated by our friends of the HelenOS project, the micro-kernel
+developer room is shepherded by a different project each year. In 2017, it's
+our turn to host the event. The developer room is open for all open-source
+projects that are related to microkernels or component-based operating
+systems. It features a mix of project introductions, experience stories,
+progress reports, discussions, and demos. This year, the following
+Genode-related topics will be presented:
+
+Saturday 10:45 *A kernel in a library Genode's custom kernel approach*
+_Microkernel devroom (AW1.125)_
+[https://fosdem.org/2017/schedule/event/microkernel_kernel_library/ - abstract...]
+
+Saturday 12:45 *Deterministic replay support for Genode components*
+_Microkernel devroom (AW1.125)_
+[https://fosdem.org/2017/schedule/event/microkernel_replay_support/ - abstract...]
+
+Saturday 14:24 *Introducing kernel-agnostic Genode executables*
+_Microkernel devroom (AW1.125)_
+[https://fosdem.org/2017/schedule/event/microkernel_kernel_agnostic_genode_executables/ - abstract...]
+
+Saturday 17:10 *The VFS paradigm from the perspective of a component OS*
+_Microkernel devroom (AW1.125)_
+[https://fosdem.org/2017/schedule/event/microkernel_vfs_component_os/ - abstract...]
+
+The complete schedule of the developer room is available at
+[https://fosdem.org/2017/schedule/track/microkernels_and_component_based_os/].
+
+
 Genode OS Framework release 16.11 | 2016-11-30
 ##############################################
 

doc/release_notes-16-11.txt

@@ -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
 overcome them. However, reworking the fundamental protocols of a system that
 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
 deliberately decided to address long-standing deficiencies rather than adding
 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
 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
-With respect to the road map, we postponed most topics originally planned for
-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
+the footsteps of the existing Muen support - using our custom
 base-hw kernel within a Xen DomU domain. However, before proceeding this
 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
@@ -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
 design problem. Second and more importantly, redesigning the fundamental
 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.
 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
@@ -445,7 +443,7 @@ router configuration:
 As you can see, each of the new IP rules in the Virtnet domains match the
 addresses of the opposite subnet and route to the corresponding domain. As
 mentioned, the new IP rules and UDP/TCP rules are not combined anymore to
-clearly distinguish IP routing from layer-3 routing. This decision has
+clearly distinguish IP routing from layer-3 routing because this decision has
 far-reaching effects. First, in contrast to UDP and TCP routing, IP routing is
 stateless. Thus, for each IP routing rule one has to be sure to have a
 back-routing rule at the remote domain or else bidirectional communication

doc/road_map.txt

@@ -14,99 +14,132 @@ The road map is not fixed. If there is commercial interest of pushing the
 Genode technology to a certain direction, we are willing to revisit our plans.
 
 
-Review of 2015
+Review of 2016
 ##############
 
-In the beginning of 2015, we declared four main topics to work on, namely
-Genode as general-purpose OS, our custom base-hw kernel platform, thorough
-documentation, and the seL4 kernel. It goes without saying that the stability
-and performance of the base system is a fundamental requirement for the first
-topic.
+We originally started the year 2016 with the ambition to expand the Genode
+community by improving the project's appeal towards system builders and
+privacy cautious users. Hence, we started the year with the resolution to
+increase our engagement with the wider community, i.e., in the form of
+publishing tutorial-like articles. Over the course of the year, however, we
+increasingly shifted our focus to architectural and deeply technical topics
+instead.
 
-In mid of 2015, we eventually reached the point where a hand full of
-developers started using Genode as their day-to-day OS in the form of the
-so-called
-[https://github.com/genodelabs/genode/issues/1552 - Turmvilla scenario].
-By the end of the year, the performance, stability, and device-driver support
-had reached a level that leaves people impressed every time we have the chance
-to show off our system. Once people become interested, the Genode Foundations
-book - published in Spring - provides a smooth introduction into Genode. The
-Turmvilla scenario is currently based on the NOVA kernel. For the future, we
-want to use also other kernels, in particular our custom base-hw kernel and
-seL4. Thanks to the contribution of
-[http://codelabs.ch - Codelabs], base-hw became usable on the 64-bit x86
-architecture and on the Muen separation kernel in particular. With our work
-on seL4, we reached the point where basic Genode scenarios are executable
-on this kernel.
+We ultimately prioritized the concerns of the existing Genode users over
+extending our user base. The existing users - ourself included - are primarily
+interested in API stability and maturity. So we made it our priority to free
+Genode from legacies and known architectural limitations. Over the year, we
+introduced and cultivated the new framework API that is designed for safety,
+achieved cross-kernel binary compatibility, and revised the framework's most
+fundamental protocols. Now that the time of sweeping architectural changes
+lies behind us, we feel much more confident to approach new users.
 
-After having passed the point where a few enthusiasts are able to use Genode
-as day-to-day OS, we should put the emphasis of 2016 on
-ways to make Genode accessible for a wider community.
+Apart from the architectural foundations, among the many other construction
+sites of 2016 were the support for the RISC-V architecture, hosting Genode on
+top of the Muen separation kernel and the seL4 microkernel, huge device driver
+improvements (wifi, graphics, USB, ACPI), VirtualBox 5, virtual networking,
+TOR, Rust and many others. Even though we largely deviated from our original
+ambition, we are proud of the outcome of the past year.
 
 
-Big picture for 2016
+Big picture for 2017
 ####################
 
-We identified two possible ways to extend the Genode community.
+Our principle direction as declared at he beginning of 2016 remains unchanged
+for 2017: Making Genode accessible to the world outside the inner circle
+of us enthusiasts. But rather than making this direction the top priority for
+now, let us first push the bounds of what the current users and
+developers can do with Genode. Hence, for the overall theme of 2017, we
+picked: *stability and scalability*. Once Genode reaches the point where it is
+routinely used and stressed for various purposes by the "inner circle", a
+growing user base will follow naturally and organically.
 
-By community we refer to two groups of people. The first group are
-maker-minded people with a strong incentive to build things. By publishing a
-series of step-by-step guides that explain how to put Genode components
-together in order to create custom system scenarios, we intend to spark
-interest of system builders in Genode. Those articles could be accompanied by
-screencasts or live-system images.
+During our seasonal road-map discussion on our mailing list, we identified the
+following topics to address in 2017:
 
-The second group are certain end users with a strong desire for privacy and
-security. We expect this narrow user group to willingly trade the comfort and
-features of traditional desktop OSes for the benefits of Genode. We plan to
-showcase a system with practical value for this group, for example a
-disposable OS like Tails that allows the user to browse the internet via the
-Tor network.
+:Application binary interfaces and package management:
 
-In this spirit, the leitmotif for 2016 will be: Let us make Genode accessible
-to the world outside the inner circle of us enthusiasts.
+  By mid 2016, we attained binary compatibility across the various OS
+  kernels supported by Genode, which cleared the way to introduce the notion
+  of a Genode application binary interface (ABI). This, in turn, is a
+  prerequisite for a scalable handling of binary packages. In 2017, we
+  will leverage these foundations in two ways: Allowing the easy creation
+  of Genode systems out of packages, and realizing a system-update mechanism
+  that allows us to automatically use (and thereby test) the latest versions
+  of Genode components on our machines.
 
-On a technical level, this motive implicates the following topics:
+:Dynamically reconfigurable subsystems:
 
-* The deployment, management, and configuration of Genode systems, i.e., by
-  bringing forward our work on the Nix package manager and by fostering
-  dynamic configurability. This direction also reinforces the need to achieve
-  binary compatibility between the various base platforms to make the
-  distribution of binary packages, reproducible builds, and continuous test
-  and integration scalable.
+  Until now, Genode subsystems were either static (using the init component to
+  define them) or relied on a scenario-specific dynamic runtime environment
+  (like CLI monitor). By enhancing init to dynamically apply configuration
+  changes, the need for special-purpose runtime environments will
+  disappear. Scenarios like multi-stage booting, boot-medium detection, or
+  a dynamic desktop environment will become dramatically easier to realize.
 
-* Accommodation of common desktop use cases like plugging in a USB
-  stick to work with the files stored on it. Also disk encryption comes
-  into mind.
+:Pruning the boot chain:
 
-* Optimization of Genode for the use on a laptop, e.g., addressing
-  fan control, power management, suspend/resume, and similar features.
+  Today, Genode on x86 machines still relies on the legacy BIOS boot
+  mechanism. We will explore alternatives such as UEFI boot and
+  coreboot.
 
-* Identifying ways of how Genode could contribute additional value to
-  Xen-based environments like Amazon EC2 and Qubes OS.
+:Asynchronous I/O:
 
-* Foster the cross-pollination of the seL4 and Genode communities.
-  Genode would allow the seL4 community to move beyond static system
-  scenarios.
+  With Genode 16.11, we successfully removed the last blocking inter-component
+  interfaces from the base framework. Still, other parts of the user-level
+  infrastructure, in particular the libc still relies on blocking operations. Even
+  though we have to offer blocking I/O to user applications for POSIX
+  compatibility, the mechanisms used behind the scenes will be changed to leverage
+  Genode's asynchronous I/O primitives.
 
-* As most use cases rely on networking, we acknowledge the need for
-  improving Genode's network support such as NAT, the robustness of the
-  available TCP/IP stacks and drivers, encryption, and possibly IPv6.
+:VirtualBox 5:
 
-* Genode as distributed system, e.g., a system spread over multiple FPGA-based
-  softcore CPUs, over multiple domains of the Muen separation kernel, or a
-  local machine and a cloud-service provider.
+  Currently, we maintain a fully-featured version of VirtualBox 4 (including
+  USB pass-through, audio, shared folders, clipboard, dynamic desktop resizing)
+  and a pretty basic version of VirtualBox 5 (without those integration
+  features). In 2017, we will replace VirtualBox 4 by a fully featured
+  version of VirtualBox 5.
 
-Assuming that we succeed in drawing the attention of a broader audience
-to our project, we should make sure that Genode's API won't undergo
-major changes soon after this point. Today, there are still a number of
-deficiencies in the current API. We should finalize the renovation of
-the Genode API until the mid of 2016. This will also be right the time for
-updating the Genode book. Also, the planned step-by-step guides will
-be based on the modernized API.
+:Updated tool chain and Qt5:
+
+  With version 17.05, we want to experiment with the idea of providing a
+  long-term supportable version of the framework in addition to the quarterly
+  releases. Consequently, at the time of its release, this version should use
+  a modern tool chain that will remain current for the foreseeable future of
+  Genode's regular development. The same holds true for Qt5.
+
+:Hardware-accelerated graphics on Intel:
+
+  Graphics is an important element for many use cases for Genode on x86-based
+  platforms. Even though we experimented with hardware-accelerated 3D
+  graphics
+  [http://genode.org/documentation/release-notes/10.08#Gallium3D_and_Intel_s_Graphics_Execution_Manager - many years ago],
+  the current GUI stack is still based on software-based rendering.
+  We want to overcome this limitation this year.
+
+:Native work flows:
+
+  In the regularly used "Turmvilla" scenarios, most work flows require the
+  use of Linux in a virtual machine. Over the course of the year, we want
+  to move the most important work flows (namely software development and
+  the work with emails) to Genode natively. As a precondition,
+  we need to improve the usability of our GUI infrastructure by adding
+  support for tiled and tabbed windows, and virtual desktops.
+
+:Storage:
+
+  There are several storage-related topics that need our attention to
+  realize the goals stated above to our satisfaction. This includes the
+  performance and stability of the used file-system stack, and the provision
+  of file-based backup and cryptographic functionality.
+
+:Genode-based cloud appliances:
+
+  We want to widen the application scope of Genode by enabling users to
+  easily deploy Genode scenarios on Xen-based cloud platforms.
 
 
-Milestones for 2016
+Milestones for 2017
 ###################
 
 In the following, we present a rough schedule of the planned work. As usual,
@@ -114,41 +147,39 @@ it is not set in stone. If you are interested in a particular line of work,
 please get in touch.
 
 
-February - Release 16.02
+February - Release 17.02
 ========================
 
-* RISC-V architecture support
-* seL4 version 2.0
-* Assignment of USB devices to VirtualBox guests
-* API modernization (introduction of new component API, deprecation
-  of API legacies)
+* Application binary interfaces (ABI)
+* Dynamic init
+* VFS: asynchronous I/O
 
 
-May - Release 16.05
+May - Release 17.05
 ===================
 
-* VirtualBox on top of the Muen separation kernel
+* Removal of deprecated APIs
+* Updated tool chain
+* Updated Qt5
+* Easy creation of Genode systems out of packages
+* Feature-complete VirtualBox 5
 * Update of the Genode Foundations book
-* NAT component
-* API modernization (removal of API legacies)
-* Definition of "packages"
 
 
-August - Release 16.08
+August - Release 17.08
 ======================
 
-* Cross-kernel binary compatibility
-* Interactive system scenarios on top of seL4
-* Networking via Tor
-* Block encryption
-* Build-system support for handling packages
+* Hardware-accelerated graphics on Intel-based platforms
+* Support for the seL4 kernel on x86_64 and ARM
+* Use of Genode for cloud-computing appliances (deployment, virtio)
+* GUI: tiled and tabbed window management, virtual desktops
 
 
-November - Release 16.11
+November - Release 17.11
 ========================
 
-* Genode on top of Xen
-* Exploration of Genode as distributed system
-* Deployment of packages
-* On-target building of packages
+* Revised boot concept (UEFI, trimming the boot chain)
+* Storage: backup, improved file-system support
+* Native work flows for email and development work
+* Test automation for interactive system scenarios
 

repos/README

@@ -120,14 +120,6 @@ but build upon of each other:
   as used for the 'libports' repository. Please consult 'libports/README'
   for further information.
 
-:'ports-<platform>':
-
-  These platform-specific source-code repositories contain software that
-  capitalizes special features of the respective kernel platform.
-  For the Fiasco.OC platform, 'ports-foc' hosts a port of the L4Linux
-  kernel. For further information, please refer to the README file at the
-  top level of the respective repository.
-
 :'gems':
 
   This source-code repository contains Genode applications that use

repos/base-fiasco/doc/fiasco.txt

@@ -59,12 +59,12 @@ with 'fiasco_x86' as argument:
 
 From within the new <build-dir>, the kernel can be compiled via
 
-! make kernel
+! make kernel/fiasco
 
-When using Genode's run mechanism, there is no need to explicitly
-build the kernel. The run environment (see 'base-fiasco/run/env')
-takes care of it. So you can simple execute run scripts from within
-the build directory, for example:
+When using Genode's run mechanism, there is no need to explicitly build the
+kernel. The run environment (see 'tool/run/boot_dir/fiasco') takes care of it.
+So you can simple execute run scripts from within the build directory, for
+example:
 
 ! make run/demo
 
@@ -115,22 +115,5 @@ interest for using Genode:
   is used to create a single binary image containing all boot-time
   OS components.
 
-To build all components under '3rd/fiasco' after extracting the
-archive, issue the following commands:
-
-! mkdir <build-dir>
-! make -C 3rd/fiasco BUILD_DIR=<build-dir>/3rd build
-
-The specified '<build-dir>' must be the absolute path to the
-directory, which will contain the build directories for the third party
-software and the Genode build directory. After the build, your compound
-build directory contains the following subdirectories:
-
-:'fiasco_x86':
-
-  All generated files and the final binary of Fiasco reside here.
-
-:'l4env':
-
-  L4 environment binaries and header files.
-
+Those components are implicitly built by the Genode build system when
+issuing 'make kernel/fiasco'.

repos/base-fiasco/etc/fiasco.conf

@@ -1,11 +0,0 @@
-#
-# Fiasco-specific default configuration options
-#
-
-#
-# Directory, where to search for L4 headers
-#
-# When using this file as template for a customized
-# '<builddir>/etc/fiasco.conf'.
-#
-#L4_DIR = $(HOME)/src/l4build.x86

repos/base-fiasco/etc/specs.conf

@@ -1,15 +1 @@
-#
-# Description of build platform
-#
-
-#
-# To build the Fiasco-specific Genode binaries,
-# use one of the the following config options.
-#
-SPECS = genode fiasco_x86
-
-#
-# To build for the ARM integrator platform,
-# use the following SPECS value.
-#
-#SPECS = genode platform_integrator fiasco_arm
+SPECS += fiasco x86_32

repos/base-fiasco/lib/import/import-syscall-fiasco.mk

@@ -0,0 +1,6 @@
+L4_SRC_DIR := $(call select_from_ports,fiasco)/src/kernel/fiasco/fiasco/snapshot
+
+INC_DIR += $(LIB_CACHE_DIR)/syscall-fiasco/include/x86/l4v2 \
+           $(LIB_CACHE_DIR)/syscall-fiasco/include/x86 \
+           $(LIB_CACHE_DIR)/syscall-fiasco/include \
+           $(LIB_CACHE_DIR)/syscall-fiasco/include/l4v2

repos/base-fiasco/lib/mk/base-fiasco-common.mk

@@ -6,7 +6,7 @@
 
 include $(BASE_DIR)/lib/mk/base-common.inc
 
-LIBS += startup
+LIBS += startup-fiasco syscall-fiasco
 
 SRC_CC += capability.cc capability_raw.cc
 SRC_CC += signal_submit.cc

repos/base-fiasco/lib/mk/base-fiasco.mk

@@ -1,5 +1,7 @@
 include $(BASE_DIR)/lib/mk/base.inc
 
+LIBS += syscall-fiasco
+
 SRC_CC += thread_start.cc
 SRC_CC += cache.cc
 SRC_CC += capability_space.cc

repos/base-fiasco/lib/mk/core-fiasco.inc

@@ -42,7 +42,7 @@ INC_DIR     += $(REP_DIR)/src/core/include \
                $(REP_DIR)/src/include \
                $(BASE_DIR)/src/include
 
-LIBS        += base-common
+LIBS        += base-fiasco-common syscall-fiasco cxx
 
 include $(GEN_CORE_DIR)/version.inc
 

repos/base-fiasco/lib/mk/kernel-fiasco.inc

@@ -0,0 +1,53 @@
+L4_SRC_DIR = $(call select_from_ports,fiasco)/src/kernel/fiasco/fiasco/snapshot
+
+FIASCO_BUILD_DIR = $(shell pwd)/build
+FIASCO           = $(FIASCO_BUILD_DIR)/fiasco
+FIASCO_SRC       = $(L4_SRC_DIR)/kernel/fiasco
+
+KERNEL_BUILD_OUTPUT_FILTER = 2>&1 | sed "s/^/      [fiasco]  /"
+
+$(FIASCO_BUILD_DIR):
+	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
+	                                 $(VERBOSE_DIR) -C $(FIASCO_SRC) BUILDDIR=$@ \
+	                                 $(KERNEL_BUILD_OUTPUT_FILTER)
+	$(VERBOSE)cp $(KERNEL_CONFIG) $@/globalconfig.out
+	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
+	                                 $(VERBOSE_DIR) -C $@ oldconfig \
+	                                 $(KERNEL_BUILD_OUTPUT_FILTER)
+	$(VERBOSE)cp $(KERNEL_CONFIG) $@/globalconfig.out
+
+$(FIASCO): $(FIASCO_BUILD_DIR)
+	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
+	                                 $(VERBOSE_DIR) -C $(FIASCO_BUILD_DIR) \
+	                                 $(KERNEL_BUILD_OUTPUT_FILTER)
+
+#
+# Sigma0 and bootstrap are provided as L4 packages
+#
+# We build them within the L4 build directory created by the 'syscall-fiasco'
+# library.
+#
+
+LIBS += syscall-fiasco
+
+PKGS = l4sys/lib \
+       uclibc/lib/uclibc \
+       uclibc/lib/include \
+       crtx \
+       l4util/lib \
+       cxx \
+       sigma0/server \
+       bootstrap
+
+L4_BUILD_DIR := $(LIB_CACHE_DIR)/syscall-fiasco
+
+include $(REP_DIR)/lib/mk/l4_pkg.inc
+
+#
+# Execute the rules in this file only at the second build stage when we know
+# about the complete build settings, e.g., 'CROSS_DEV_PREFIX'.
+#
+ifeq ($(called_from_lib_mk),yes)
+all: $(FIASCO)
+endif
+

repos/base-fiasco/lib/mk/l4_pkg.inc

@@ -8,8 +8,6 @@
 #          the target
 #
 
-LIBS += platform
-
 ifeq ($(filter-out $(SPECS),x86_32),)
 	L4_BUILD_ARCH := x86
 endif
@@ -19,19 +17,29 @@ ifeq ($(filter-out $(SPECS),arm),)
 endif
 
 ifeq ($(L4_BUILD_ARCH),)
-all: l4_build_arch_undefined
-	$(VERBOSE)$(ECHO) "Error: L4_BUILD_ARCH undefined, architecture not supported"
-	$(VERBOSE)false
+$(error L4_BUILD_ARCH undefined, architecture not supported)
 endif
 
-L4_PKG_DIR   = $(L4_SRC_DIR)/l4/pkg
-PKG_TAGS     = $(addsuffix .tag,$(PKGS))
+ifndef L4_BUILD_DIR
+$(error L4_BUILD_DIR undefined)
+endif
+
+L4_PKG_DIR = $(L4_SRC_DIR)/l4/pkg
+PKG_TAGS   = $(addsuffix .tag,$(PKGS))
+
+BUILD_OUTPUT_FILTER = 2>&1 | sed "s~^~      [$*]  ~"
 
 ifeq ($(VERBOSE),)
 L4_VERBOSE = V=1
 endif
 
-$(TARGET): $(PKG_TAGS)
+#
+# Execute the rules in this file only at the second build stage when we know
+# about the complete build settings, e.g., 'CROSS_DEV_PREFIX'.
+#
+ifeq ($(called_from_lib_mk),yes)
+all: $(PKG_TAGS)
+endif
 
 #
 # We preserve the order of processing 'l4/pkg/' directories because of
@@ -52,17 +60,7 @@ $(TARGET): $(PKG_TAGS)
 	                      -C $(L4_PKG_DIR)/$* \
 	                      CC="$(CROSS_DEV_PREFIX)gcc" \
 	                      CXX="$(CROSS_DEV_PREFIX)g++" \
-	                      LD="$(CROSS_DEV_PREFIX)ld"
+	                      LD="$(CROSS_DEV_PREFIX)ld" \
+	                      $(BUILD_OUTPUT_FILTER)
 	$(VERBOSE)mkdir -p $(dir $@) && touch $@
 
-clean cleanall: clean_tags
-
-# if (pseudo) target is named after a directory, remove the whole subtree
-clean_prg_objects: clean_dir_named_as_target
-
-clean_dir_named_as_target:
-	$(VERBOSE)(test -d $(TARGET) && rm -rf $(TARGET)) || true
-
-clean_tags:
-	$(VERBOSE)rm -f $(PKG_TAGS)
-

repos/base-fiasco/lib/mk/l4v2_support.mk

@@ -1,19 +0,0 @@
-#
-# Build L4env base libraries, needed by sigma0 and bootstrap
-
-
-# ignore stage one, visit the L4 build system at second build stage
-ifeq ($(called_from_lib_mk),yes)
-
-# packages in 'l4/pkg/'
-PKGS = l4sys/lib \
-       uclibc/lib/uclibc \
-       uclibc/lib/include \
-       crtx \
-       l4util/lib \
-       cxx
-
-include $(REP_DIR)/mk/l4_pkg.mk
-all: $(PKG_TAGS)
-
-endif

repos/base-fiasco/lib/mk/platform.inc

@@ -1,56 +0,0 @@
-#
-# Create prerequisites for building Genode for Fiasco
-#
-# Prior building Genode programs for Fiasco, the kernel bindings must be
-# generated. This is done by building a minimalistic subset of the original
-# userland that comes with Fiasco.
-#
-
-#
-# Execute the rules in this file only at the second build stage when we know
-# about the complete build settings, e.g., the 'CROSS_DEV_PREFIX'.
-#
-ifeq ($(called_from_lib_mk),yes)
-
-#
-# Sanity checks
-#
-ifeq ($(L4_BUILD_DIR),$(BUILD_BASE_DIR)/l4)
-all: $(L4_SRC_DIR)
-
-$(L4_SRC_DIR):
-	$(VERBOSE)$(ECHO) "--> Please, execute './tool/ports/prepare_port fiasco' in $(GENODE_DIR)"
-	$(VERBOSE)$(ECHO) "--> before compiling Genode apps for Fiasco."
-	$(VERBOSE)exit 1
-endif
-
-#
-# Create L4 build directory
-#
-$(BUILD_BASE_DIR)/l4/.Makeconf.bid.old:
-	$(VERBOSE)mkdir -p $(dir $@)
-	$(VERBOSE)cp $(L4_CONFIG) $(@:.old=)
-	$(VERBOSE_MK) MAKEFLAGS= make $(VERBOSE_DIR) -C $(L4_SRC_DIR)/l4 \
-         O=$(BUILD_BASE_DIR)/l4 SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" oldconfig
-
-$(BUILD_BASE_DIR)/l4/pkg/uclibc/lib/uclibc:
-	$(VERBOSE)mkdir -p $(BUILD_BASE_DIR)/l4/pkg/uclibc/lib/uclibc
-	$(VERBOSE)tar cf - --exclude .svn -C $(L4_SRC_DIR)/../uclibc ARCH-all ARCH-x86 \
-              | tar xf - -C $(BUILD_BASE_DIR)/l4/pkg/uclibc/lib/uclibc
-
-PKGS = input/include \
-       drivers/uart/include \
-       l4sys/include \
-       l4util/include \
-       libc_support/include \
-       libsigma0/include
-
-include $(REP_DIR)/mk/l4_pkg.mk
-
-all: $(PKG_TAGS)
-
-$(PKG_TAGS): $(BUILD_BASE_DIR)/l4/.Makeconf.bid.old
-$(PKG_TAGS): $(BUILD_BASE_DIR)/l4/pkg/uclibc/lib/uclibc
-
-endif
-

repos/base-fiasco/lib/mk/spec/x86_32/core-fiasco.mk

@@ -1,7 +1,7 @@
-include $(REP_DIR)/lib/mk/core.inc
+include $(REP_DIR)/lib/mk/core-fiasco.inc
 
-REQUIRES += x86
-SRC_CC   += platform_x86.cc
+LIBS   += base-fiasco-common
+SRC_CC += platform_x86.cc
 
 vpath io_port_session_component.cc $(GEN_CORE_DIR)/spec/x86
 vpath io_port_session_support.cc   $(GEN_CORE_DIR)/spec/x86

repos/base-fiasco/lib/mk/spec/x86_32/kernel-fiasco.mk

@@ -0,0 +1,3 @@
+KERNEL_CONFIG = $(REP_DIR)/config/kernel-config.x86
+
+include $(REP_DIR)/lib/mk/kernel-fiasco.inc

repos/base-fiasco/lib/mk/spec/x86_32/ld-fiasco.mk

@@ -0,0 +1,3 @@
+BASE_LIBS += base-fiasco-common base-fiasco
+
+include $(BASE_DIR)/lib/mk/spec/x86_32/ld-platform.inc

repos/base-fiasco/lib/mk/spec/x86_32/startup-fiasco.mk

@@ -0,0 +1,3 @@
+include $(BASE_DIR)/lib/mk/spec/x86_32/startup.inc
+
+LIBS += syscall-fiasco

repos/base-fiasco/lib/mk/spec/x86_32/syscall-fiasco.mk

@@ -3,4 +3,4 @@
 #
 L4_CONFIG = $(REP_DIR)/config/l4env-config.x86
 
-include $(REP_DIR)/lib/mk/platform.inc
+include $(REP_DIR)/lib/mk/syscall-fiasco.inc

repos/base-fiasco/lib/mk/syscall-fiasco.inc

@@ -0,0 +1,38 @@
+#
+# Create prerequisites for building Genode for Fiasco
+#
+# Prior building Genode programs for Fiasco, the kernel bindings must be
+# generated. This is done by building a minimalistic subset of the original
+# userland that comes with Fiasco.
+#
+
+L4_SRC_DIR    = $(call select_from_ports,fiasco)/src/kernel/fiasco/fiasco/snapshot
+L4_BUILD_DIR := $(shell pwd)
+
+#
+# Create L4 build directory
+#
+.Makeconf.bid.old:
+	$(VERBOSE)mkdir -p $(dir $@)
+	$(VERBOSE)cp $(L4_CONFIG) $(@:.old=)
+	$(VERBOSE_MK) MAKEFLAGS= make $(VERBOSE_DIR) -C $(L4_SRC_DIR)/l4 \
+	   O=$(L4_BUILD_DIR) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" oldconfig \
+	   2>&1 | sed "s/^/      [l4build]  /"
+	$(VERBOSE)touch $@
+
+pkg/uclibc/lib/uclibc:
+	$(VERBOSE)mkdir -p pkg/uclibc/lib/uclibc
+	$(VERBOSE)tar cf - --exclude .svn -C $(L4_SRC_DIR)/../uclibc ARCH-all ARCH-x86 \
+	        | tar xf - -C pkg/uclibc/lib/uclibc
+
+PKGS = input/include \
+       drivers/uart/include \
+       l4sys/include \
+       l4util/include \
+       libc_support/include \
+       libsigma0/include
+
+include $(REP_DIR)/lib/mk/l4_pkg.inc
+
+$(PKG_TAGS): .Makeconf.bid.old
+$(PKG_TAGS): pkg/uclibc/lib/uclibc

repos/base-fiasco/mk/spec/fiasco.mk

@@ -1,25 +0,0 @@
-#
-# Specifics for the l4v2 kernel API
-#
-
-#
-# Read default and builddir-specific config files
-#
-# In these config files, we find the definition of L4_DIR
-#
--include $(call select_from_repositories,etc/fiasco.conf)
--include $(BUILD_BASE_DIR)/etc/fiasco.conf
-
-L4_BUILD_DIR := $(BUILD_BASE_DIR)/l4
-L4_SRC_DIR   := $(call select_from_ports,fiasco)/src/kernel/fiasco/fiasco/snapshot
-
-#
-# L4/sys headers
-#
-L4_INC_DIR   += $(L4_BUILD_DIR)/include \
-                $(L4_BUILD_DIR)/include/l4v2
-
-clean_contrib:
-	$(VERBOSE)rm -rf $(BUILD_BASE_DIR)/l4
-
-cleanall: clean_contrib

repos/base-fiasco/mk/spec/fiasco_x86.mk

@@ -1,20 +0,0 @@
-#
-# Specifics for Fiasco L4v2 on x86
-#
-
-SPECS += x86_32 fiasco
-SPECS += pci ps2 vesa framebuffer
-
-#
-# x86-specific L4v2/sys headers
-#
-L4_INC_DIR   += $(L4_BUILD_DIR)/include/x86/l4v2 \
-                $(L4_BUILD_DIR)/include/x86
-
-#
-# Also include less-specific configuration last
-#
-include $(call select_from_repositories,mk/spec/x86_32.mk)
-include $(call select_from_repositories,mk/spec/fiasco.mk)
-
-INC_DIR      += $(L4_INC_DIR)

repos/base-fiasco/src/bootstrap/target.mk

@@ -1,5 +0,0 @@
-TARGET = bootstrap
-PKGS   = bootstrap
-LIBS   = l4v2_support
-
-include $(REP_DIR)/mk/l4_pkg.mk

repos/base-fiasco/src/core/core_log.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* core includes */

repos/base-fiasco/src/core/fiasco/target.mk

@@ -0,0 +1,3 @@
+LIBS = core-fiasco
+
+include $(BASE_DIR)/src/core/target.inc

repos/base-fiasco/src/core/include/ipc_pager.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__IPC_PAGER_H_

repos/base-fiasco/src/core/include/map_local.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2010-2013 Genode Labs GmbH
+ * Copyright (C) 2010-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__MAP_LOCAL_H_

repos/base-fiasco/src/core/include/platform.h

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2007-2013 Genode Labs GmbH
+ * Copyright (C) 2007-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__PLATFORM_H_

repos/base-fiasco/src/core/include/platform_pd.h

@@ -8,10 +8,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__PLATFORM_PD_H_

repos/base-fiasco/src/core/include/platform_thread.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__PLATFORM_THREAD_H_

repos/base-fiasco/src/core/include/rpc_cap_factory.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__RPC_CAP_FACTORY_H_

repos/base-fiasco/src/core/include/util.h

@@ -7,10 +7,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _CORE__INCLUDE__UTIL_H_

repos/base-fiasco/src/core/io_mem_session_support.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* core includes */

repos/base-fiasco/src/core/irq_session_component.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2007-2015 Genode Labs GmbH
+ * Copyright (C) 2007-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/core/pager.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/core/pager_object.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* core includes */

repos/base-fiasco/src/core/platform.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */
@@ -436,8 +436,6 @@ Platform::Platform() :
 	if (initialized) panic("Platform constructed twice!");
 	initialized = true;
 
-	init_log();
-
 	_setup_basics();
 	_setup_mem_alloc();
 	_setup_io_port_alloc();

repos/base-fiasco/src/core/platform_pd.cc

@@ -12,10 +12,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/core/platform_thread.cc

@@ -8,10 +8,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/core/ram_session_support.cc

@@ -8,10 +8,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #include "ram_session_component.h"

repos/base-fiasco/src/core/region_map_support.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2009-2013 Genode Labs GmbH
+ * Copyright (C) 2009-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* core includes */

repos/base-fiasco/src/core/spec/x86/platform_x86.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #include <base/internal/fiasco_thread_helper.h>

repos/base-fiasco/src/core/thread_start.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/include/base/internal/fiasco_thread_helper.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2007-2013 Genode Labs GmbH
+ * Copyright (C) 2007-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FIASCO__THREAD_HELPER_H_

repos/base-fiasco/src/include/base/internal/lock_helper.h

@@ -12,10 +12,10 @@
  */
 
 /*
- * Copyright (C) 2009-2013 Genode Labs GmbH
+ * Copyright (C) 2009-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__LOCK_HELPER_H_

repos/base-fiasco/src/include/base/internal/native_thread.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__NATIVE_THREAD_H_

repos/base-fiasco/src/include/base/internal/native_utcb.h

@@ -8,10 +8,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__NATIVE_UTCB_H_

repos/base-fiasco/src/include/base/internal/parent_cap.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2015-2016 Genode Labs GmbH
+ * Copyright (C) 2015-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__PARENT_CAP_H_

repos/base-fiasco/src/include/base/internal/raw_write_string.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__RAW_WRITE_STRING_H_

repos/base-fiasco/src/include/base/internal/rpc_destination.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__BASE__INTERNAL__RPC_DESTINATION_H_

repos/base-fiasco/src/kernel/fiasco/target.mk

@@ -0,0 +1,18 @@
+TARGET = kernel-fiasco
+LIBS   = kernel-fiasco
+
+$(TARGET): sigma0 bootstrap kernel
+
+L4_BUILD_DIR = $(LIB_CACHE_DIR)/syscall-fiasco
+
+kernel:
+	$(VERBOSE)ln -sf $(LIB_CACHE_DIR)/kernel-fiasco/build/fiasco $@
+
+sigma0:
+	$(VERBOSE)ln -sf $(L4_BUILD_DIR)/bin/x86_586/l4v2/sigma0
+
+bootstrap:
+	$(VERBOSE)ln -sf $(L4_BUILD_DIR)/bin/x86_586/bootstrap
+
+clean cleanall:
+	$(VERBOSE)rm -f kernel sigma0 bootstrap

repos/base-fiasco/src/kernel/spec/x86/target.mk

@@ -1,4 +0,0 @@
-REQUIRES      = x86 32bit
-KERNEL_CONFIG = $(REP_DIR)/config/kernel-config.x86
-
--include $(PRG_DIR)/../../target.inc

repos/base-fiasco/src/kernel/target.inc

@@ -1,22 +0,0 @@
-TARGET           = fiasco
-REQUIRES        += fiasco
-FIASCO_BUILD_DIR = $(BUILD_BASE_DIR)/kernel/$(TARGET)
-FIASCO           = $(FIASCO_BUILD_DIR)/fiasco
-FIASCO_SRC       = $(L4_SRC_DIR)/kernel/fiasco
-
-$(TARGET): $(FIASCO)
-
-$(FIASCO_BUILD_DIR):
-	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
-                                     $(VERBOSE_DIR) -C $(FIASCO_SRC) BUILDDIR=$@
-	$(VERBOSE)cp $(KERNEL_CONFIG) $@/globalconfig.out
-	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
-                                     $(VERBOSE_DIR) -C $@ oldconfig
-
-$(FIASCO): $(FIASCO_BUILD_DIR)
-	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
-                                     $(VERBOSE_DIR) -C $(FIASCO_BUILD_DIR)
-	$(VERBOSE)ln -sf $@ $(BUILD_BASE_DIR)/bin/$(TARGET)
-
-clean cleanall:
-	$(VERBOSE)rm -rf $(FIASCO_BUILD_DIR)

repos/base-fiasco/src/lib/base/capability_raw.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #include <base/log.h>

repos/base-fiasco/src/lib/base/ipc.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2006-2013 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/lib/base/lock.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2007-2013 Genode Labs GmbH
+ * Copyright (C) 2007-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/lib/base/sleep.cc

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2006-2016 Genode Labs GmbH
+ * Copyright (C) 2006-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */

repos/base-fiasco/src/lib/base/thread_bootstrap.cc

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2014 Genode Labs GmbH
+ * Copyright (C) 2014-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 /* Genode includes */
@@ -37,5 +37,5 @@ void Thread::_thread_bootstrap() { }
 void Thread::_init_platform_thread(size_t, Type type)
 {
 	if (type == NORMAL) { return; }
-	_thread_cap = Genode::env()->parent()->main_thread_cap();
+	_thread_cap = Genode::env_deprecated()->parent()->main_thread_cap();
 }

repos/base-fiasco/src/lib/ld/fiasco/target.mk

@@ -0,0 +1,2 @@
+TARGET = ld-fiasco
+LIBS = ld-fiasco

repos/base-fiasco/src/sigma0/target.mk

@@ -1,5 +0,0 @@
-TARGET = sigma0
-PKGS   = sigma0/server
-LIBS   = l4v2_support
-
-include $(REP_DIR)/mk/l4_pkg.mk

repos/base-foc/doc/foc.txt

@@ -83,54 +83,6 @@ instead of building everything:
 ! make run/demo
 
 
-Running L4Linux on top of Genode
-################################
-
-To get the L4Linux running on top of Genode, you have to change prepare its
-sources:
-
-! ./tool/ports/prepare_port l4linux
-
-This will fetch the currently supported version from the L4Linux subversion
-repository, and apply a patch to it, that is needed to execute it on top of
-Genode.
-
-Before compiling L4Linux for Genode/Fiasco.OC you have to integrate the 'ports-foc'
-repository into your build environment. Therefore edit the 'etc/build.conf' file
-in your build directory, and uncomment the following line:
-
-! REPOSITORIES += $(GENODE_DIR)/repos/ports-foc
-
-After that you can build and run L4Linux by issuing:
-
-! make run/l4linux
-
-in your build directory. This run-script boots a single L4Linux instance into
-a minimal console environment. After booting completes, the run-scripts tries
-to download the Genode project webpage via the 'wget' tool within the L4Linux
-environment. If all wents fine the run-script completes successfully.
-
-
-Integration of Fiasco.OC with Genode
-####################################
-
-If you don't want the Genode build system to build the Fiasco.OC kernel for
-you, but you want to provide your own version, you have to state in the
-'etc/foc.conf' file within your build directory, where to find it:
-
-! L4_BUILD_DIR = <l4re-build-dir>
-! KERNEL       = <fiasco.oc-kernel-binary>
-
-The first variable states where to find the kernel bindings (the L4RE build
-directory), the second one states where your kernel binary can be found.
-After adding these variable to the file, you have to do a full cleanup
-in your build directory to ensure, that the right bindings are used:
-
-! make cleanall
-
-From now on, run-scripts will use your provided kernel.
-
-
 Further Information
 ###################
 

repos/base-foc/etc/foc.conf

@@ -1,20 +0,0 @@
-#
-# Fiasco.OC-specific default configuration options
-#
-
-#
-# Directory, where to search for L4 headers
-#
-# When using this file as template for a customized
-# '<builddir>/etc/kernel.conf'.
-#
-#L4_BUILD_DIR = $(HOME)/src/l4build.x86
-
-#
-# Path to the Fiasco.OC kernel
-#
-# When using this file as template for a customized
-# '<builddir>/etc/kernel.conf'.
-#
-#KERNEL = $(HOME)/src/fiasco-build.x86/fiasco
-

repos/base-foc/etc/specs.conf

@@ -1,8 +1,5 @@
-#
-# Description of build platform
-#
+SPECS += foc
 
-#
-# By default, build Fiasco.OC binaries for ia32.
-#
-SPECS ?= genode foc_x86_32
+ifneq ($(filter x86_%,$(SPECS)),)
+SPECS += pci acpi ps2 vesa framebuffer
+endif

repos/base-foc/include/base/thread_state.h

@@ -1,49 +0,0 @@
-/*
- * \brief  Thread state
- * \author Stefan Kalkowski
- * \date   2010-01-20
- *
- * This file contains the Fiasco.OC specific part of the thread state.
- */
-
-/*
- * Copyright (C) 2010-2013 Genode Labs GmbH
- *
- * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
- */
-
-#ifndef _INCLUDE__BASE__THREAD_STATE_H_
-#define _INCLUDE__BASE__THREAD_STATE_H_
-
-#include <base/capability.h>
-#include <base/lock.h>
-#include <base/thread_state_base.h>
-
-/* Fiasco includes */
-namespace Fiasco {
-#include <l4/sys/types.h>
-}
-
-namespace Genode {
-
-	struct Thread_state : Thread_state_base
-	{
-		Fiasco::l4_cap_idx_t  kcap;         /* thread's gate cap in its pd */
-		int                   id;           /* id of gate capability */
-		addr_t                utcb;         /* thread's utcb in its pd */
-		unsigned              exceptions;   /* counts exceptions raised by the thread */
-		bool                  paused;       /* indicates whether thread is stopped */
-		bool                  in_exception; /* true if thread is in exception */
-		Lock                  lock;
-
-		/**
-		 * Constructor
-		 */
-		Thread_state()
-		: kcap(Fiasco::L4_INVALID_CAP), id(0), utcb(0), exceptions(0),
-		  paused(false), in_exception(false) { }
-	};
-}
-
-#endif /* _INCLUDE__BASE__THREAD_STATE_H_ */

repos/base-foc/include/foc/capability_space.h

@@ -7,10 +7,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC__CAPABILITY_SPACE_H_

repos/base-foc/include/foc/native_capability.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC__NATIVE_CAPABILITY_H_

repos/base-foc/include/foc/native_thread.h

@@ -9,10 +9,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC__NATIVE_THREAD_H_

repos/base-foc/include/foc/receive_window.h

@@ -5,10 +5,10 @@
  */
 
 /*
- * Copyright (C) 2016 Genode Labs GmbH
+ * Copyright (C) 2016-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC__RECEIVE_WINDOW_H_

repos/base-foc/include/foc/thread_state.h

@@ -0,0 +1,49 @@
+/*
+ * \brief  Thread state
+ * \author Stefan Kalkowski
+ * \date   2010-01-20
+ *
+ * This file contains the Fiasco.OC specific part of the thread state.
+ */
+
+/*
+ * Copyright (C) 2010-2017 Genode Labs GmbH
+ *
+ * This file is part of the Genode OS framework, which is distributed
+ * under the terms of the GNU Affero General Public License version 3.
+ */
+
+#ifndef _INCLUDE__FOC__THREAD_STATE_H_
+#define _INCLUDE__FOC__THREAD_STATE_H_
+
+#include <base/capability.h>
+#include <base/lock.h>
+#include <base/thread_state.h>
+
+/* Fiasco includes */
+namespace Fiasco {
+#include <l4/sys/types.h>
+}
+
+namespace Genode { struct Foc_thread_state; }
+
+
+struct Genode::Foc_thread_state : Thread_state
+{
+	Fiasco::l4_cap_idx_t  kcap;         /* thread's gate cap in its pd */
+	int                   id;           /* id of gate capability */
+	addr_t                utcb;         /* thread's utcb in its pd */
+	unsigned              exceptions;   /* counts exceptions raised by the thread */
+	bool                  paused;       /* indicates whether thread is stopped */
+	bool                  in_exception; /* true if thread is in exception */
+	Lock                  lock;
+
+	/**
+	 * Constructor
+	 */
+	Foc_thread_state()
+	: kcap(Fiasco::L4_INVALID_CAP), id(0), utcb(0), exceptions(0),
+	  paused(false), in_exception(false) { }
+};
+
+#endif /* _INCLUDE__FOC__THREAD_STATE_H_ */

repos/base-foc/include/foc_native_cpu/client.h

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2011-2013 Genode Labs GmbH
+ * Copyright (C) 2011-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC_NATIVE_CPU__CLIENT_H_
@@ -26,14 +26,17 @@ struct Genode::Foc_native_cpu_client : Rpc_client<Foc_native_cpu>
 	explicit Foc_native_cpu_client(Capability<Native_cpu> cap)
 	: Rpc_client<Foc_native_cpu>(static_cap_cast<Foc_native_cpu>(cap)) { }
 
-	void enable_vcpu(Thread_capability cap, addr_t vcpu_state) {
+	void enable_vcpu(Thread_capability cap, addr_t vcpu_state) override {
 		call<Rpc_enable_vcpu>(cap, vcpu_state); }
 
-	Native_capability native_cap(Thread_capability cap) {
+	Native_capability native_cap(Thread_capability cap) override {
 		return call<Rpc_native_cap>(cap); }
 
-	Native_capability alloc_irq() {
+	Native_capability alloc_irq() override {
 		return call<Rpc_alloc_irq>(); }
+
+	Foc_thread_state thread_state(Thread_capability cap) override {
+		return call<Rpc_thread_state>(cap); }
 };
 
 #endif /* _INCLUDE__FOC_NATIVE_CPU__CLIENT_H_ */

repos/base-foc/include/foc_native_cpu/foc_native_cpu.h

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2011-2016 Genode Labs GmbH
+ * Copyright (C) 2011-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC_NATIVE_CPU__FOC_NATIVE_CPU_H_
@@ -17,6 +17,7 @@
 
 #include <base/rpc.h>
 #include <cpu_session/cpu_session.h>
+#include <foc/thread_state.h>
 
 namespace Genode { struct Foc_native_cpu; }
 
@@ -24,8 +25,9 @@ namespace Genode { struct Foc_native_cpu; }
 struct Genode::Foc_native_cpu : Cpu_session::Native_cpu
 {
 	virtual void enable_vcpu(Thread_capability cap, addr_t vcpu_state) = 0;
-	virtual Native_capability native_cap(Thread_capability cap) = 0;
+	virtual Native_capability native_cap(Thread_capability) = 0;
 	virtual Native_capability alloc_irq() = 0;
+	virtual Foc_thread_state thread_state(Thread_capability) = 0;
 
 
 	/*********************
@@ -35,8 +37,9 @@ struct Genode::Foc_native_cpu : Cpu_session::Native_cpu
 	GENODE_RPC(Rpc_enable_vcpu, void, enable_vcpu, Thread_capability, addr_t);
 	GENODE_RPC(Rpc_native_cap, Native_capability, native_cap, Thread_capability);
 	GENODE_RPC(Rpc_alloc_irq, Native_capability, alloc_irq);
+	GENODE_RPC(Rpc_thread_state, Foc_thread_state, thread_state, Thread_capability);
 
-	GENODE_RPC_INTERFACE(Rpc_enable_vcpu, Rpc_native_cap, Rpc_alloc_irq);
+	GENODE_RPC_INTERFACE(Rpc_enable_vcpu, Rpc_native_cap, Rpc_alloc_irq, Rpc_thread_state);
 };
 
 #endif /* _INCLUDE__FOC_NATIVE_CPU__FOC_NATIVE_CPU_H_ */

repos/base-foc/include/foc_native_pd/client.h

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2011-2013 Genode Labs GmbH
+ * Copyright (C) 2011-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC_NATIVE_PD__CLIENT_H_

repos/base-foc/include/foc_native_pd/foc_native_pd.h

@@ -6,10 +6,10 @@
  */
 
 /*
- * Copyright (C) 2011-2016 Genode Labs GmbH
+ * Copyright (C) 2011-2017 Genode Labs GmbH
  *
  * This file is part of the Genode OS framework, which is distributed
- * under the terms of the GNU General Public License version 2.
+ * under the terms of the GNU Affero General Public License version 3.
  */
 
 #ifndef _INCLUDE__FOC_NATIVE_PD__FOC_NATIVE_PD_H_

repos/base-foc/lib/import/import-syscall-foc.mk

@@ -0,0 +1,23 @@
+L4_INCLUDE_DIR := $(LIB_CACHE_DIR)/syscall-foc/include
+
+ifeq ($(filter-out $(SPECS),x86_32),)
+  INC_DIR += $(L4_INCLUDE_DIR)/x86/l4f $(L4_INCLUDE_DIR)/x86
+endif # 32bit
+
+ifeq ($(filter-out $(SPECS),x86_64),)
+  INC_DIR += $(L4_INCLUDE_DIR)/amd64/l4f $(L4_INCLUDE_DIR)/amd64
+endif # 64bit
+
+ifeq ($(filter-out $(SPECS),arm),)
+  INC_DIR += $(L4_INCLUDE_DIR)/arm/l4f $(L4_INCLUDE_DIR)/arm
+  CC_OPT  += -DARCH_arm
+endif # ARM
+
+INC_DIR += $(L4_INCLUDE_DIR)/l4f $(L4_INCLUDE_DIR)
+CC_OPT += -DCONFIG_L4_CALL_SYSCALLS
+
+#
+# Use 'regparm=0' call instead of an inline function, when accessing
+# the utcb. This is needed to stay compatible with L4linux
+#
+CC_OPT += -DL4SYS_USE_UTCB_WRAP=1

repos/base-foc/lib/mk/base-foc-common.inc

@@ -6,7 +6,7 @@
 
 include $(BASE_DIR)/lib/mk/base-common.inc
 
-LIBS += syscall startup
+LIBS += syscall-foc startup-foc
 
 SRC_CC += spin_lock.cc cap_map.cc
 SRC_CC += signal_submit.cc

repos/base-foc/lib/mk/base-foc.inc

@@ -1,4 +1,6 @@
 include $(BASE_DIR)/lib/mk/base.inc
 
+LIBS   += base-foc-common syscall-foc cxx
+
 SRC_CC += cap_map_remove.cc cap_alloc.cc
 SRC_CC += thread_start.cc

repos/base-foc/lib/mk/core-foc.inc

@@ -1,8 +1,6 @@
-REQUIRES    += foc
-
 GEN_CORE_DIR = $(BASE_DIR)/src/core
 
-LIBS        += base-common
+LIBS        += base-foc-common syscall-foc cxx
 
 SRC_CC      += stack_area.cc \
                core_log.cc \

repos/base-foc/lib/mk/kernel-foc.inc

@@ -0,0 +1,50 @@
+FOC_BUILD_DIR = $(shell pwd)/build
+FOC           = $(FOC_BUILD_DIR)/foc
+FOC_SRC      := $(call select_from_ports,foc)/src/kernel/foc/kernel/fiasco
+
+KERNEL_BUILD_OUTPUT_FILTER = 2>&1 | sed "s/^/      [fiasco.oc]  /"
+
+MAKEOVERRIDES := $(filter-out KERNEL=%,$(MAKEOVERRIDES))
+unexport KERNEL
+
+$(FOC_BUILD_DIR):
+	$(VERBOSE_MK) $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
+	                      $(VERBOSE_DIR) -C $(FOC_SRC) BUILDDIR=$@ \
+	                      $(KERNEL_BUILD_OUTPUT_FILTER)
+	$(VERBOSE)cp $(KERNEL_CONFIG) $@/globalconfig.out
+
+$(FOC): $(FOC_BUILD_DIR)
+	$(VERBOSE_MK) $(MAKE) SYSTEM_TARGET="$(CROSS_DEV_PREFIX)" \
+	                      CC="$(CC)" CXX="$(CXX)" \
+	                      $(VERBOSE_DIR) -C $(FOC_BUILD_DIR) \
+	                      $(KERNEL_BUILD_OUTPUT_FILTER)
+	$(VERBOSE)touch $@
+
+#
+# Sigma0 and bootstrap are provided as L4 packages
+#
+# We build them within the L4 build directory created by the 'syscall-fiasco'
+# library.
+#
+
+LIBS += syscall-foc
+
+PKGS := uclibc-headers \
+        uclibc-minimal \
+        l4util \
+        cxx \
+        sigma0 \
+        drivers-frst/include drivers-frst/of drivers-frst/uart \
+        bootstrap
+
+L4_BUILD_DIR := $(LIB_CACHE_DIR)/syscall-foc/build
+
+include $(REP_DIR)/lib/mk/l4_pkg.inc
+
+#
+# Execute the rules in this file only at the second build stage when we know
+# about the complete build settings, e.g., 'CROSS_DEV_PREFIX'.
+#
+ifeq ($(called_from_lib_mk),yes)
+all: $(FOC)
+endif

repos/base-foc/lib/mk/l4_pkg.inc

@@ -8,8 +8,6 @@
 #          the target
 #
 
-LIBS += platform
-
 ifeq ($(filter-out $(SPECS),x86_32),)
 	L4_BUILD_ARCH := x86_586
 endif
@@ -27,17 +25,22 @@ ifeq ($(filter-out $(SPECS),arm_v6),)
 endif
 
 ifeq ($(L4_BUILD_ARCH),)
-all: l4_build_arch_undefined
-	$(VERBOSE)$(ECHO) "Error: L4_BUILD_ARCH undefined, architecture not supported"
-	$(VERBOSE)false
+$(error L4_BUILD_ARCH undefined, architecture not supported)
 endif
 
-L4_BUILD_DIR = $(BUILD_BASE_DIR)/l4
 L4_BUILD_OPT = SYSTEM_TARGET=$(CROSS_DEV_PREFIX)
 L4_PKG_DIR  := $(call select_from_ports,foc)/src/kernel/foc/l4/pkg
 PKG_TAGS     = $(addsuffix .tag,$(PKGS))
 
-$(TARGET): $(PKG_TAGS)
+BUILD_OUTPUT_FILTER = 2>&1 | sed "s~^~      [$*]  ~"
+
+#
+# Execute the rules in this file only at the second build stage when we know
+# about the complete build settings, e.g., 'CROSS_DEV_PREFIX'.
+#
+ifeq ($(called_from_lib_mk),yes)
+all: $(PKG_TAGS)
+endif
 
 #
 # We preserve the order of processing 'l4/pkg/' directories because of
@@ -47,17 +50,7 @@ $(TARGET): $(PKG_TAGS)
 .NOTPARALLEL: $(PKG_TAGS)
 
 %.tag:
-	$(VERBOSE_MK) $(MAKE) $(VERBOSE_DIR) O=$(L4_BUILD_DIR) -C $(L4_PKG_DIR)/$* "$(L4_BUILD_OPT)"
+	$(VERBOSE_MK) $(MAKE) $(VERBOSE_DIR) O=$(L4_BUILD_DIR) -C $(L4_PKG_DIR)/$* \
+	                      "$(L4_BUILD_OPT)" $(BUILD_OUTPUT_FILTER)
 	$(VERBOSE)mkdir -p $(dir $@) && touch $@
 
-clean cleanall: clean_tags
-
-# if (pseudo) target is named after a directory, remove the whole subtree
-clean_prg_objects: clean_dir_named_as_target
-
-clean_dir_named_as_target:
-	$(VERBOSE)(test -d $(TARGET) && rm -rf $(TARGET)) || true
-
-clean_tags:
-	$(VERBOSE)rm -f $(PKG_TAGS)
-

repos/base-foc/lib/mk/l4re_support.mk

@@ -1,14 +0,0 @@
-#
-# Build L4re base libraries, needed by sigma0 and bootstrap
-
-
-# ignore stage one, visit the L4 build system at second build stage
-ifeq ($(called_from_lib_mk),yes)
-
-# packages in 'l4/pkg/'
-PKGS = uclibc-headers uclibc-minimal l4util cxx
-
-include $(REP_DIR)/mk/l4_pkg.mk
-all: $(PKG_TAGS)
-
-endif

repos/base-foc/lib/mk/platform.inc

@@ -1,59 +0,0 @@
-#
-# Create prerequisites for building Genode for Fiasco.OC
-#
-# Prior building Genode programs for Fiasco.OC, the kernel bindings must be
-# generated. This is done by building a minimalistic subset of the original
-# userland (L4re) that comes with Fiasco.OC.
-#
-
-#
-# We do this also in the first build stage to ensure that the kernel
-# port, if missing, is added to the missing-ports list of this stage.
-#
-FOC_CONTRIB_DIR := $(call select_from_ports,foc)/src/kernel/foc
-
-#
-# Execute the rules in this file only at the second build stage when we know
-# about the complete build settings, e.g., the 'CROSS_DEV_PREFIX'.
-#
-ifeq ($(called_from_lib_mk),yes)
-
-#
-# Create mirror for architecture-specific L4sys header files
-#
-L4_INC_TARGETS += l4/sys \
-                  l4f/l4/sys \
-                  l4/sigma0 \
-                  l4/vcpu
-
-all: $(addprefix $(BUILD_BASE_DIR)/include/,$(L4_INC_TARGETS))
-
-$(BUILD_BASE_DIR)/include/%:
-	$(VERBOSE)mkdir -p $(dir $@)
-	$(VERBOSE)ln -sf $(L4_BUILD_DIR)/include/$* $@
-
-#
-# Create L4 build directory
-#
-# Resetting the 'MAKEFLAGS' is important because otherwise, the L4
-# build system will stuble over predefined variables, i.e., 'LIB'
-#
-$(BUILD_BASE_DIR)/l4/.kconfig:
-	$(VERBOSE_MK) MAKEFLAGS= $(MAKE) $(VERBOSE_DIR) -C $(FOC_CONTRIB_DIR)/l4 B=$(dir $@) \
-	     DROPSCONF_DEFCONFIG="$(L4_CONFIG)" \
-	     VERBOSE="$(VERBOSE)" SYSTEM_TARGET="$(CROSS_DEV_PREFIX)"
-
-PKGS = ldscripts \
-       libgcc-pure \
-       l4sys \
-       libgcc \
-       libsigma0 \
-       libvcpu/include
-
-include $(REP_DIR)/mk/l4_pkg.mk
-all: $(PKG_TAGS)
-
-$(PKG_TAGS): $(BUILD_BASE_DIR)/l4/.kconfig
-
-endif
-

repos/base-foc/lib/mk/spec/arm/base-foc-common.mk

@@ -1,4 +1,4 @@
 # override default stack-area location
 INC_DIR += $(REP_DIR)/src/include/spec/arm
 
-include $(REP_DIR)/lib/mk/base-common.inc
+include $(REP_DIR)/lib/mk/base-foc-common.inc

repos/base-foc/lib/mk/spec/arm/base-foc.mk

@@ -1,4 +1,4 @@
 # override default stack-area location
 INC_DIR += $(REP_DIR)/src/include/spec/arm
 
-include $(REP_DIR)/lib/mk/base.inc
+include $(REP_DIR)/lib/mk/base-foc.inc

repos/base-foc/lib/mk/spec/arm/core-foc.mk

@@ -5,6 +5,6 @@ SRC_CC   += spec/arm/platform_arm.cc \
 # override default stack-area location
 INC_DIR  += $(REP_DIR)/src/include/spec/arm
 
-include $(REP_DIR)/lib/mk/core.inc
+include $(REP_DIR)/lib/mk/core-foc.inc
 
 vpath platform_services.cc $(GEN_CORE_DIR)

repos/base-foc/lib/mk/spec/arm/ld-foc.mk

@@ -0,0 +1,3 @@
+BASE_LIBS += base-foc-common base-foc
+
+include $(BASE_DIR)/lib/mk/spec/arm/ld-platform.inc

repos/base-foc/lib/mk/spec/arm/platform.inc

@@ -1,8 +0,0 @@
-#
-# Create mirror for architecture-specific L4sys header files
-#
-L4_INC_TARGETS = arm/l4/sys \
-                 arm/l4f/l4/sys \
-                 arm/l4/vcpu
-
-include $(REP_DIR)/lib/mk/platform.inc

repos/base-foc/lib/mk/spec/arm/startup-foc.mk

@@ -0,0 +1,3 @@
+LIBS += syscall-foc
+
+include $(BASE_DIR)/lib/mk/spec/arm/startup.inc

repos/base-foc/lib/mk/spec/arm/syscall-foc.inc

@@ -0,0 +1,18 @@
+L4_INC_TARGETS = arm/l4/sys \
+                 arm/l4f/l4/sys \
+                 arm/l4/vcpu
+
+CC_OPT += -Iinclude/arm
+
+include $(REP_DIR)/lib/mk/syscall-foc.inc
+
+SRC_C += utcb.c
+SRC_S += atomic_ops_s.S
+
+utcb.c:
+	$(VERBOSE)ln -sf $(L4_BUILD_DIR)/source/pkg/l4sys/lib/src/utcb.c
+
+atomic_ops_s.S:
+	$(VERBOSE)ln -sf $(L4_BUILD_DIR)/source/pkg/l4sys/lib/src/ARCH-arm/atomic_ops_s.S
+
+utcb.c atomic_ops_s.S: $(PKG_TAGS)

repos/base-foc/lib/mk/spec/arm/syscall.mk

@@ -1,5 +0,0 @@
-SRC_C += utcb.c
-SRC_S += atomic_ops_s.S
-
-vpath atomic_ops_s.S $(L4_BUILD_DIR)/source/pkg/l4sys/lib/src/ARCH-arm
-vpath utcb.c         $(L4_BUILD_DIR)/source/pkg/l4sys/lib/src

repos/base-foc/lib/mk/spec/arndale/kernel-foc.mk

@@ -0,0 +1,3 @@
+KERNEL_CONFIG := $(REP_DIR)/config/arndale.kernel
+
+include $(REP_DIR)/lib/mk/kernel-foc.inc

repos/base-foc/lib/mk/spec/arndale/platform.mk

@@ -1,6 +0,0 @@
-#
-# Configuration for L4 build system (for kernel-bindings, sigma0, bootstrap).
-#
-L4_CONFIG = $(call select_from_repositories,config/arndale.user)
-
-include $(REP_DIR)/lib/mk/spec/arm/platform.inc

repos/base-foc/lib/mk/spec/arndale/syscall-foc.mk

@@ -0,0 +1,3 @@
+L4_CONFIG := $(call select_from_repositories,config/arndale.user)
+
+include $(REP_DIR)/lib/mk/spec/arm/syscall-foc.inc

repos/base-foc/lib/mk/spec/imx53/kernel-foc.mk

@@ -0,0 +1,3 @@
+KERNEL_CONFIG := $(REP_DIR)/config/imx53.kernel
+
+include $(REP_DIR)/lib/mk/kernel-foc.inc

repos/base-foc/lib/mk/spec/imx53/platform.mk

@@ -1,6 +0,0 @@
-#
-# Configuration for L4 build system (for kernel-bindings, sigma0, bootstrap).
-#
-L4_CONFIG = $(call select_from_repositories,config/imx53.user)
-
-include $(REP_DIR)/lib/mk/spec/arm/platform.inc