diff -r 578be2adaf3e -r 307f4279f433 Adaptation/GUID-C38DA704-8868-479B-AF81-375E0A2F5BCC.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Adaptation/GUID-C38DA704-8868-479B-AF81-375E0A2F5BCC.dita Fri Oct 15 14:32:18 2010 +0100 @@ -0,0 +1,42 @@ + + + + + +NameThis document describes how names are assigned to device drivers. +

Each +Symbian platform device driver has a name. When the driver is +loaded by the user, LDDs and PDDs register themselves using a name. LDDs and +PDDs have different names, which are used to identify the logical device and +physical device objects.

The following shows how the example device +drivers set their names:

_LIT(KDriverPddName," d_expio.pdd"); + +// Called while loading PDD +TInt DExH4PhysicalDevice::Install() + { + return SetName(&KDriverPddName); + } _LIT(KDriverName, " d_expio"); + +// Called while loading LDD +TInt DExDriverLogicalDevice::Install() + { + return SetName(&KDriverName); + }

The framework uses driver names to identify the PDDs +that can be used with a given LDD. This can happen in two ways:

    +
  • The framework uses the +name of the PDD factory object passed by the user while creating the logical +channel. This requires a PDD with that name to be already loaded, and its +factory object created. The framework searches for a PDD factory object with +the specified name.

  • +
  • If the user does not +pass the PDD name explicitly, then the framework searches all PDD factory +objects that have a name in the form of x.y, where x is the name of the LDD +factory object.

  • +
+
\ No newline at end of file