Issue 171 in libnfc: Add timed version of communication API

5 views
Skip to first unread message

lib...@googlecode.com

unread,
Sep 9, 2011, 7:06:38 AM9/9/11
to nfc-...@googlegroups.com
Status: Feedback
Owner: romain.t...@gmail.com
Labels: Type-Task Priority-Medium Milestone-1.6.x

New issue 171 by romain.t...@gmail.com: Add timed version of communication
API
http://code.google.com/p/libnfc/issues/detail?id=171

The following API functions (at least) needs to be available with timeout
for the libnfc-llcp:

- nfc_initiator_transceive_bytes()
- nfc_target_receive_bytes()
- nfc_target_send_bytes()

The timeout could be specified as a "struct timeval *" argument that could
be directly passed to select(2) in the UART code and with minor math to
usb_bulk_read(3) & usb_bulk_write(3) in the USB code.

The new API functions could be called:

- nfc_initiator_timedtransceive_bytes()
- nfc_target_timedreceive_bytes()
- nfc_target_timedsend_bytes()

... to follow the mq_send(2) -> mq_timedsend(2) to follow the message
queues POSIX convention.

However, a nfc_initiator_transceive_bytes_timed() function is already
available, allowing to specify a uint32_t 'cycles' argument used by the PN
itself. So maybe proper names should be found. Any suggestion is
welcomed, so I set the status to feedback for now!

Thanks!

lib...@googlecode.com

unread,
Sep 29, 2011, 5:08:30 AM9/29/11
to nfc-...@googlegroups.com
Updates:
Status: Started

Comment #1 on issue 171 by romain.t...@gmail.com: Add timed version of
communication API
http://code.google.com/p/libnfc/issues/detail?id=171

I started working on this a few weeks ago.

lib...@googlecode.com

unread,
Sep 29, 2011, 11:04:08 AM9/29/11
to nfc-...@googlegroups.com

Comment #2 on issue 171 by romain.t...@gmail.com: Add timed version of
communication API
http://code.google.com/p/libnfc/issues/detail?id=171

Fixed

lib...@googlecode.com

unread,
Sep 29, 2011, 11:11:19 AM9/29/11
to nfc-...@googlegroups.com
Updates:
Status: Fixed

Comment #3 on issue 171 by romain.t...@gmail.com: Add timed version of

Reply all
Reply to author
Forward
0 new messages