Symbian3/SDK/Source/GUID-57A909F3-EAEA-5FE2-B620-E21204794497.dita
changeset 2 ebc84c812384
parent 0 89d6a7a84779
equal deleted inserted replaced
1:25a17d01db0c 2:ebc84c812384
    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
    12 <task id="GUID-57A909F3-EAEA-5FE2-B620-E21204794497" xml:lang="en"><title>How
    12 <task id="GUID-57A909F3-EAEA-5FE2-B620-E21204794497" xml:lang="en"><title>How
    13 to Load the Physical Device Driver and Logical Device Driver: Tutorial</title><shortdesc>When testing using the console, all drivers need to be loaded directly.
    13 to Load the Physical Device Driver and Logical Device Driver: Tutorial</title><shortdesc>When testing using the console, all drivers need to be loaded directly.
    14 This tutorial describes how to load the drivers required for the Serial Communications
    14 This tutorial describes how to load the drivers required for the Serial Communications
    15 Server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
    15 Server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
    16 <context><p>Testing of communications software can be done using the Symbian
    16 <context id="GUID-3FD29C37-082A-4B68-A955-E4B0D625BA92"><p>Testing of communications software can be done using the Symbian platform
    17 OS console shell interface rather than a GUI interface. The console shell
    17 console shell interface rather than a GUI interface. The console shell interface
    18 interface has advantages when testing since the console allows software to
    18 has advantages when testing since the console allows software to be tested
    19 be tested in isolation. When testing with a GUI interface the testing can
    19 in isolation. When testing with a GUI interface the testing can be difficult
    20 be difficult if other software in the GUI is attempting to access resources.
    20 if other software in the GUI is attempting to access resources. If the device
    21 If the device or the emulator is started with just the console, then only
    21 or the emulator is started with just the console, then only the kernel and
    22 the kernel and file system are running. The tester can then load the software
    22 file system are running. The tester can then load the software required for
    23 required for the test and ensure that no other software is using any resources.
    23 the test and ensure that no other software is using any resources. This avoids
    24 This avoids problems of other software interrupting the CPU or using and releasing
    24 problems of other software interrupting the CPU or using and releasing memory
    25 memory or other hardware while a test is running. </p><p>Any test applications
    25 or other hardware while a test is running. </p><p>Any test applications that
    26 that have not been launched by the GUI should
    26 have not been launched by the GUI should  explicitly load the correct physical
    27  explicitly load the correct physical and logical device drivers. In most
    27 and logical device drivers. In most cases the bootloader will load the physical
    28 cases the bootloader will load the physical device driver. It is safe to load
    28 device driver. It is safe to load a device driver which has already been loaded,
    29 a
    29 since the API will return <xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
    30 device driver which has already been loaded, since the API will return
       
    31 <xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
       
    32 <steps id="GUID-8D0D239F-51F9-512A-8405-ADD01AE1660B">
    30 <steps id="GUID-8D0D239F-51F9-512A-8405-ADD01AE1660B">
    33 <step id="GUID-21876E62-D2A9-510A-BAD2-CB3E4271A02B"><cmd>Identify the names
    31 <step id="GUID-21876E62-D2A9-510A-BAD2-CB3E4271A02B"><cmd>Identify the names
    34 of the physical and logical device drivers required.</cmd>
    32 of the physical and logical device drivers required.</cmd>
    35 <info><p> The names of device drivers change since variations are created
    33 <info><p> The names of device drivers change since variations are created
    36 for different platforms: the ecuart and infra-red logical device driver is
    34 for different platforms: the ecuart and infra-red logical device driver is