--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-003D2C5B-09DC-5BD1-AF45-A0FCB56F567B.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-003D2C5B-09DC-5BD1-AF45-A0FCB56F567B" xml:lang="en"><title>ROMBUILD</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>ROMBUILD is the Symbian platform binary XIP (execute-in-place)
+ROM builder. It is normally invoked through <xref href="GUID-E4447BEF-33D2-5099-BCC1-C72FBB3B0463.dita">BUILDROM</xref>,
+the Symbian platform ROM configuration tool that acts as a front-end
+to ROMBUILD. </p>
+<section id="GUID-CFAB320B-5F0D-4E76-AD96-FE6EE8D3BE43"> </section>
+<section id="GUID-06C4A9F7-E8D4-5A53-97BA-F3C2973B661A"><title>ROMBUILD
+command syntax</title><p>If the OBY files are encoded in UTF-8 with
+non-ASCII character support, use the following the ROMBUILD command
+syntax:</p><codeblock id="GUID-379818BF-A17B-5CAF-A311-3EE4142EE51D-GENID-1-2-1-8-1-1-6-1-1-5-1-2-3-3" xml:space="preserve">ROMBUILD [options] [–oby-charset=utf-8 &lt;obyfile&gt;] [-datadrive=&lt;fat.oby&gt;]</codeblock><p>If the OBY files are encoded in local character set with non-ASCII
+characters support, use the following the ROMBUILD command syntax:</p><codeblock id="GUID-B3A01582-9631-57C6-A654-D5539DF1AE54-GENID-1-2-1-8-1-1-6-1-1-5-1-2-3-5" xml:space="preserve">ROMBUILD [options] &lt;obeyfile&gt; [-datadrive=&lt;fat.oby&gt;]</codeblock> <p>The following command line <codeph>options</codeph> are supported: </p> <table id="GUID-321B472A-D58B-5348-A701-EA7E33E3A0B5">
+<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
+<tbody>
+<row>
+<entry><p> <codeph>–argfile=&lt;parameter file&gt;</codeph>  </p> </entry>
+<entry><p>Accepts a parameter file, which contains a list of command-line
+parameters specific to the ROM tools, as input. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph> -? </codeph>  </p> </entry>
+<entry><p>Displays more detailed help for the command. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-coff-header</codeph>  </p> </entry>
+<entry><p>Uses a PE-COFF header instead of a Symbian platform header. PE-COFF is a Portable Executable–Common Object File
+Format and is a Microsoft extension to the COFF standard. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph> -compress</codeph>  </p> </entry>
+<entry><p>Compresses executable files where possible using the inflate
+(Deflate, Huffman+LZ77) algorithm unless the <codeph>-compressionmethod</codeph> keyword is used to override the default (see below). </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-compressionmethod [none | inflate | bytepair]</codeph>  </p> </entry>
+<entry><p>Specifies the compression algorithm to use. Can be used
+either with the <codeph>-compress</codeph> keyword or alone. </p> <p><table id="GUID-34E5FD4C-7B82-5342-85C3-C84A706C8C17-GENID-1-2-1-8-1-1-6-1-1-5-1-2-3-7-1-3-5-2-2-1">
+<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
+<tbody>
+<row>
+<entry><p> <codeph>none </codeph>  </p> </entry>
+<entry><p>No compression is used. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>inflate </codeph>  </p> </entry>
+<entry><p>Compresses executable files using the default (Deflate,
+Huffman+LZ77) algorithm. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>bytepair </codeph>  </p> </entry>
+<entry><p>Compresses executable files using the bytepair algorithm.
+Bytepair compression allows faster decompression than the default
+Deflate, Huffman+LZ77 algorithm and supports demand paging by performing
+compression and decompression of code in independent 4 KB pages. </p> </entry>
+</row>
+</tbody>
+</tgroup>
+</table> </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>coreimage=&lt;core ROM image file&gt;</codeph>  </p> </entry>
+<entry><p>Uses the specified core image file as the basis for creating
+the ROM image extension. </p> <p>If the given core ROM image file
+is invalid or does not exist, an error message is displayed. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-d&lt;bitmask&gt; </codeph>  </p> </entry>
+<entry><p>Sets the trace bitmask; this only applies to debug builds. </p> <p>The simplest way of specifying this is to use a string of hexadecimal
+characters starting with 0x (for example, 0x01234567). However, any
+string that can be interpreted and translated into a valid TUint value
+may be used. See the standard C function <codeph>strtoul()</codeph>. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-lowmem</codeph>  </p> </entry>
+<entry><p>Reduces the physical memory consumption during image generation. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-loglevel&lt;level&gt;</codeph>  </p> </entry>
+<entry><p>Level of information to log file. The following valid log
+levels are available: </p> <p><table id="GUID-6D12A1F6-70D6-5CAC-891F-CC0E98D21E70">
+<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
+<tbody>
+<row>
+<entry><p> <codeph>0</codeph>  </p> </entry>
+<entry><p>Default level of information to log file. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>1</codeph>  </p> </entry>
+<entry><p>Logs the host or the ROM filenames, the file size, and the
+hidden attribute in addition to the <codeph>loglevel 0</codeph> information. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph> 2</codeph>  </p> </entry>
+<entry><p>Logs the E32 file header attributes such as UIDs, data size,
+heap size, stack size, VID, SID, and priority in addition to the <codeph>loglevel 1</codeph> information. </p> </entry>
+</row>
+</tbody>
+</tgroup>
+</table> </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-no-header </codeph>  </p> </entry>
+<entry><p>Suppresses the image loader header. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-no-sorted-romfs </codeph>  </p> </entry>
+<entry><p>Does not add sorted entry arrays (6.1 compatible). It is
+a table of offsets for the subdirectories and files which are not
+in the sorted order. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-r&lt;fileName&gt;</codeph>  </p> </entry>
+<entry><p>Compares the generated ROM image with the ROM image whose
+file name is specified. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-s[log|screen|both] </codeph>  </p> </entry>
+<entry><p>Displays a summary of the size to the specified destination,
+that is, to the log, to the screen or to both the log and the screen. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-v </codeph>  </p> </entry>
+<entry><p>Verbose mode. </p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-wstdpath</codeph>  </p> </entry>
+<entry><p>Displays a warning if a file is placed in a non-standard
+directory when <codeph>PlatSecEnforceSysBin</codeph> is set to <codeph>OFF</codeph>.  </p><p> For example, the following instruction in
+OBY file leads to a warning when <codeph>-wstdpath</codeph> is used
+and <codeph>PlatSecEnforceSysBin</codeph> is <codeph>OFF</codeph>:</p><p><codeph>File=ABI_DIR/BUILD_DIR/hello.exe myfolder/bin/hello.exe</codeph></p> </entry>
+</row>
+<row>
+<entry><p> <codeph>-j&lt;NUM_OF_WORKING_THREADS&gt;</codeph></p> </entry>
+<entry><p>Specifies the number of working threads that can run concurrently
+to create a ROM image. The <codeph>&lt;NUM_OF_WORKING_THREADS&gt;</codeph> must be an integer in the range 1-128. </p> <p>If the <codeph>-j</codeph> option is not specified or an invalid value is specified, ROMBUILD
+uses the following ways to determine the number of working threads: </p> <ul>
+<li id="GUID-7B81919D-9F6A-5945-A311-EFDE7B0985F5"><p>If the <codeph>NUMBER_OF_PROCESSORS</codeph> environment variable is set correctly,
+ROMBUILD uses the number of processors as the number of working threads. </p> </li>
+<li id="GUID-6C697962-2AE9-5AEC-950F-304ABE720501"><p>If the <codeph>NUMBER_OF_PROCESSORS</codeph> environment variable is not set or
+is invalid, the default value <codeph>8</codeph> is used as the number
+of working threads. </p> </li>
+</ul> </entry>
+</row>
+<row>
+<entry><p><codeph>-gendep</codeph></p></entry>
+<entry><p>Generates a dependencies file describing internal dependencies
+among executables or dlls in a ROM image.</p><p><b>Note</b>: You can
+only generate dependence information in the paged section of a ROM
+image.</p></entry>
+</row>
+<row>
+<entry><p><codeph>-symbols</codeph></p></entry>
+<entry><p>Generates symbols for each data or executable specified
+in the OBY file. </p><p><b>Note</b>: The symbols file is not generated
+by default.</p></entry>
+</row>
+</tbody>
+</tgroup>
+</table> <p> <codeph>&lt;obeyfile&gt;</codeph> is a standard text file
+containing statements that are used to control the operation of the
+tool. </p> <p>See the <xref href="GUID-9CF985F1-C100-5999-9410-58B7865A1E18.dita">OBEY files</xref> reference for the full syntax. </p> </section>
+</conbody></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-009D71C6-481F-5EF1-B230-EB64F67047C8.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-009D71C6-481F-5EF1-B230-EB64F67047C8" xml:lang="en"><title>Calibration</title><shortdesc>Calibration of the Digitizer Driver is required to convert between
+digitiser ADC values and screen coordinates. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>Calibration is done through a user-side calibration application. </p>
+<p>The platform specific layer performs the following calculation to convert
+between ADC values and co-ordinates: </p>
+<fig id="GUID-932E1DED-C393-5C26-A08F-E270CF5DC90B">
+<image href="GUID-D6861A7A-1845-52AF-BB09-4B97E6B8AA13_d0e10260_href.png" placement="inline"/>
+</fig>
+<p>Where the <b>R</b> matrix determines the scaling and rotation, and the <b>T</b> vector
+determines the translation. </p>
+<p>This conversion is implemented by the platform specific layer's implementation
+of <xref href="GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9.dita#GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9/GUID-A51F6890-2D47-3FCC-A51B-19479658E49F"><apiname>DDigitiser::DigitiserToScreen()</apiname></xref> and <xref href="GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9.dita#GUID-2EDAF642-2399-3594-986A-5E8A5EEA01B9/GUID-F85119E0-83DC-3C54-BDFC-4F156ADFE538"><apiname>DDigitiser::ScreenToDigitiser()</apiname></xref>.
+Default implementations are provided by the template port. Note, however,
+that in these implementations, the calculation is slightly more complex because
+screen coordinate values are left shifted 16 bits. This allows the operations
+to use integer divisions without loosing precision. </p>
+<p>All that you need to do is to provide an initial set of values for <b>R</b> and <b>T</b>.
+An example of how to set them up is included in the template port. </p>
+<p>The principle is that the application draws cross hairs on the screen,
+and then invites the user to touch these points. The digitiser ADC value is
+used to calculate the digitiser to screen pixel value transformation. </p>
+<p>Any calibration code will interface with the <xref href="GUID-2D977A02-5928-5441-8AE7-42A722F2A4B8.dita#GUID-2D977A02-5928-5441-8AE7-42A722F2A4B8/GUID-4DA41221-40B9-5BC7-B2C6-7C6EB4522508">User-Side
+Hardware Abstraction</xref> component using four <xref href="GUID-8B3280A2-318F-380C-B2A4-894C3C675868.dita"><apiname>UserHal</apiname></xref> functions. </p>
+<p>On a cold restart, the calibration application goes through the following
+steps: </p>
+<ul>
+<li id="GUID-DDEF3346-09D3-56B1-A9EE-CC520620611B"><p>Gets the calibration
+points by using <xref href="GUID-8B3280A2-318F-380C-B2A4-894C3C675868.dita#GUID-8B3280A2-318F-380C-B2A4-894C3C675868/GUID-57FFFEEF-200A-3F62-937F-181760F756A9"><apiname>UserHal::CalibrationPoints()</apiname></xref>  </p> </li>
+<li id="GUID-F93D82ED-924D-5268-807F-8F52F18A1A9E"><p>Sets calibration points
+by using: <xref href="GUID-8B3280A2-318F-380C-B2A4-894C3C675868.dita#GUID-8B3280A2-318F-380C-B2A4-894C3C675868/GUID-D494A58D-BBFA-3D3B-A979-A7CB4045EF23"><apiname>UserHal::SetXYInputCalibration()</apiname></xref>  </p> </li>
+<li id="GUID-C368C9AA-BE3C-5B95-AEDA-703B91059AFB"><p>Saves calibration data
+by using: <xref href="GUID-8B3280A2-318F-380C-B2A4-894C3C675868.dita#GUID-8B3280A2-318F-380C-B2A4-894C3C675868/GUID-B93BD9B9-9F33-337D-A110-993B717F1D50"><apiname>UserHal::SaveXYInputCalibration()</apiname></xref>  </p> </li>
+</ul>
+<p>On a warm restart, the calibration application just restores calibration
+data using <xref href="GUID-8B3280A2-318F-380C-B2A4-894C3C675868.dita#GUID-8B3280A2-318F-380C-B2A4-894C3C675868/GUID-63CC94BD-CD0C-3B2C-8714-1A976FE7D0DD"><apiname>UserHal::RestoreXYInputCalibration()</apiname></xref>. </p>
+</conbody></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-01072199-382F-4691-AC0D-D1226EE5CF2F.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-01072199-382F-4691-AC0D-D1226EE5CF2F" xml:lang="en"><title>Time Client Interface Quick Start</title><shortdesc>Explains how to use the interface between the Time platform
+service and its clients.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<section id="GUID-91FBBDBE-A015-4B6A-A1DB-74D87A6DB816"><title>Introduction</title><p>The Time client interface is used when communicating with the
+Real Time Clock (RTC). This client interface can be used to check
+that the RTC is working correctly, maintain its request queue and
+to set/reset the wake-up alarm.</p> </section>
+<section id="GUID-C072C87B-323F-4678-BD81-7D34F2E9E6DF"><title>Time
+client interface limitations</title><p>None</p></section>
+<section id="GUID-E306BFAB-60CC-46D5-8176-A2FEDF55C89B"><title>Adaptation
+dependencies</title><p>None</p></section>
+<section id="GUID-4ADBBA99-D1D6-4E1A-9C5A-81E882011A61"><title>Time
+client interface classes</title><p>The following classes provide the
+RTC interface:</p><table id="GUID-D01391B7-9427-45F3-A873-5FE9BDEDCCA4">
+<tgroup cols="2"><colspec colname="col1" colwidth="0.46*"/><colspec colname="col2" colwidth="1.54*"/>
+<tbody>
+<row>
+<entry><p><b>Name</b></p></entry>
+<entry><p><b>Description</b></p></entry>
+</row>
+<row>
+<entry><p><xref href="GUID-CC79A63E-15DF-3437-983B-9A90966B3004.dita"><apiname>MRtcAdaptation</apiname></xref></p></entry>
+<entry><p>Provides the interface between the Real Time Clock (RTC)
+and the upper layers of the OS.</p></entry>
+</row>
+<row>
+<entry><p><xref href="GUID-69C70CA3-1121-3C5B-AEA4-B2E0245539B9.dita"><apiname>ASIC</apiname></xref></p></entry>
+<entry><p>Provides an interface to the Application Specific Integrated
+Circuit (ASIC) that is being used.</p></entry>
+</row>
+</tbody>
+</tgroup>
+</table><p>The functionality provided by this class, can be split
+into the following groups:</p><ul>
+<li><p>Diagnostics</p></li>
+<li><p>Management of the wake-up alarm</p></li>
+<li><p>Request management</p></li>
+<li><p>Set and read the RTC</p></li>
+</ul></section>
+<section id="GUID-7A7E1108-5D58-4500-AB6C-BFC8CA65EE0E"><title>Diagnostics</title><p>These methods are used to test that the RTC is working correctly.
+The methods that are included in this group are:</p><ul>
+<li><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-98F7B0DE-CBA6-430C-972D-02F9AB444E1B">MRtcAdaptation::ValidateRtc()</xref></li>
+<li><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-3D0DD0AB-4F3F-4411-B5E8-9199AB71F1A6">ASIC::SetSystemTimeCalibration()</xref></li>
+</ul></section>
+<section id="GUID-CB062F05-0410-4B8D-930F-2DD55BAFC829"><title>Management
+of the wake-up alarm</title><p>This group of methods, relate to the
+setting and releasing of the wake-up alarm. The methods that are included
+in this group are:<ul>
+<li><p><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-813CB223-3385-4293-9D1C-8C712B031E8F">MRtcAdaptation::SetWakeUpAlarm()</xref></p></li>
+<li><p><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-DE156EC7-759F-4BFC-BCAA-FE0E84CC83D9">MRtcAdaptation::UnsetWakeUpAlarm()</xref></p></li>
+</ul></p></section>
+<section id="GUID-DDED587F-ADBF-4C3D-A263-8A1D333EE85C"><title>Request
+management</title><p>Calls to the RTC are placed in a request queue,
+waiting for the RTC to process them. Calls to the other two groups
+of functionality add requests to the queue for the RTC, the methods
+in this group remove them.  The methods that are included in this
+group are:</p><ul>
+<li><p><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-1111CFEA-D85C-4107-BB14-618C6A5A0B3F">MRtcAdaptation::Cancel()</xref></p></li>
+<li><p><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-2EE46E01-006D-431E-B6C0-CAEBDDE5D53A">MRtcAdaptation::Release()</xref></p></li>
+</ul></section>
+<section id="GUID-69B30672-ABD6-421A-967A-3669C8477505"><title>Set
+and read the RTC</title><p>These functions are used to set and read
+the RTC. Both functions measure time as the number of seconds since
+the start of the year 2000.</p><ul>
+<li><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-C69C0225-1779-4FFC-B071-D18B71C18A74">ASIC::SystemTimeInSecondsFrom2000()</xref></li>
+<li><xref href="GUID-8D237BD6-9759-4180-B190-F1624594017F.dita#GUID-8D237BD6-9759-4180-B190-F1624594017F/GUID-1BFBAEE5-AE48-4624-BD34-3D6B936C8C3B">ASIC::SetSystemTimeInSecondsFrom2000()</xref></li>
+</ul></section>
+</conbody></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-01F1F488-8E95-56B0-818E-6096CAE4C50C.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-01F1F488-8E95-56B0-818E-6096CAE4C50C" xml:lang="en"><title>Architecture</title><shortdesc>This topic describes the architecture of the Base Starter program, <filepath>e32strt.exe</filepath>.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>The Base Starter is started by the File Server, <filepath>EFILE.EXE</filepath>,
+near the end of the boot process. </p>
+<p> <filepath> EFILE.EXE</filepath> initialises generic file services. <filepath>e32strt.exe</filepath> performs
+handset specific initialisation. The Base Starter completes the initialisation
+of the file server, and then creates the system starter process. The system
+starter process is the next process in the chain of processes responsible
+for starting all the major Symbian platform services. The following
+diagram shows the relative position of the Base Starter in the start-up sequence. </p>
+<fig id="GUID-C184517B-0E86-5E22-BCD6-F4DFD7AEA731">
+<title>           Base Starter architecture         </title>
+<image href="GUID-CEDA0EFF-A1D4-53FE-9BF2-DB9AA857BCF5_d0e3163_href.png" placement="inline"/>
+</fig>
+</conbody></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-024EE22F-4B86-48EF-A55E-C9C1C7E9BADB.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-024EE22F-4B86-48EF-A55E-C9C1C7E9BADB" xml:lang="en"><title>SDIO Client Interface</title><shortdesc>Describes SDIO APIs and their use in a device driver.</shortdesc><prolog><metadata><keywords/></metadata></prolog></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-02B40662-B5F3-59BD-832B-9A28FE3B51C7.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-02B40662-B5F3-59BD-832B-9A28FE3B51C7" xml:lang="en"><title>Debug</title><shortdesc>This topic describes how to use debug messages in the USB
+client controller.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>As the USB PDD runs in kernel mode, debug <codeph>printf</codeph> are implemented using the <codeph>KTRACE</codeph> macro.
+This macro takes two arguments: </p>
+<ul>
+<li id="GUID-E3A1AA52-12D9-58EE-A459-46FAA7F5001C"><p>The debug message
+type </p> </li>
+<li id="GUID-2D7B1C30-563C-5346-8DBC-943839008874"><p>A kernel object
+that takes a message string as a constructor. </p> </li>
+</ul>
+<p>Two debug message types are used: </p>
+<ul>
+<li id="GUID-962DAE50-32C5-53AB-A203-E08CA57252D5"><p> <codeph>KPANIC</codeph> for error messages </p> </li>
+<li id="GUID-6F6409F4-37B1-5713-A763-61B477545706"><p> <codeph>KUSBPSL</codeph> for PSL information messages </p> </li>
+</ul>
+<p>The following code samples illustrate their use: </p>
+<codeblock id="GUID-A130740F-20FA-5825-9BDB-9CE234971757" xml:space="preserve">_KTRACE_OPT(KPANIC, Kern::Printf("Error: USB Controller not present"));</codeblock>
+<codeblock id="GUID-6A8812CE-791C-5C62-AC67-29FF5098D9E4" xml:space="preserve">_KTRACE_OPT(KUSBPSL, Kern::Printf("Received new Ep0 Setup packet"));</codeblock>
+<note>Do not use the <codeph>KUSB</codeph> flag. This flag is used
+within the PDD PIL and the USB LDD only.</note>
+</conbody></concept>
\ No newline at end of file

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-0346036B-A470-4C18-B276-3A3485F6A069.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-0346036B-A470-4C18-B276-3A3485F6A069" xml:lang="en"><title>Design
+Options</title><shortdesc>These documents describe high-level implementation choices for
+a device driver.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p> </p>
+</conbody></concept>
\ No newline at end of file

