-->

This section describes the class-of-device (CoD) registry subkeys and entries that apply to the Bluetooth driver stack.

'COD Major' and 'COD Type' Values

Original equipment manufacturer (OEMs) can use the COD Major and COD Type values to indicate the Class of Device for a Bluetooth-enabled Windows device. After the Bluetooth class installer sets the Class of Device based on these registry values, a remote device can determine whether it is connecting to a portable computer, a desktop computer, a phone, and so on.

For a listing of video card drivers, see our video card drivers page. Other PCI device that Windows cannot identify. If you tried the above two steps and your Windows Device Manager still contains an Unknown PCI device, likely the device cannot be identified. A library of over 250,000 device drivers, firmware, BIOS and utilities for Windows.

The registry path to the COD Major and COD Type values is:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBTHPORTParameters

Note that setting these values changes the Bluetooth Class of Device for the system, regardless of which Bluetooth radio may be attached. You can set the COD Major and COD Type to DWORD values as defined for the Class of Device field values in the Bluetooth SIG Assigned Numbers.

The Bluetooth profile driver, BthPort.sys, reads the COD Major and COD Type values to determine how it should respond to a device inquiry. These values affect only the COD_MAJOR_XXX and COD_XXX_MINOR_XXX bits of the Class of Device. The COD_SERVICE_XXX bits are not affected by this registry entry.

If the COD Major and COD Type values are not set or are set to invalid values, the Bluetooth class installer will set these values to COD_MAJOR_COMPUTER and COD_COMPUTER_MINOR_DESKTOP, respectively.

Scanning Parameterization Settings

Profile drivers can specify scanning parameters settings for their device(s) in their profile driver's INF file to tailor to the specific needs of a given device scenario.

You can override the default system scanning parameters by providing one or more of the following scanning parameters listed below into the AddReg directive. More information on how to use this directive can be found in INF AddReg Directive.

Value Name	Type	Min Value	Max Value
HighDutyCycleScanWindow	DWORD 0x10001	0x0004	0x4000. Shall be equal or smaller than the HighDutyCycleScanInterval parameter
HighDutyCycleScanInterval	DWORD 0x10001	0x0004	0x4000
LowDutyCycleScanWindow	DWORD 0x10001	0x0004	0x4000. Shall be smaller than the LowDutyCycleScanInterval parameter
LowDutyCycleScanInterval	DWORD 0x10001	0x0004	0x4000
LinkSupervisionTimeout	DWORD 0x10001	0x000A	0x0C80
ConnectionLatency	DWORD 0x10001	0x0000	0x01F4
ConnectionIntervalMin	DWORD 0x10001	0x0006	0x0C80. Shall be smaller or equal to ConnectionIntervalMax
ConnectionIntervalMax	DWORD 0x10001	0x0006	0x0C80

Note

Changes to scanning parameters make a global impact on the performance of the Bluetooth stack. Making changes to scanning parameters programmatically is not permitted. Using Low Duty Cycle scanning parameters that are too aggressive can not only have a negative impact to the available bandwidth for other Bluetooth Low Energy connections, but also for Bluetooth BR/EDR connections.

Sun Dual 10GbE XFP PCIe ExpressModule User’s Guide

C H A P T E R 5

Configuring the nxge Device Driver Parameters

The nxge device driver controls the Sun Dual 10GbE interfaces. You can manually set the nxge driver parameters to customize each device in your system.

This chapter lists the available device driver parameters and describes how you can set these parameters.

`nxge` Hardware and Software Overview

The Sun Dual 10GbE XFP PCIe ExpressModule provides two 10-Gigabit full-duplex networking interfaces. The device driver automatically sets the link speed to 10000 Mbit/sec and conforms to the IEEE 802.3 Ethernet standard. Each interface has 8 receive DMA channels and 12 transmit DMA channels to enable parallel processing of the packets.

The Sun Dual 10GbE XFP PCIe ExpressModule extends CPU and OS parallelism to networking with its support for hardware-based flow classification and multiple DMAs. Using CPU thread affinity to bind a given flow to a specific CPU thread, the EM enables a one-to-one correlation of Rx and Tx packets across the same TCP connection. This functionality can help avoid cross-calls and context switching to deliver greater performance while reducing the need for CPU resources to support I/O processing. The Sun 10-Gigabit Ethernet EM uses the Sun MAC controller to map the 10-Gigabit XAUI interface onto the PCI Express form factor. The EM supports 10 Gbit/sec bandwidth using eight transmit and eight receive lanes.

Setting `nxge` Driver Parameters on a Solaris Platform

You can set the nxge device driver parameters in two ways:

Using the ndd utility
Using the nxge.conf file

If you use the ndd utility, the parameters are valid only until you reboot the system. This method is good for testing parameter settings.

To set parameters so they remain in effect after you reboot the system, create a
/platform/sun4u/kernel/drv/nxge.conf file and add parameter values to this file when you need to set a particular parameter for a device in the system.

Setting Parameters Using the `ndd` Utility

Use the ndd utility to configure parameters that are valid until you reboot the system.

The following sections describe how you can use the nxge driver and the ndd utility to modify (with the -set option) or display (without the -set option) the parameters for each nxge device.

Noninteractive and Interactive Modes

You can use the ndd utility in two modes:

Noninteractive
Interactive

In Noninteractive mode, you invoke the utility to execute a specific command. Once the command is executed, you exit the utility. In Interactive mode, you can use the utility to get or set more than one parameter value. Refer to the ndd(1M) man page for more information.

To Specify Device Instances for the ndd Utility

Before you use the ndd utility to get or set a parameter for an nxge device, you must specify the device instance for the utility.

Check the /etc/path_to_inst file to identify the instance associated with a particular device.

To Specify Parameter Values Using the ndd Utility

This procedure describes how to modify and display parameter values.

1. Modify a parameter value, using the -set option.

If you invoke the ndd utility with the -set option, the utility passes value, which must be specified, down to the named /dev/nxgedriver-instance, and assigns the value to the parameter:

where number is the driver instance, for example /dev/nxge0, /dev/nxge1.

2. Display the value of a

'COD Major' and 'COD Type' Values

Scanning Parameterization Settings

nxge Hardware and Software Overview

Setting nxge Driver Parameters on a Solaris Platform

Setting Parameters Using the ndd Utility

Noninteractive and Interactive Modes

`nxge` Hardware and Software Overview

Setting `nxge` Driver Parameters on a Solaris Platform

Setting Parameters Using the `ndd` Utility

NDD Port Devices Driver