|
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-C38DA704-8868-479B-AF81-375E0A2F5BCC" xml:lang="en"><title>Name</title><shortdesc>This document describes how names are assigned to device drivers.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
13 <section id="GUID-905BD0EF-85EB-4568-B810-0D0D40B3CFDA"> <p>Each |
|
14 Symbian platform device driver has a name. When the driver is |
|
15 loaded by the user, LDDs and PDDs register themselves using a name. LDDs and |
|
16 PDDs have different names, which are used to identify the logical device and |
|
17 physical device objects. </p> <p>The following shows how the example device |
|
18 drivers set their names: </p> <codeblock id="GUID-83FA2EE4-2193-5D76-A5F8-BA26DCFEBE06" xml:space="preserve">_LIT(KDriverPddName," d_expio.pdd"); |
|
19 |
|
20 // Called while loading PDD |
|
21 TInt DExH4PhysicalDevice::Install() |
|
22 { |
|
23 return SetName(&KDriverPddName); |
|
24 }</codeblock> <codeblock id="GUID-B0A503EE-F823-51F4-B7BD-A9852E1B0864" xml:space="preserve">_LIT(KDriverName, " d_expio"); |
|
25 |
|
26 // Called while loading LDD |
|
27 TInt DExDriverLogicalDevice::Install() |
|
28 { |
|
29 return SetName(&KDriverName); |
|
30 }</codeblock> <p>The framework uses driver names to identify the PDDs |
|
31 that can be used with a given LDD. This can happen in two ways: </p> <ul> |
|
32 <li id="GUID-0801CDDD-D1FB-531A-9361-97707C35C2D1"><p>The framework uses the |
|
33 name of the PDD factory object passed by the user while creating the logical |
|
34 channel. This requires a PDD with that name to be already loaded, and its |
|
35 factory object created. The framework searches for a PDD factory object with |
|
36 the specified name. </p> </li> |
|
37 <li id="GUID-A6049F4E-7DC1-5ED9-B40B-1985FF837469"><p>If the user does not |
|
38 pass the PDD name explicitly, then the framework searches all PDD factory |
|
39 objects that have a name in the form of x.y, where x is the name of the LDD |
|
40 factory object. </p> </li> |
|
41 </ul> </section> |
|
42 </conbody></concept> |