summaryrefslogtreecommitdiffstats
path: root/usr.sbin/bluetooth
Commit message (Collapse)AuthorAgeFilesLines
* MFC r291145:hselasky2015-11-241-2/+2
| | | | | | Fix scancodes for Kana and Eisu keys. PR: 204709
* MFC r289637emax2015-11-051-9/+43
| | | | | | | check boundaries while parsing SDP responses Reported by: hps Reviewed by: hps
* MFC r278360:trasz2015-05-152-4/+4
| | | | | | Make hccontrol(8) and sdpcontrol(8) appear in "man -k bluetooth" output. Sponsored by: The FreeBSD Foundation
* MFC r282054:ngie2015-05-131-4/+9
| | | | | ath3kfw, bcmfw, bthidcontrol, bthidd all require usb(4); build them conditionally if MK_USB != no
* MFC r281146.rakuco2015-04-151-6/+0
| | | | | | | | | | bthidd: Remove unused macros from hid.c. ASIZE() was never used, and min() stopped being used in r207812. Differential Revision: https://reviews.freebsd.org/D2230 Reviewed by: emax Approved by: emax
* MFC r281116.rakuco2015-04-151-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bthidd: Consider usage ranges when dealing with array inputs. So far, we were always using HID_USAGE() to determine the Usage ID of a certain HID report input item. This does not work as intended if a field is an array and the allowed usages are specified with a usage range, as HID_USAGE() will return 0. We need to use the field value as an index in the usage range list in this case instead. This makes the volume keys in a Microsoft Bluetooth Mobile Keyboard 5000 be properly recognized. The relevant part of the HID report looks like this: 0xA1, 0x01, // Collection (Application) 0x85, 0x07, // Report ID (7) 0x05, 0x0C, // Usage Page (Consumer) 0x19, 0x00, // Usage Minimum (Unassigned) 0x2A, 0xFF, 0x03, // Usage Maximum (0x03FF) 0x95, 0x01, // Report Count (1) 0x75, 0x10, // Report Size (16) 0x15, 0x00, // Logical Minimum (0) 0x27, 0xFF, 0x03, 0x00, 0x00, // Logical Maximum (1023) 0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred // State,No Null Position) When a key such as "volume down" is pressed, the following data is transferred through Interrupt In: 0x07 0xEA 0x00 Differential Revision: https://reviews.freebsd.org/D2229
* MFC r275709emax2015-01-071-2/+2
| | | | | | | handle "Kana" and "Eisu" keys on Apple Wireless Keyboard (JIS) PR: 187470 Submitted by: naito.yuichiro
* MFC r258779,r258780,r258787,r258822:eadler2014-02-041-1/+1
| | | | | | | | | | | | | Fix undefined behavior: (1 << 31) is not defined as 1 is an int and this shifts into the sign bit. Instead use (1U << 31) which gets the expected result. Similar to the (1 << 31) case it is not defined to do (2 << 30). This fix is not ideal as it assumes a 32 bit int, but does fix the issue for most cases. A similar change was made in OpenBSD.
* Work around build breakages with GCC 4.2.jkim2013-05-231-0/+2
| | | | Reported by: tinderbox
* Fxi a bunch of typos.eadler2013-05-101-1/+1
| | | | | PR: misc/174625 Submitted by: Jeremy Chadwick <jdc@koitsu.org>
* Add the Clang specific -Wmissing-variable-declarations to WARNS=6.ed2013-04-191-0/+2
| | | | | | | | | | | | | This compiler flag enforces that that people either mark variables static or use an external declarations for the variable, similar to how -Wmissing-prototypes works for functions. Due to the fact that Yacc/Lex generate code that cannot trivially be changed to not warn because of this (lots of yy* variables), add a NO_WMISSING_VARIABLE_DECLARATIONS that can be used to turn off this specific compiler warning. Announced on: toolchain@
* Remove contractions.joel2013-04-111-1/+1
|
* Extend ath3kfw to include overridable device / vendor IDs.adrian2013-04-051-4/+14
| | | | | | | This is required for ar3k series bluetooth devices who need firmware but have a different vendor ID than normal. Reviewed by: maksim
* A number of places in the source tree still reference cuad.* aftereadler2012-12-082-2/+2
| | | | | | | | | | | sio(4) was deprecated by uart(4). s/cuad/cuau/g/ PR: docs/171533 Reviewed by: imp Approved by: cperciva (implicit) MFC after: 3 weeks
* make sure that socket's send and receive buffers are properly sizedemax2012-10-182-1/+45
| | | | | Submitted by: Iain Hibbert plunky at rya-online dot net MFC after: 3 weeks
* mdoc: add missing width argument to Bl -tag.joel2012-06-035-8/+8
|
* Fix world after byacc import:bapt2012-05-222-1/+2
| | | | | | | | - old yacc(1) use to magicially append stdlib.h, while new one don't - new yacc(1) do declare yyparse by itself, fix redundant declaration of 'yyparse' Approved by: des (mentor)
* Remove trailing whitespace per mdoc lint warningeadler2012-03-291-1/+1
| | | | | | | Disussed with: gavin No objection from: doc Approved by: joel MFC after: 3 days
* Fix date.joel2012-03-261-1/+1
|
* Touch up some more small typos missed in the previous round.uqs2012-01-051-1/+1
| | | | Reported by: Ben Kaduk <minimarmot@gmail.com> et al.
* Fix typos in command descriptions.stefanf2011-12-311-2/+2
|
* Spelling fixes for usr.sbin/uqs2011-12-302-2/+2
|
* Reencode files to UTF-8. Drop CP1252 em-dash.uqs2011-12-301-4/+4
|
* In usr.sbin/bluetooth/sdpd/server.c, don't use the size of a pointer asdim2011-12-171-1/+1
| | | | | | the length argument to memset, but the size of the object pointed to. MFC after: 1 week
* Plug fd leakskevlo2011-11-231-0/+1
|
* Remove redundant assignments to WARNS.ed2011-06-061-1/+0
| | | | For these directories, WARNS is already implied to be 6.
* Encode horizontal scroll events (AC Pan) as button presses (bit 5 and 6)emax2011-05-041-0/+11
| | | | | Submitted by: David Demelier demelier dot david at gmail dot com MFC after: 1 week
* Improve the man page and l2control's usage() a bit.emax2011-04-192-13/+22
| | | | | Submitted by: arundel MFC after: 1 week
* Do not use word 'flood' as it not entirely correct. Use better 'no delay'emax2011-03-282-18/+19
| | | | | | | description. While here, replace atoi(3) with strtol(3). Submitted by: arundel MFC after: 1 week
* Don't generate input() since it's not used.brucec2010-11-222-2/+2
|
* Add firmware downloader for Atheros AR3011 based USB Bluetooth devices.emax2010-11-124-0/+375
| | | | | | | Hardware donated by: Rusty Nejdl rnejdl at ringofsaturn dot com Tested by: Rusty Nejdl rnejdl at ringofsaturn dot com Tested by: Andrzej Tobola ato at iem dot pw dot edu dot pl MFC after: 3 weeks
* Make sure to only pickup hid_input items when parsing input reports.emax2010-09-081-1/+2
| | | | | | | | As it turns out, libusbhid(3) also picks up hic_collection items even though we explicitly requested hid_input items only. Tested by: Buganini < buganini at gmail dot com > MFC after: 1 week
* Do not request SDP attributes using ranges.emax2010-09-071-2/+4
| | | | | | | Apparently some devices do not like it. MFC after: 1 week Tested by: Buganini < buganini at gmail dot com >
* mdoc: move remaining sections into consistent orderuqs2010-05-132-9/+9
| | | | | | | This pertains mostly to FILES, HISTORY, EXIT STATUS and AUTHORS sections. Found by: mdocml lint run Reviewed by: ru
* mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to theuqs2010-05-132-25/+25
| | | | | | | | | | | bottom of the manpages and order them consistently. GNU groff doesn't care about the ordering, and doesn't even mention CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put them. Found by: mdocml lint run Reviewed by: ru
* Catch up with libusbhid merge (rev 205728).kaiw2010-05-091-11/+5
| | | | | | | | | | | | | | hid_get_data() now expects that the hid data passed in always contains the report ID byte. Thus we should not skip the the report ID byte in hid_interrupt(). Also, if HUP_KEYBOARD usage is an array, do not try to modify the 'data' pointer, instead, increase the hid_item_t field 'pos' by 'report_size' before calling hid_get_data() during each iteration. PR: usb/146367 Reported and tested by: Alex Deiter Pointy hat to: kaiw Reviewed by: emax
* Remove redundant WARNS?=6 overrides and inherit the WARNS setting fromuqs2010-03-021-1/+0
| | | | | | | | the toplevel directory. This does not change any WARNS level and survives a make universe. Approved by: ed (co-mentor)
* Teach btpand(8) to recognized Bluetooth device node names.emax2009-05-181-1/+1
| | | | | Tested by: Daniel O'Connor <doconnor -at- gsoft -dot- com -dot- au> MFC after: 3 days
* Fix bug in event timeout handlingemax2009-04-171-5/+5
| | | | | Submitted by: mav MFC after: 3 days
* Build fixups for the new USB stack.thompsa2009-02-231-0/+1
|
* Clenup code a bit and do not call fork(2) before dameon(3) where not needed.emax2009-02-043-36/+10
| | | | MFC after: 1 month
* Hook up btpand(8) to the buildemax2009-02-021-0/+1
| | | | MFC after: 1 month
* Fix client mode. Pick up service availability changes.emax2009-02-023-21/+19
| | | | | Obtained from: NetBSD MFC after: 1 month
* Add btpand(8) daemon from NetBSD. This daemon provides support foremax2009-01-3015-0/+3372
| | | | | | | | Bluetooth Network Access Point (NAP), Group Ad-hoc Network (GN) and Personal Area Network User (PANU) profiles. Obtained from: NetBSD MFC after: 1 month
* Straighten out those pesky SDP records for the Bluetoothemax2008-11-251-10/+26
| | | | | | | Service Discovery Application Profile. Discussed with: Iain Hibbert of NetBSD plunky at rya dash online dot net MFC after: 3 weeks
* Add mandatory "security description" SDP parameter to the PANU profileemax2008-03-191-0/+15
| | | | | Pointed-out by: Iain Hibbert < plunky at rya-online dot net > MFC after: 3 days
* Add PSM and Load Factor SDP parameters to the BNEP based profilesemax2008-03-186-15/+110
| | | | | | | | | | | (NAP, GN and PANU). No reason to not to support them. Separate SDP parameters data structures for the BNEP based profiles. Generalize Service Availability SDP parameter creation. Requested by: Iain Hibbert < plunky at rya-online dot net > MFC after: 3 days
* Update usage() - add new -D option. While I'm here, update copyrightemax2008-03-141-2/+5
| | | | | | information and license formatting MFC after: 1 day
* Add support for the NAP, GN and PANU profiles to the sdpd(8).emax2008-03-116-6/+562
| | | | | | | It should be mentioned that a somewhat similar patch was submitted by Rako < rako29 at gmail dot com > MFC after: 1 week
* Add an option to register DUN (Dial-Up Networking) service on the sameemax2008-03-062-3/+43
| | | | | | | RFCOMM channel if needed. There is really no good reason to not to support this. AT-command exchange can be faked with chat script in ppp.conf. MFC after: 1 week
OpenPOWER on IntegriCloud