korg/bluez
0
0
Fork 0
mirror of https://git.kernel.org/pub/scm/bluetooth/bluez.git synced 2024-12-26 20:33:46 +08:00
Code Issues Packages Projects Releases Wiki Activity
826f869b8b
bluez/tools/hid2hci.1

47 lines
1.3 KiB
Groff
Raw Normal View History

Add hid2hci utility
2004-04-24 19:16:58 +08:00
.\"
.\" This program is free software; you can redistribute it and/or modify
.\" it under the terms of the GNU General Public License as published by
.\" the Free Software Foundation; either version 2 of the License, or
.\" (at your option) any later version.
.\"
.\" This program is distributed in the hope that it will be useful,
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
.\" GNU General Public License for more details.
.\"
.\" You should have received a copy of the GNU General Public License
.\" along with this program; if not, write to the Free Software
.\" Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
.\"
.\"
build: Move all programs to be installed into bin directory
2012-12-09 18:03:46 +08:00
.TH HID2HCI 1 "MAY 15, 2009" "" ""
Add hid2hci utility
2004-04-24 19:16:58 +08:00
.SH NAME
hid2hci \- Bluetooth HID to HCI mode switching utility
.SH SYNOPSIS
.BR "hid2hci
[
.I options
]
.SH DESCRIPTION
.B hid2hci
Add support for command line arguments on hid2hci tool This means that the hid2hci tool will not have to run on every bootup for every machine with BlueZ installed. It instead gets ran on demand if a product that is called out from a udev rules file contains the correct attributes and/or VID/PID. It also makes it easier for users to manually test new VID/PID combinations to determine if they should be supported by BlueZ.
2009-05-16 05:31:42 +08:00
is used to set up switch supported Bluetooth devices into the HCI
Add hid2hci utility
2004-04-24 19:16:58 +08:00
mode and back.
.SH OPTIONS
.TP
Update hid2hci tool from udev codebase
2011-04-28 17:08:47 +08:00
.B --mode= [hid, hci]
Add support for command line arguments on hid2hci tool This means that the hid2hci tool will not have to run on every bootup for every machine with BlueZ installed. It instead gets ran on demand if a product that is called out from a udev rules file contains the correct attributes and/or VID/PID. It also makes it easier for users to manually test new VID/PID combinations to determine if they should be supported by BlueZ.
2009-05-16 05:31:42 +08:00
Sets the mode to switch the device into
Add hid2hci utility
2004-04-24 19:16:58 +08:00
.TP
Update hid2hci tool from udev codebase
2011-04-28 17:08:47 +08:00
.B --method= [csr, logitech-hid, dell]
Which vendor method to use for switching the device.
Add support for command line arguments on hid2hci tool This means that the hid2hci tool will not have to run on every bootup for every machine with BlueZ installed. It instead gets ran on demand if a product that is called out from a udev rules file contains the correct attributes and/or VID/PID. It also makes it easier for users to manually test new VID/PID combinations to determine if they should be supported by BlueZ.
2009-05-16 05:31:42 +08:00
.TP
Update hid2hci tool from udev codebase
2011-04-28 17:08:47 +08:00
.B --devpath=
Specifies the device path in /sys
.TP
.B --help
Gives a list of possible options.
Add support for command line arguments on hid2hci tool This means that the hid2hci tool will not have to run on every bootup for every machine with BlueZ installed. It instead gets ran on demand if a product that is called out from a udev rules file contains the correct attributes and/or VID/PID. It also makes it easier for users to manually test new VID/PID combinations to determine if they should be supported by BlueZ.
2009-05-16 05:31:42 +08:00
.TP
Add hid2hci utility
2004-04-24 19:16:58 +08:00
.SH AUTHOR
Written by Marcel Holtmann <marcel@holtmann.org>.
.br
Reference in New Issue Copy Permalink