summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add ofono as telephony providerbaserock/ct143/masterBen Brewer2012-12-131-1/+1
|
* Enable alsa supportBen Brewer2012-12-131-1/+1
|
* Fix path error in morphBen Brewer2012-12-131-1/+1
|
* Correctly use $DESTDIR in service installBen Brewer2012-12-131-2/+2
|
* Install bluetooth in systemd tooBen Brewer2012-12-131-0/+5
|
* Removed bluez.conf since bluetooth.conf now correctly installsBen Brewer2012-12-131-14/+0
|
* Fixed syntax error in bluez.morphBen Brewer2012-12-131-1/+1
|
* Set paths correctly for installBen Brewer2012-12-131-9/+1
|
* Made bluez.morph create the relevant /etc subdirectory for bluez.conf.Ben Brewer2012-12-131-1/+1
|
* Added bluez.conf to morph file.Ben Brewer2012-12-132-1/+16
|
* Install several bluetooth test utilitiesJannis Pohlmann2012-12-131-0/+7
|
* Add morphology to build/install test programs and toolsJannis Pohlmann2012-12-131-0/+10
|
* Release 4.1014.101Marcel Holtmann2012-06-222-1/+9
|
* build: fix MISC_LDFLAGS typo to fix "--enable-pie"Stefan Seyfried2012-06-211-1/+1
|
* adapter: Change not-connected authorization error to a warningJohan Hedberg2012-06-191-1/+1
| | | | | | | | | Due to scheduling/timing on some kernels it is possible that the device connected event through mgmt comes slightly after an L2CAP socket receives the same event. We should try to fix this on the kernel side but as this check in user space is not protecting against critical errors but just potential profile bugs it can be changed to a simple warning message.
* gdbus: add macro for methods marked as NOREPLYLucas De Marchi2012-06-181-0/+7
|
* simple-agent: Fix input with python version < 3.0Johan Hedberg2012-06-181-5/+11
| | | | | | input() in python < 3.0 is the same as eval(raw_input()) which is not what we want. With python >= 3.0 in turn raw_input doesn't exist. This patch fixes support for both versions by a simple try-except clause.
* AVDTP: Fix rejecting AVDTP Start if starting flag is setLuiz Augusto von Dentz2012-06-181-3/+2
| | | | This is now handled by checking if the command collided.
* audio: Fix aborting A2DP setup while AVDTP Start is in progressLuiz Augusto von Dentz2012-06-152-3/+3
| | | | | Change return of avdtp_start to -EINPROGRESS so the caller can check if the operation is in progress and don't abort because of that.
* AVDTP: Fix responding to ABORT with rejectLuiz Augusto von Dentz2012-06-153-13/+7
| | | | ABORT command cannot be rejected
* AVDTP: Do not respond ABORT command with invalid idLuiz Augusto von Dentz2012-06-151-4/+2
| | | | | | | AVDTP spec, 8.15.2 Abort Response: "If an AVDTP_ABORT_CMD contains an invalid SEID, no response shall be sent."
* audio: Wait remote side to send AVDTP_START when acting as acceptorLuiz Augusto von Dentz2012-06-151-1/+17
| | | | | | | | | | | | | Some devices like Sony Ericsson MW600 reject AVDTP_START if it was the initiator of the connection, apparently it follows recommendation 12 of simultaneous use of HFP, A2DP and AVRCP profiles white paper which says: "If the RD has configured and opened a stream it is also responsible to start the streaming via GAVDP_START." If the client is fast enough and try to acquire the transport this cause an error, so instead of sending AVDTP_START the code now checks if it is the acceptor of the stream and wait the remote side to send the command.
* audio: Fix handling of A2DP abort indicationLuiz Augusto von Dentz2012-06-151-0/+9
| | | | When an abort is received all setup callbacks should return an error.
* audio: Fix handling of A2DP start indicationLuiz Augusto von Dentz2012-06-151-4/+12
| | | | | Only process callbacks if avdtp_start was sent, otherwise it may cancel setup callbacks that were registere via g_idle_add.
* audio: Fix handling of A2DP open indicationLuiz Augusto von Dentz2012-06-151-0/+11
| | | | | When accepting the open indication all config callbacks should be notified that open completed.
* audio: Fix handling of A2DP suspend indicationLuiz Augusto von Dentz2012-06-151-5/+33
| | | | | | | | When accepting the suspend indication all callbacks should be notified that suspend completed. In addition to this fix not using avdtp_start return in indication callback as well as in the confirmation.
* audio: Add handling of AVDTP command collisionLuiz Augusto von Dentz2012-06-151-0/+80
| | | | | | Check collision for AVDTP Open, Close, Start, Suspend and Abort commands and if they collided remove the pending request if SEP has accepted the indication.
* Fix ALSA plugin having full sonameBastien Nocera2012-06-151-1/+1
| | | | | This is a plugin, so spell -avoid-version correctly so it doesn't have a full soname.
* Update tests to be compatible with gi and python3Steve Langasek2012-06-1524-294/+342
| | | | | | | | | This patch makes the python tests source-compatible with python 3, while leaving the interpreter at python 2 for now. The tradeoff is that this source is no longer compatible with python versions < 2.6, and requires gobject-introspection for the glib-based tests.
* Remove test/apitestJohan Hedberg2012-06-152-449/+1
| | | | This script is back from BlueZ 3.x times and unusable now
* Add org.bluez.service to the tarballBastien Nocera2012-06-151-1/+1
| | | | Seeing as we want to install it.
* Release 4.1004.100Marcel Holtmann2012-06-132-1/+27
|
* Update library versionMarcel Holtmann2012-06-131-1/+1
|
* mgmtops: Clear pending_cod_change when powering offJohan Hedberg2012-06-131-0/+1
|
* mgmtops: Move error message after command status handlers callsSzymon Janc2012-06-131-5/+7
| | | | | Don't print error message for actions that are expected or recoverable i.e. add_uuid returning EBUSY status.
* mgmtops: Handle EBUSY status from MGMT_OP_ADD_UUID commandsSzymon Janc2012-06-131-9/+50
| | | | | | MGMT_OP_ADD_UUID may fail with EBUSY due to ongoing CoD update. In case of EBUSY error wait for Class Of Device changed event before adding more UUIDs.
* audio: Separate profile specific fields from media_transportLuiz Augusto von Dentz2012-06-121-34/+82
|
* gattrib: Make event callback identifiers globally uniqueJohan Hedberg2012-06-081-2/+2
| | | | | | The attrib server code relies on these id's to be unique globally and not just per GAttrib instance. As an easy fix make them global by adding a static guint to g_attrib_register.
* btmgmt: Fix use after free in mgmt_check_pendingSzymon Janc2012-06-071-0/+1
| | | | Break loop when pending command was found and callback called.
* gattrib: Fix protection of GAttrib while calling callbacksJohan Hedberg2012-06-071-0/+4
| | | | | | The callbacks could result with the reference count dropping to 0 and the object being freed. This patch fixes the issue by adding one extra reference for the duration of the timeout function.
* mgmtops: Fix handling of cmd_status(0)Johan Hedberg2012-06-071-0/+6
|
* Remove workaround in gatt_connectAndre Guedes2012-06-071-13/+0
| | | | | This workaround is not necessary anymore since setsockopt is now checking for minimum MTU.
* Fix gatt_connect for BR/EDRAndre Guedes2012-06-071-1/+1
| | | | | | Use BT_IO_OPT_IMTU instead of BT_IO_OPT_OMTU in bt_io_connect. We cannot control omtu value since it is negotiated during L2CAP configuration phase.
* Remove omtu parameter from LE bt_io_connect callsAndre Guedes2012-06-071-1/+0
| | | | | There is no need to set the omtu of L2CAP ATT fixed channel. We use the default value.
* attrib-server: Update GAttrib buffer after Exchange MTUAndre Guedes2012-06-071-0/+1
| | | | We should update the GAttrib buffer length after exchanging ATT_MTU.
* attrib-server: Fix mtu_exchangeAndre Guedes2012-06-071-7/+16
| | | | | | | | | | | | | | | | If the client requests an ATT_MTU less than the minimum ATT_MTU, the server should send an Error Response message with Request Not Supported code. According to GATT spec, the server shall respond to Exchange MTU Requests messages with an Exchange MTU Response with the Server Rx MTU parameter set to the maximum MTU that this server can receive. Thus, we should get L2CAP imtu value in order to properly send the Exchange MTU Response message. Additionally, we should not change the L2CAP ATT fixed channel MTU. bt_io_set call will always fail since we are not supposed to change L2CAP MTU after connection is established.
* attrib-server: Fix gatt_channel MTU valueAndre Guedes2012-06-071-7/+7
| | | | | | | | In attrib_channel_attach, channel->mtu should be initialized according to ATT_MTU value. Over BR/EDR, ATT_MTU should be set to the L2CAP imtu negotiated during L2CAP configuration phase. Over LE, ATT_MTU should be 23 octets.
* gattrib: Fix g_attrib_set_mtuAndre Guedes2012-06-071-8/+0
| | | | | | | | | | | 23 octets is the default (and minimum) ATT_MTU value. If someone tries to set ATT_MTU less than 23 octets g_attrib_set_mtu should fail (return FALSE). Additionally, there is no constraint regarding the maximum value of ATT_MTU, so we should not check for it. Also, we should not change the L2CAP ATT fixed channel MTU. bt_io_set call will always fail since we are not supposed to change L2CAP MTU after connection is established.
* gattrib: Fix GAttrib buffer allocationAndre Guedes2012-06-071-12/+20
| | | | | | GAttrib buffer should be allocated according to ATT_MTU value. Over BR/EDR, ATT_MTU should be set to the L2CAP imtu negotiated during L2CAP configuration phase. Over LE, ATT_MTU should be 23 octets.
* gattrib: Fix a premature response timer removalIdo Yariv2012-06-071-5/+5
| | | | | | | | | | A timer is set when a response is expected. The timer is removed when data is received, regardless of whether or not the data is a response. As a result, the timer may be cleared even though a response was not received and there would be no way to detect a command timeout. Fix this by clearing the timer only after verifying a response was received.
View Lorry Controller Status