IOCTL_NFP_GET_KILO_BYTES_PER_SECOND - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers
// nfpdev.h

// CTL_CODE(0x0051, 0x021, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define IOCTL_NFP_GET_KILO_BYTES_PER_SECOND 0x00510084
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Windows Driver Kit DDI reference (ni-nfpdev-ioctl_nfp_get_kilo_bytes_per_second)

IOCTL_NFP_GET_KILO_BYTES_PER_SECOND IOCTL

Description

A client sends the IOCTL_NFP_GET_KILO_BYTES_PER_SECOND request to any generic handle, one that is non-published and non-subscribed, to the provider device. The request is sent in order to determine the approximate best-case transmission speed supported by the provider or its underlying RF technology. This is used to distinguish the difference in one order of magnitude in transmission rate to another.

Note A typical NFC implementation should provide a value of approximately 50.

Parameters

Major code

Input buffer

None

Input buffer length

Output buffer

One INT32 value that defines the approximate transmission speed supported by the provider or its underlying technology.

Output buffer length

Input/output buffer

Input/output buffer length

Status block

Irp->IoStatus.Status is set to STATUS_SUCCESS if the request is successful.

Otherwise, Status to the appropriate error condition as a NTSTATUS code.

For more information, see NTSTATUS Values.

Remarks

Each provider implementation can specify an approximate transmission rate. A typical NFC implementation should provide a value of around 50 KB per second.

The following are required actions when using this IOCTL:

See also

Near field communication (NFC) overall design guide

Near field proximity design guide (Tap and Do, NFP provider model, driver requirements)