| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Recent gcc versions, like 4.3.2 from ubuntu intrepid, give warnings like
"format not a string literal and no format arguments" without this
patch.
|
| |
|
| |
|
|
|
|
|
| |
If the remote end sends a START_CMD while we're setting up the stream
use it to notify the stream requestor (unix.c) of success.
|
|
|
|
|
|
|
| |
This could happen if both peers send START_CMD at the same time and the
SNK peer doesn't reject the command (as it should according to the
spec). This behaviour can be seen e.g. when using pulseaudio and the
Mororola S9 headset.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some time back the INT role OPEN transition was moved from receiving the OPEN
response to actually having the stream L2CAP channel ready. Unfortunatly this
patch forgot to change the ACP case so the code has so far attempted a double
->OPEN transition. According to the AVDTP spec the transition should happen
before the stream L2CAP transport but this doesn't really make sense since
several places want to have the stream fd ready when we go to the OPEN state.
Therefore, this patch removes the ACP role OPEN transition from receiving the
OPEN command and lets the state change be in having the stream L2CAP transport
established.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This error code doesn't appear in the CME error table in the HFP spec but there
are references to it in a couple of other places in the spec.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The name won't be there until we connect otherwise
|
|
|
|
|
|
|
| |
Remove out-dated code to parse the HID input descriptor
Make sure that all the Bluetooth addresses used are upper-case
Add captured once SDP PNP record for the sixaxis controller
Store device id, profile, and trust information about the device
|
|
|
|
|
|
| |
Direction for the USB command was wrong, also disable
all the report code, so sixpair can run (minus saving device
records)
|
|
|
|
|
|
| |
Export record_from_string() from the storage functions,
so it can be used to generate an sdp_record from a
static string in sixpair.c
|
|
|
|
|
| |
Port sixpair to libusb-1.0, as it allows us to re-attach
the driver to the device after we're done.
|
|
|
|
|
| |
Sixpair is an unfinished helper to automatically pair a
plugged in Playstation 3 Sixaxis Bluetooth joypad.
|
|
|
|
|
|
| |
As per https://bugzilla.redhat.com/show_bug.cgi?id=246840
and the udev release notes, update the udev rules for newer
versions of udev (>= 098).
|
| |
|
|
|
|
| |
The previous error message was a bit terse.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Fix byte-reading in the decode function by using a guint8, instead
of an int, we were overreading and were getting keycodes of
0xffffff44 when we wanted a single byte of 0x44.
- Remove use of KEY_REMOTE_X, those keys never got upstream, and the
values they were defined at are now used for completely different
keys
- Update uinput.h with the latest keycodes from 2.6.27
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
0 0x0000000000a5cf71 in sdp_data_get (rec=0x0, attrId=0) at sdp.c:1444
1 0x000000008c704721 in hid_device_probe (device=0x7f1bed2a80b0, uuids=0x7f1bed29fa90) at manager.c:70
2 0x00007f1becb5bc33 in device_probe_drivers (device=0x7f1bed2a80b0, uuids=0x7f1bed2a2980) at device.c:647
3 0x00007f1becb58a23 in create_stored_device_from_profiles (key=0x7f1bed2a7360 "00:1E:45:AD:F1:96",
value=0x7f1bed2a7aa0 "00000002-0000-1000-8000-0002ee000002 00001101-0000-1000-8000-00805f9b34fb 00001103-0000-1000-8000-00805f9b34fb 00001104-0000-1000-8000-00805f9b34fb 00001105-0000-1000-8000-00805f9b34fb 00001106-0000-1"..., user_data=0x7f1bed29edd0) at adapter.c:2296
4 0x00007f1becb61d12 in textfile_foreach (pathname=0x7ffff4b6f2a0 "/var/lib/bluetooth/00:13:EF:F1:42:B7/profiles", func=0x7f1becb58955 <create_stored_device_from_profiles>, data=0x7f1bed29edd0) at textfile.c:447
5 0x00007f1becb58b36 in load_devices (adapter=0x7f1bed29edd0) at adapter.c:2327
6 0x00007f1becb58fa0 in adapter_up (adapter=0x7f1bed29edd0, dd=18) at adapter.c:2462
7 0x00007f1becb59479 in adapter_start (adapter=0x7f1bed29edd0) at adapter.c:2569
8 0x00007f1becb5427f in manager_start_adapter (id=0) at manager.c:424
9 0x00007f1becb48e02 in device_devup_setup (dev_id=0) at main.c:481
10 0x00007f1becb48f35 in init_all_devices (ctl=7) at main.c:512
11 0x00007f1becb496d0 in main (argc=1, argv=0x7ffff4b70788) at main.c:748
The HID device's SDP record can be NULL, so don't crash when that happens
|
| |
|
|
|
|
|
|
|
|
| |
There's something broken in the "profile enabled" logic at the moment which
makes server_is_enabled return FALSE sometimes when it shouldn't which causes
the necessary interface not to be added to remote device objects. Use simply
the config file values for now since we don't support per-adapter server
configuration anyway.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Previously the avctp session would be free'd and the connect callback would try
to access this free'd memory. Now we detect this situation properly but the
fundamental problem remains that the bt_l2cap_connect API doesn't allow
aborting the connect procedure.
|