| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Make hccontrol(8) and sdpcontrol(8) appear in "man -k bluetooth" output.
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
ath3kfw, bcmfw, bthidcontrol, bthidd all require usb(4); build them
conditionally if MK_USB != no
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
handle "Kana" and "Eisu" keys on Apple Wireless Keyboard (JIS)
PR: 187470
Submitted by: naito.yuichiro
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Reported by: tinderbox
|
|
|
|
|
| |
PR: misc/174625
Submitted by: Jeremy Chadwick <jdc@koitsu.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
|
|
|
|
|
|
| |
This is required for ar3k series bluetooth devices who need firmware
but have a different vendor ID than normal.
Reviewed by: maksim
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Submitted by: Iain Hibbert plunky at rya-online dot net
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
|
|
| |
- 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)
|
|
|
|
|
|
|
| |
Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days
|
| |
|
|
|
|
| |
Reported by: Ben Kaduk <minimarmot@gmail.com> et al.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
the length argument to memset, but the size of the object pointed to.
MFC after: 1 week
|
| |
|
|
|
|
| |
For these directories, WARNS is already implied to be 6.
|
|
|
|
|
| |
Submitted by: David Demelier demelier dot david at gmail dot com
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: arundel
MFC after: 1 week
|
|
|
|
|
|
|
| |
description. While here, replace atoi(3) with strtol(3).
Submitted by: arundel
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Apparently some devices do not like it.
MFC after: 1 week
Tested by: Buganini < buganini at gmail dot com >
|
|
|
|
|
|
|
| |
This pertains mostly to FILES, HISTORY, EXIT STATUS and AUTHORS sections.
Found by: mdocml lint run
Reviewed by: ru
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
the toplevel directory.
This does not change any WARNS level and survives a make universe.
Approved by: ed (co-mentor)
|
|
|
|
|
| |
Tested by: Daniel O'Connor <doconnor -at- gsoft -dot- com -dot- au>
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: mav
MFC after: 3 days
|
| |
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
| |
Obtained from: NetBSD
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
Bluetooth Network Access Point (NAP), Group Ad-hoc Network (GN) and
Personal Area Network User (PANU) profiles.
Obtained from: NetBSD
MFC after: 1 month
|
|
|
|
|
|
|
| |
Service Discovery Application Profile.
Discussed with: Iain Hibbert of NetBSD plunky at rya dash online dot net
MFC after: 3 weeks
|
|
|
|
|
| |
Pointed-out by: Iain Hibbert < plunky at rya-online dot net >
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
(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
|
|
|
|
|
|
| |
information and license formatting
MFC after: 1 day
|
|
|
|
|
|
|
| |
It should be mentioned that a somewhat similar patch was
submitted by Rako < rako29 at gmail dot com >
MFC after: 1 week
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Approved by: re (kensmith)
|