summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2014-11-25Add packaging directoryHEADtizen_4.0.m1_releasetizen_3.0_ivi_releasetizen_3.0.m2.a1_tv_releasetizen_3.0.m2.a1_mobile_releasetizen_3.0.m1_tv_releasetizen_3.0.m1_mobile_releasesubmit/tizen_unified/20170313.040938submit/tizen_ivi/20160217.000006submit/tizen_ivi/20160217.000000submit/tizen_3.0_common/20161104.104000submit/tizen/20141128.010817submit/tizen/20141126.073427accepted/tizen/unified/20170313.043903accepted/tizen/mobile/20141201.102132accepted/tizen/ivi/20160218.025302accepted/tizen/ivi/20141208.013047accepted/tizen/common/20141128.095251accepted/tizen/3.0/common/20161114.111336tizen_3.0_ivitizen_3.0.m2tizen_3.0.m1_tvtizen_3.0.m1_mobiletizen_3.0.2015.q2_commontizen_3.0.2015.q1_commontizen_3.0.2014.q4_commontizen_3.0tizenaccepted/tizen_wearableaccepted/tizen_unifiedaccepted/tizen_tvaccepted/tizen_mobileaccepted/tizen_iviaccepted/tizen_commonaccepted/tizen_3.0_iviaccepted/tizen_3.0_commonArron Wang5-1/+149
Change-Id: I5704e7f54c2162b644eaa12aa508d4bf127145eb
2014-11-25ndef: Add support for WiFi Handover through MIME/x-nfctlSamuel Ortiz4-1/+146
The NFC task launcher Android application reads NFC tags formatted with a proprietary MIME/x-nfctl NDEF containing an SSID and a passphrase. By pushing the same kind of NDEF through SNEP, a WiFi association with the neard WiFi handover agent can be triggered. Change-Id: I49f13dc3b32b347357c6d2a13f6b3a132ad74dab Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>
2014-11-25Add raw NDEF support for P2PArron Wang2-2/+37
Change-Id: I7ab5cd5eea7b0e60b9980f15a7ba15def86ced0e
2014-11-25tag: Implement a raw NDEF accessorArron Wang3-2/+38
Change-Id: Id7fab24395d45502e8cdde573c40f2bd99348e27
2014-11-25ndef: Support RAW ndef writesSamuel Ortiz3-0/+76
Change-Id: I21a341b2482556458e381b4a3033ef3e9313194c
2013-12-10Release 0.14upstream/0.140.14Samuel Ortiz2-1/+12
2013-12-07AUTHORS: Mention Timo's contributionsSamuel Ortiz1-0/+1
2013-12-07test: Add handover support with BlueZ 5Timo Mueller1-2/+57
Bluetooth pairing information is removed before any handover requests are sent to a remote device. This adds support to allow pairing information removal with BlueZ 5. The information about the default adapter is no longer publicly available with BlueZ 5. The user can therefore select the bluetooth adapter whose paired devices are removed. If no adapter is specified the first adapter is used.
2013-12-07test: Move paired device removal to separate methodTimo Mueller1-9/+14
To prepare the test script for the integration with BlueZ5 the code specific to BlueZ has been refactored into a separate method.
2013-11-25netlink: Check for netlink message sender PIDSamuel Ortiz1-0/+7
If PID is not 0 (i.e. this is not the kernel sending us the message), the message is skipped. Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-25phdc: Check for the sender identity before registering the agentSamuel Ortiz1-2/+16
In order to avoid DoS type of errors by only allowing the registrer to unregister. Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-25nfctype1: Check for remaining space before memcpy'ing meta dataSamuel Ortiz1-0/+5
Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-25nfctype1: Check for remaining space before memcpy'ing dataSamuel Ortiz1-0/+5
Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-25test: Display device properties from the list commandSamuel Ortiz1-0/+5
2013-11-25device: Implement Adapter propertySamuel Ortiz2-3/+33
In order to not only rely on a specific naming scheme, the device Adapter path is now exported as a property.
2013-11-25test: Display tag properties from the list commandSamuel Ortiz1-0/+13
2013-11-25tag: Implement Adapter propertySamuel Ortiz2-2/+28
In order to not only rely on a specific naming scheme, the tag Adapter path is now exported as a property.
2013-11-21main: Call agent_init firstSamuel Ortiz1-2/+2
agent_init will register the /org/neard name and if an adapter is registered before /org/neard is registered, its parent will be "/". That happens when starting neard with an adapter already plugged in.
2013-11-21adapter: Remove near_adapter_listSamuel Ortiz2-20/+0
This routine is no longer called.
2013-11-20nfctool: Fix snep-decode potential overflowSamuel Ortiz1-0/+4
Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-20nfctool: Fix llcp-decode potential overflowSamuel Ortiz1-2/+2
Code review done by Sebastian Krahmer <krahmer@suse.de>.
2013-11-20adapter: Make the power cycle upon driver error configurableSamuel Ortiz4-6/+26
The default behaviour is to power cycle the adapter when receiving a driver error.
2013-11-18adapter: Catch polling errorsSamuel Ortiz3-2/+59
Receiving a NFC_EVENT_TARGETS_FOUND with a NULL payload means the driver entered an error state. This is handled by checking if the devices and targets arrays are empty from the GET_TARGET finish handler. In the polling error case, neard resets the adapter and starts polling again. The polling error handler runs asynchrounously for the D-Bus properties toggle to be exported properly.
2013-11-18netlink: Expose NL_CB_FINISH handlerSamuel Ortiz1-5/+27
In some cases (e.g. multipart messages) it is interesting to know when a messages is finished. Some multipart messages can carry a NULL payload and without having a NL_CB_FINISH handler, neard never knows when it's actually finished.
2013-11-13agent: Export matching record payload from GetNDEFSamuel Ortiz3-1/+17
Besides the record path and the complete NDEF raw data, the matching record payload is also now exported.
2013-11-13ndef: Implement record payload getterSamuel Ortiz2-0/+9
2013-11-13agent: Only print matching record from NDEF agent's GetNDEFSamuel Ortiz2-29/+10
There is no need to print all records from the NDEF. With each matching record, the record path and the NDEF raw data is pushed back to the agent.
2013-11-11gdbus: Fix trying to remove already removed sourcesBastien Nocera1-0/+3
When we return FALSE from idle handlers, the source is removed. This will be causing warnings in glib 2.40. See https://bugzilla.gnome.org/show_bug.cgi?id=710724
2013-11-11test: Port bt-handover to the ObjectManager interfaceSamuel Ortiz1-32/+34
2013-11-11device: Create the Device D-Bus interface only when the DEP link is upSamuel Ortiz3-6/+19
In Initiator mode, this is when we get a DEP_LINK_UP event. In target mode, DEP link is up as soon as we see a new device. This fix avoids racy situations where a Device interface is available although the DEP link is still not up.
2013-11-11agent: Keep legacy interfaces for a few more releasesSamuel Ortiz1-0/+14
Give ConnMan and BlueZ a few weeks to transition.
2013-11-10test: Fix test-tag whitespace damageSamuel Ortiz1-3/+3
2013-11-10tag: Remove trailing whitespacesSamuel Ortiz1-2/+2
2013-11-10test: Remove dump-recordSamuel Ortiz2-33/+1
This is replaced with test/test-tag dump
2013-11-10tag: Create new path when writing a new RecordSamuel Ortiz1-5/+4
By resetting n_records to 0 after successfully writing a new Record, the newly written Record would be exposed with the same path as the previous one. n_records become next_record and tracks the next available record index.
2013-11-10test: Add test-device scriptSamuel Ortiz1-0/+115
2013-11-10neardutils: Implement dump_all_recordsSamuel Ortiz2-9/+20
This is useful for dumping all records from all tags, and avoids always having to specify a tag path on the test-tag command line.
2013-11-10tag: Unregister Record before TagSamuel Ortiz1-6/+3
When a Tag is leaving the field, it makes more sense to unregister its associated records before the Device itself, and not the other way around.
2013-11-10device: Unregister Record before DeviceSamuel Ortiz1-6/+3
When a Device is leaving the field, it makes more sense to unregister its associated records before the Device itself.
2013-11-10ndef: ObjectManager conversionSamuel Ortiz4-170/+278
ndef.c handles the Record interface. With the ObjectManager interface, GetProperties is no longer needed.
2013-11-10tag: ObjectManager conversionSamuel Ortiz9-367/+181
Set and GetProperties are no longer relevant. Also, there is no longer any need to update the Tags and Records Adapter properties.
2013-11-10test: Fix test-adapter prototypeSamuel Ortiz1-9/+11
The adapter argument (e.g. "nfc0") should be the 2nd one, for consistency sake.
2013-11-10device: ObjectManager conversionSamuel Ortiz6-197/+36
No need to export the Record property. GetProperties and SetProperties are also removed. We also centralize all device related test scripts into test-device, a la BlueZ.
2013-11-10adapter: Initial transition to managed objectsSamuel Ortiz22-684/+510
The manager Adapters property is removed. And so are the adapter Tags and Devices properties. All of them become managed objects and thus no longer need to be explicit parent object properties. Since the only methods left to the Manager interface were agent registration ones, the Manager interface becomes the AgentManager one.
2013-11-05tag: Do not unref a NULL write messageSamuel Ortiz1-2/+4
After successfully writing a tag, the next read might fail in which case tag_read_cb may be called several times. The pending write_msg pointer needs to be unrefed only once.
2013-10-30nfctype4: Do not release target after a succesful tag writeSamuel Ortiz1-1/+0
There is no reason for releasing a target after tag writing succeeded. Especially since check presence still needs the link.
2013-10-18ndef: Simplify the exported MIME type D-Bus type furtherSamuel Ortiz2-2/+2
And make it less confusable with the MIMEType property.
2013-10-18ndef: Simplify D-Bus exported record type stringsSamuel Ortiz2-3/+5
"Android Application Record (AAR)" is not really D-Bus clients friendly.
2013-10-14gdbus: Remove not needed check for NULL DBusPendingCallSzymon Janc1-5/+0
It is now checked by g_dbus_send_message_with_reply() so there is no need to double check that in caller.
2013-10-14gdbus: Check for NULL DBusPendingCall in g_dbus_send_message_with_replySzymon Janc1-1/+10
"Warning: if the connection is disconnected or you try to send Unix file descriptors on a connection that does not support them, the DBusPendingCall will be set to NULL, so be careful with this." Check this in g_dbus_send_message_with_reply so that callers don't need to double check for NULL if g_dbus_send_message_with_reply returned TRUE. This also fix crash if passing FD over D-Bus is blocked e.g. by SELinux policy. bluetoothd[1894]: profiles/audio/avdtp.c:session_cb() bluetoothd[1894]: profiles/audio/avdtp.c:avdtp_parse_cmd() Received SET_CONFIGURATION_CMD bluetoothd[1894]: profiles/audio/a2dp.c:endpoint_setconf_ind() Source 0x6c5000: Set_Configuration_Ind bluetoothd[1894]: profiles/audio/avdtp.c:avdtp_ref() 0x6df360: ref=1 bluetoothd[1894]: profiles/audio/a2dp.c:setup_ref() 0x6d32b0: ref=1 process 1894: arguments to dbus_pending_call_set_notify() were incorrect, assertion "pending != NULL" failed in file dbus-pending-call.c line 636. This is normally a bug in some application using the D-Bus library.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-18 14:32:17 +0000