User's Manual

Datalogic Scanning, Inc
959 Terry Street
Eugene, Oregon 97402
Page 42 10/23/2009
Revision X2
The configuration uses a structure of type HOSTIO_FC_PS_BLOCK in which the only field currently used
is:
bool allow_sco_fc - if TRUE then the chip will allow SCO
over HCI flow control to be turned on, else it
will be refused.
The remaining fields are redundant:
uint16 ncp_max_period - the default milliseconds between
sending NCP (hci number of completed packets)
events to the host.
uint16 acl_trip_level - the number of ACL packets required
to cause an extra NCP event to be sent to the
host.
uint16 sco_trip_level - the number of SCO packets required
to cause an extra NCP event to be sent to the
host.
(Type bool is fundamentally a uint16 with values 0 and 1 mapping to FALSE and TRUE.)
Key Name Key
Number
Type Default Setting
PSKEY_HOSTIO_PROTOCOL_INFO0 0x0194 PROTOCOL_INFO 0, FALSE, 0, FALSE
Configure the protocol that flows over BCSP channel 0.
The host transport subsystem provides 16 channels, each of which is configured by a PROTOCOL_INFO
struct held in the ps; the structure is described below.
BCSP channel 0 is dedicated to signalling between BCSP stacks - it carries message acknowledgements -
so it is not available as a channel to carry user messages through BCSP. I.e., the information on the
PROTOCOL_INFO structure is useless for channel 0, but other channels use the same structure and their
descriptions refer here. Channel 0 is used by the BCSP host transport only.
CSR document CS-101680-SP (previously numbered as bcore-sp-007p) describes the allocation of BCSP's
channels.
The type PROTOCOL_INFO has the following fields:
uint16 max_tx_payload_size - The maximum size in bytes of
BCSP payload sent to the host. For ACL and SCO the
actual maximum size will be the lower of the value
from PS and the value indicated to BlueCore in the
host's HOST_BUFFER_SIZE command, if one has been
received. In addition, at runtime, we check these
values against the size of hardware buffer
allocated.