Binary file Adaptation/GUID-04FF36CE-DEFA-45DC-BAAF-77F3BB649AFF-master.png has changed

Binary file Adaptation/GUID-04FF36CE-DEFA-45DC-BAAF-77F3BB649AFF_d0e499_href.png has changed

--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Adaptation/GUID-052F58B7-117B-5EDD-A3D5-CB0DE6A4E239.dita	Fri Oct 15 14:32:18 2010 +0100
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-052F58B7-117B-5EDD-A3D5-CB0DE6A4E239" xml:lang="en"><title>IIC SHAI Implementation Layer: Generic Considerations</title><shortdesc>This document explains how to implement the SHAI implementation
+layer for IIC.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<section id="GUID-C3EE341A-BEAB-4E0C-A91E-7A1A285BCE96"><title>Purpose</title> <p>This document covers information which is generic to master and
+slave channel implementation </p> <p><b>Intended Audience</b> </p> <p>Base porting engineers. </p> <p><b>Introduction</b> </p> <p>IIC
+buses (a term used in this document to represent serial inter-chip
+buses that IIC can operate on) are a class of bus used to transmit
+non time-critical data between components of a hardware system. </p> </section>
+<section id="GUID-38B543E8-06DB-417F-8B8E-84F6B43DF8BF"><title>Generic
+architecture</title> <p>Different IIC buses have a large amount of
+functionality in common, but some functionality is specific to individual
+implementations. For this reason, the IIC software has an architecture
+consisting of two layers, the Platform Independent Layer (PIL) and
+the SHAI implementation layer. The Platform Independent Layer is a
+set of classes which encapsulate generic functionality and have been
+implemented for you. The SHAI implementation layer is an interface
+which you must implement yourself to encapsulate the functionality
+specific to the platform you are working on. </p> <p>You implement
+the SHAI implementation layer by subclassing the classes of the Platform
+Independent Layer and writing functions that provide an abstraction
+of your hardware. To access the hardware you are strongly recommended
+to use existing Symbian APIs such as e.g. <codeph>AsspRegister</codeph> to access hardware registers, or <codeph>GPIO</codeph> to access
+GPIO pins). </p> <p>An IIC channel operates in one of two modes, master
+and slave, and there are separate master and slave APIs to be implemented.
+In master mode, a channel and a client communicating with that channel
+execute in two separate threads. In slave mode there is only one thread
+for both channel and client. </p> <p>The SHAI implementation and platform
+independent APIs assume an interrupt-driven approach to implementation.
+An event on hardware triggers an interrupt, which then signals this
+event to the channel thread (where client is master) or client thread
+(where client is slave). This means that implementation involves writing
+interrupt service routines (ISRs) and a DFC queue to hold the callbacks
+which respond to them. For both master and slave operation, the callbacks
+are queued for execution on the client thread - so the client thread
+must not be blocked, otherwise the callbacks will never run.</p><p>Clients of a master channel request transactions for execution in
+either a synchronous or asynchronous manner. This results in the transaction
+being entered in the channel’s request queue.  </p><p>If synchronous
+execution is requested, the client thread is blocked until the transaction
+completes (either an ISR or polling mechanism in the SHAI implementation
+layer recognizes the transaction has completed, and it calls the PIL
+method <codeph>CompleteRequest()</codeph>, which will unblock the
+client thread.  </p><p>If asynchronous execution is requested, the
+client thread is not blocked, and may continue to perform other tasks.
+In the meanwhile, the channel thread will retrieve the next transaction
+from the request queue and pass it to the SHAI implementation layer
+for processing. When the transaction completes, the SHAI implementation
+layer calls the PIL method <codeph>CompleteRequest()</codeph> and
+this adds the client’s callback to the client’s DFC queue.  </p><p>A client of a slave channel provides receive and transmit buffers
+to be used and specifies the types of event (trigger) that it wishes
+to be notified of. When ANY event occurs, the SHAI implementation
+layer should call the PIL method <codeph>NotifyClient()</codeph>;
+this determines whether the reported triggers qualify for notifying
+the client – if so, the client callback is added to the client’s DFC
+queue for execution. Note that the same mechanism is used to notify
+the client of completion of asynchronous capture of the channel, and
+of bus errors.</p> <p>You should refer to the template port at <filepath>\os\kernelhwsrv\bsptemplate\asspandvariant\template_assp\iic</filepath> for more information. </p> </section>
+</conbody><related-links>
+<link href="GUID-0C8318B1-71D7-5384-97EB-85CBBC3E6B84.dita"><linktext>IIC
+SHAI Implementation Layer: Master Channel</linktext></link>
+<link href="GUID-C9644081-004E-5DA0-8133-A32EEA91EF5E.dita"><linktext>IIC
+SHAI Implementation Layer: Slave Channel</linktext></link>
+<link href="GUID-9986DCC6-EE73-59FB-BDAC-9B09DC64FBCE.dita"><linktext>Client
+of Master Channel Tutorial</linktext></link>
+<link href="GUID-F461CBB3-F8D1-5961-AD51-5741143A1CB1.dita"><linktext>Client
+of Slave Channel Tutorial</linktext></link>
+<link href="GUID-B2F86F54-EF50-56DB-ADF7-15325AC9324D.dita"><linktext>IIC
+Concepts</linktext></link>
+<link href="GUID-3A30DA16-ECA8-5639-A9DC-6BE2AD55420B.dita"><linktext>I2C
+Technology Guide</linktext></link>
+</related-links></concept>
\ No newline at end of file