Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function is used by OEMs to provide custom calls into the RIL driver. It is an extension mechanism allowing the RIL driver developer to include any needed additional functionality.

Syntax 

HRESULT RIL_DevSpecific(
  HRIL 
hRil,
  const BYTE* 
lpbParams,
  DWORD 
dwSize
);

Parameters

hRil

Handle to the RIL instance returned by RIL_Initialize.

lpbParams

Pointer to a buffer containing any parameters required for the device specific call.

dwSize

Specifies the size of the data, in bytes, pointed to by lpbParams.

Return Value

Positive HRESULTvalues indicate success of the function call and are used as command identifications for matching the asynchronous call result. Zero is not a valid command identification. Negative HRESULTvalues indicate an error. Errors are defined in the winerror.h file and Ril.h file.

An asynchronous result callback of RIL_RESULT_OKindicates success. The lpDatanotification parameter points to a byte array containing the asynchronous result produced by the device specific call. For more information on the result callback, see RILRESULTCALLBACK.

Remarks

If the calling application and the driver agree on the interpretation of the lpbParamsbuffer and the lpDatareturn value, then any additional functionality may be implemented with this mechanism.

The RIL proxy translates the RIL_DevSpecificfunction into IOCTL_RIL_DevSpecificwhen the RIL proxy calls RIL_IOControl.

Requirements

Header ril.h
Library Ril.lib
Windows Embedded CE Windows CE .NET 4.2 and later

See Also