destructor

This method allows a client to obtain the command complete event data when being notified of a CommandComplete. That is it can be called as part of his implementation of "CommandCompleted" in his MVendorSpecificHciConduit derived class.

NOTE: If no event data is returned from the stack, as is the case if IssueCommandL was called, *** this will return the original command data! ***

MVendorSpecificHciConduit

2nd phase construction

Implements cancellation of an outstanding request.

This function is called as part of the active object's Cancel() .

It must call the appropriate cancel function offered by the active object's asynchronous service provider. The asynchronous service provider's cancel is expected to act immediately.

DoCancel() must not wait for event completion; this is handled by Cancel() .

CActive::Cancel

Issues a vendor specific command to the hardware. This command should have an associated command complete event.

The client need not be concerned with the exact formatting of the HCI frame as the HCI only requires the opcode and the correctly fomatted parameters in order to construct the appropriate the vendor debug frame. Note that the caller need NOT to be concerned with the HCTL framing at all. The HCI will only then copy this frame to the Host Controller after putting it in an HCTL frame. This command will not be completed until the hardware responds with the command complete event. Note: a command complete event is NOT a vendor debug event.

Warning: If this command is used after the command IssueRequestL has been called, the associated callback, MVendorSpecificHciConduit::CommandCompleted , could receive the wrong CommandCompleteEvent data.

MVendorSpecificHciConduit::CommandCompleted

Issues a vendor specific command to the hardware.

The client need not be concerned with the exact formatting of the HCI frame as the HCI only requires the opcode and the correctly fomatted parameters in order to construct the appropriate the vendor debug frame. Note that the caller need NOT to be concerned with the HCTL framing at all. The HCI will only then copy this frame to the Host Controller after putting it in an HCTL frame. This command will be completed when the Bluetooth stack receives it. This API should not be used if the caller wants to receive any data from an associated command complete event.

Note: a command complete event is NOT a vendor debug event.

two phase constructor to create an HCI Conduit. Note that access to an HCI Conduit from a thread other than that which creates the conduit is not supported

Handles an active object's request completion event.

A derived class must provide an implementation to handle the completed request. If appropriate, it may issue another request.

The function is called by the active scheduler when a request completion event occurs, i.e. after the active scheduler's WaitForAnyRequest() function completes.

Before calling this active object's RunL() function, the active scheduler has:

1. decided that this is the highest priority active object with a completed request

2. marked this active object's request as complete (i.e. the request is no longer outstanding)

RunL() runs under a trap harness in the active scheduler. If it leaves, then the active scheduler calls RunError() to handle the leave.

Note that once the active scheduler's Start() function has been called, all user code is run under one of the program's active object's RunL() or RunError() functions.

CActiveScheduler::Start CActiveScheduler::Error CActiveScheduler::WaitForAnyRequest TRAPD

Instructs the conduit that no more vendor debug events are expected back from the hardware. The conduit will issue no more upcalls on the MVendorSpecificHciConduit derived object passed into the CHciExtensionConduit factory function.

Instructs the conduit that vendor debug events are expected back from the hardware. The conduit will listen for events, and on reception of one will issue an upcall on the MVendorSpecificHciConduit derived object passed into the CHciExtensionConduit factory function.