Age | Commit message (Collapse) | Author | Files | Lines |
|
The intial request is kept through the snep_data and
snep_core_process_request no longer relies on the last read frame to
build an answer but only on the snep_data pointer.
Without this fix, each fragment from a fragmented PUT was handled as
a complete SNEP frame (header included) which caused process_request
to get completely confused about how to handle fragments.
Now that snep_core_read is fixed, the fragmentation SNEP unit test can
be fixed as well.
|
|
Added api to prepare MIME type WSC record for unit tests.
|
|
|
|
This is needed for implementing SNEP unit tests.
|
|
|
|
|
|
|
|
Current handover registration apis does not support for carrier
specific registration. Added an extra parameter (carrier type) to
RegisterHandoverAgent and UnregisterHandoverAgent. This is an initial
patch for wifi handover agent registration. WiFi NDEF message handling
will be supported soon.
|
|
To be more generic, renaming structure name from bt_data to
carrier_data.
|
|
With the netlink kernel API changes, including a copy of the NFC header and
not relying on the system one will allow clean builds. The drawback could
be missing runtime features but that's better than not being able to run
the daemon at all.
|
|
It will be also used by handover agent implementation
|
|
This fix number of build error on architectures that can't handle
unaligned memory access (eg. ARM).
Most of the code was originally written in BlueZ's bluetooth.h.
|
|
These functions propose to check ndef records for specific fields
like mime type or ID field in record header.
|
|
If detected BlueZ is not version 4 handover agent is used for bluetooth
data handling.
|
|
|
|
This would allow multiple carriers at the same time (e.g. Bluetooth
and Wifi)
|
|
Add suffix "_msg" to function near_ndef_parse for
name consistency and to stress out its role.
|
|
Now this function will release allocated data using callback, so it will
be unnecessary to check its returned error code (if callback was passed).
Main reasons to prepare this change were improvement of code readability
and removing error prone code paths.
|
|
This is needed by the MIFARE plugin.
|
|
The type3 tag IC type information will be used for tag formatting.
|
|
|
|
|
|
For consistency sake, setters return void.
|
|
|
|
* Add a new near_tag_driver op (format) used for formatting blank tags.
* In case an un-formatted tag is being written __near_tag_write()
first format the tag and if that succeeds it proceeds to writing
the data.
|
|
Add an API for marking blank tags.
|
|
The check has been moved from plugins to the core code. No need to
export this getter anymore.
|
|
Depending on the NDEF type, the service name will be different. In
particular, Handover NDEFs should be sent to the handover service, not
the SNEP one.
|
|
Bind and listening are related to a particular adapter, not to a target
or device index.
|
|
This patch allows to create handover (Hr or Hs) frames with all the
expecteded records (collision, ac, ...) and the configuration ones
(like e.g. the Bluetooth OOB related data).
|
|
For a defined record type, this routine will count how many records are
found in an NDEF.
|
|
This function returns the length of a NDEF record.
|
|
|
|
Plugins don't need to call thsi routine.
|
|
read and write sounds more like what those drivers do.
|
|
|
|
The NDEF and TLV parsing routines no longer take tag pointers as an argument.
Instead they return a list of records that is added to the underlying
tag structure. Devices will also get their records list.
|
|
|
|
|
|
|
|
The device layer will define the NFC devices (in peer to peer mode at first)
structure and operations.
|
|
|
|
Adapters talk to tags or device directly. The target vs initiator
idea will be removed from the code base.
This commit temporarily breaks p2p.
|
|
Preparing for moving the Target D-Bus interface to Tag.
|
|
|
|
The MAC layer state tell if the peer device is there or not.
|
|
main.conf will be neard settings file.
|
|
Before disconnecting from a target, check if it's present or not.
If it's not, disconnect and decide to start a new poll depending on the
periodic poll setting.
|
|
|
|
The API now allows for an NDEF buffer to be passed when creating the tag.
|