1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-C86A7929-DC0F-50FA-93CB-662A22C4CD35" xml:lang="en"><title>Device

    13 Variant Using Multiple Keyspace Files</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>This topic describes the use of multiple keyspace files on multiple ROFS

    15 layers to create a device variant. </p>

    16 <section><title>Introduction</title> <p>The central respository consists of

    17 keyspaces used to store application settings. The device variant creators

    18 need to modify these settings for every variant of the device. </p> <p>In

    19 the older method the variant engineer has to branch out the exisiting keyspace

    20 files , modify the settings and reflash the device with the new keyspace files.

    21 The disadvantage of the older method is that the variant engineer has to maintain

    22 multiple keyspace files. The modified keyspace must have the same files name

    23 as the existing one. </p> </section>

    24 <section><title>Multiple ROFS layers </title> <p>The central repository now

    25 supports keyspace that is composed of multiple files. A new keyspace file

    26 is created for a new ROFS layer. This enables the variant engineers to modify

    27 a specific setting in the keyspace in one layer and merge the repository with

    28 the new settings. The new feature to modify specific settings of a keyspace

    29 reduces the time to create different variants. </p> </section>

    30 <section><title>Merge the settings</title> <p>The figure below shows how a

    31 specific setting is modified in the new meachnism. In the example below the

    32 keyspace d is modified in the new ROFS layer to create a variant. The central

    33 repository reads the keyspace files and merges the modified settings of <codeph>keyspace

    34 d</codeph>. The settings in the higher ROFS layer get the priority of the

    35 settings. The higher ROFS layers cannot modify the global properties of the

    36 keyspaces like metadata, owner information and the access control information. </p> <fig id="GUID-BABA2027-0E54-575A-8A59-EB771CF46529">

    37 <title>              Central repository - Modify a setting            </title>

    38 <image href="GUID-D7179664-C442-5253-9925-994CA0C63B50_d0e569071_href.png" placement="inline"/>

    39 </fig> <p>The figure below shows how a new setting is added to the central

    40 repository keyspace. </p> <fig id="GUID-B1ED9F5D-4490-5F61-A084-44C8C6C0978C">

    41 <title>              Central repository - Add a new setting            </title>

    42 <image href="GUID-3A07445A-1CD4-5556-BE65-553A4A251789_d0e569082_href.png" placement="inline"/>

    43 </fig> </section>

    44 <section><title>Advantages</title> <p>The advantages of using

    45 multiple ROFS layer to create device variant are: </p> <ul>

    46 <li id="GUID-EED83088-C966-5206-94B3-4B9B693F6CF7"><p>variant engineers can

    47 modify selective settings in a keyspace </p> </li>

    48 <li id="GUID-5FCD32A3-8780-5B5C-BE29-0A6BAA068EF6"><p>no need to branch and

    49 maintain multiple keyspace files for each variant created </p> </li>

    50 <li id="GUID-89B96F5E-F33D-5512-889A-98D6A9A35033"><p>central repository can

    51 detect the multiple keyspace files at run time and merge the settings as one

    52 keyspace </p> </li>

    53 </ul> </section>

    54 <section><title>Guidelines</title> <p>The following are some guidelines to

    55 use the multiple ROFS layers to create device variant: </p> <ul>

    56 <li id="GUID-2D54FF98-37FE-554A-9C33-A9E60FFA6EF8"><p>Use the binary files

    57 (CRE) or text files to initialise the keyspaces </p> </li>

    58 <li id="GUID-97C5701A-58A5-57FD-A1F6-B36CB169D073"><p>Do not use the combination

    59 of text and binary files for a keyspace. Use one format of the initialisation

    60 files. </p> </li>

    61 <li id="GUID-1A5774F2-9CD9-509C-B17C-83990C51973F"><p>The keyspace files in

    62 higher ROFS layers must not modify the global properties such as metadata,

    63 owner information and access control information. </p> </li>

    64 </ul> </section>

    65 <section><title>Errors</title> <p>The following table shows the possible errors

    66 that may occur in use of multiple ROFS layers for device variant creation: </p> <table id="GUID-78196B5E-6474-5C23-9488-10290CA7D3D0">

    67 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>

    68 <thead>

    69 <row>

    70 <entry>Error</entry>

    71 <entry>Reason for the error</entry>

    72 </row>

    73 </thead>

    74 <tbody>

    75 <row>

    76 <entry><p> <codeph>CENREPCLI: Panic 8</codeph>  </p> </entry>

    77 <entry><p>The binary files (CRE) must be converted with the new central repository

    78 conversion tool. </p> </entry>

    79 </row>

    80 <row>

    81 <entry><p> <codeph>CENREPCLI: Panic 9</codeph>  </p> </entry>

    82 <entry><p>The keyspace files in the higher layer is trying to modify a global

    83 property </p> </entry>

    84 </row>

    85 <row>

    86 <entry><p> <codeph>CENREPCLI: Panic 10</codeph>  </p> </entry>

    87 <entry><p>Higher layer keyspace file is trying to modify a type of a setting

    88 in the lower layer </p> </entry>

    89 </row>

    90 <row>

    91 <entry><p> <codeph>CENREPCLI: Panic 11</codeph>  </p> </entry>

    92 <entry><p>The default ROFS layer file is associated with <codeph>exattrib=u

    93                   </codeph> attribute </p> </entry>

    94 </row>

    95 </tbody>

    96 </tgroup>

    97 </table> </section>

    98 </conbody><related-links>

    99 <link href="GUID-E3BE62B2-9625-5F79-84A4-0248A3F36225.dita"><linktext> Central

   100 Repository Access Guide</linktext></link>

   101 <link href="GUID-1C683226-C142-5C7B-BD20-060058352B08.dita"><linktext>Central Repository

   102 Guide </linktext></link>

   103 <link href="GUID-3D152CC5-AF20-520A-AB67-457F956A5551.dita"><linktext>Device Variant

   104 With Multiple ROFS Layers                 Tutorial </linktext></link>

   105 </related-links></concept>