<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[libnfc developers community - Feature Requests]]></title>
		<link>http://www.libnfc.org/community/</link>
		<description><![CDATA[The most recent topics at libnfc developers community.]]></description>
		<lastBuildDate>Mon, 12 Sep 2011 22:24:27 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Making libnfc work alongside other serial communication]]></title>
			<link>http://www.libnfc.org/community/topic/455/making-libnfc-work-alongside-other-serial-communication/new/posts/</link>
			<description><![CDATA[<p>The way libnfc currently works is that the communication always follows a back and forth pattern. It sends a message and then waits for the expected number of bytes to be received and processes them. I am using a custom board that sends/receives data from an NFC chip (PN532) and other components. For example, the user could press a button and it would send some data over the serial port which could happen when other NFC communication is taking place at the same time. </p><p>Are there any plans to make libnfc do something like buffer incoming data and pull out responses as available? Any suggestions? Thanks!</p>]]></description>
			<author><![CDATA[dummy@example.com (rconty)]]></author>
			<pubDate>Mon, 12 Sep 2011 22:24:27 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/455/making-libnfc-work-alongside-other-serial-communication/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Retry on failure?]]></title>
			<link>http://www.libnfc.org/community/topic/419/retry-on-failure/new/posts/</link>
			<description><![CDATA[<p>Would it be good to retry sending commands if they don&#039;t return the expected response?</p><p>For example in pn532_uart_send do something like?</p><p>&nbsp; if (pn53x_check_ack_frame (pnd, abtRxBuf, sizeof(abtRxBuf))) {<br />&nbsp; &nbsp; // The PN53x is running the sent command<br />&nbsp; } else {<br />&nbsp; &nbsp;&nbsp; &nbsp;// ******&nbsp; try resending up to 3 times<br />&nbsp; &nbsp;&nbsp; &nbsp;pn532_uart_send_helper(pnd, pbtData, szData, attempts+1);</p><p>&nbsp; &nbsp;&nbsp; &nbsp;return false;<br />&nbsp; }</p><p>As one wrinkle, I don&#039;t think it should do this during serial autoprobing, so a mechanism would also be need to be added to disable retries.</p><p>Also, would it be OK to return different error codes for the different failures and have a method that can convert the error code to text to be able to display what command failed (even when logging is turned off)?</p><p>Any thoughts? Thanks!</p>]]></description>
			<author><![CDATA[dummy@example.com (ektimo)]]></author>
			<pubDate>Fri, 24 Jun 2011 14:39:33 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/419/retry-on-failure/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[NDEF push protocol]]></title>
			<link>http://www.libnfc.org/community/topic/317/ndef-push-protocol/new/posts/</link>
			<description><![CDATA[<p>Since Android now has <a href="http://developer.android.com/sdk/android-2.3.3.html">NFC read and write capabilities</a> (de-facto only on the Nexus S as of Feb 2011) I am looking into libnfc for the PC side of an Android-to-PC NFC data transfer.</p><p>This could e.g. be used to establish a Bluetooth connection between phone and PC and use Bluetooth to transfer further data.</p><p>The <a href="http://developer.android.com/reference/android/nfc/NfcAdapter.html">Android documentation</a> speaks of an &quot;NDEF push protocol&quot; and a URI: com.android.npp that any device would have to implement that wants to converse with an Android phone.</p><p>What&#039;s this &quot;NDEF push protocol&quot;? The googletubes wouldn&#039;t reveal much about this.</p><p>What role does the URI play in this protocol?</p><p>In this protocol a feature that can be added to libnfc?</p><p>Thanks for clarifications.</p>]]></description>
			<author><![CDATA[dummy@example.com (zuck)]]></author>
			<pubDate>Tue, 17 May 2011 12:48:22 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/317/ndef-push-protocol/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[NXP PN53X and I2C/SPI]]></title>
			<link>http://www.libnfc.org/community/topic/310/nxp-pn53x-and-i2cspi/new/posts/</link>
			<description><![CDATA[<p>Hi</p><p>I&#039;m currently working on a project which involves NFC. I&#039;m planning right now to use libnfc, but I have not found any support for I2C or SPI. I have other protocols available on my platform, but I would really prefer I2C or SPI instead.</p><p>Have anybody here on this forum successfully implemented a combination of NXP PN53X and I2C/SPI?</p>]]></description>
			<author><![CDATA[dummy@example.com (Gwenn)]]></author>
			<pubDate>Wed, 09 Feb 2011 19:13:03 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/310/nxp-pn53x-and-i2cspi/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[C# DLL]]></title>
			<link>http://www.libnfc.org/community/topic/2/c-dll/new/posts/</link>
			<description><![CDATA[<p>Hi. I&#039;m new here and i was wondering if you could make a dll in managed code so i can use it with C#.</p><p>I want something close to <a href="http://www.phidgets.com/documentation/web/NETDoc/Index.html">phidget&#039;s RFID API</a> for .NET</p><p>Thanks for reading. Tagnard</p>]]></description>
			<author><![CDATA[dummy@example.com (GGelec)]]></author>
			<pubDate>Tue, 01 Feb 2011 16:43:51 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/2/c-dll/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Specify target device in examples]]></title>
			<link>http://www.libnfc.org/community/topic/275/specify-target-device-in-examples/new/posts/</link>
			<description><![CDATA[<p>I noticed that most of the examples will take the first PN53x device they find, and it could be quite helpful (essential even) to be able to specify a specific board via an optional argument (i.e.: &quot;./nfc-emulate-tag /dev/usbTTY1&quot;).&nbsp; As it is now, I wanted to test emulating a card on one board (/dev/usbTTY0) and run nfc-poll on the other (/dev/usbTTY1) but this isn&#039;t possible since they both try to use the first device found.</p><p>It&#039;s trivial to change in the example SW and recompile or make your own application, but it could be helpful to add this by default in future versions to the examples as well since they are quite useful for quick debugging and to make sure your HW is working OK.</p><p>Just a suggestion anyway.</p>]]></description>
			<author><![CDATA[dummy@example.com (rconty)]]></author>
			<pubDate>Mon, 03 Jan 2011 14:12:49 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/275/specify-target-device-in-examples/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Function to check if a nfc target is still present]]></title>
			<link>http://www.libnfc.org/community/topic/189/function-to-check-if-a-nfc-target-is-still-present/new/posts/</link>
			<description><![CDATA[<p>I am happy to see the ongoing development of libnfc, e.g. polling for targets without making an active connection.</p><p>Would it also be possible to check if an active connection made with nfc_initiator_select_tag is still valid? So far i can see no possibility to check if the target has been moved out of the field other than sending data to the tag.</p>]]></description>
			<author><![CDATA[dummy@example.com (dreddolo)]]></author>
			<pubDate>Thu, 24 Jun 2010 13:07:48 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/189/function-to-check-if-a-nfc-target-is-still-present/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[mfd Reader/Maker]]></title>
			<link>http://www.libnfc.org/community/topic/40/mfd-readermaker/new/posts/</link>
			<description><![CDATA[<p>I might be wrong but so far google hasn&#039;t turned up anyway to make the &#039;mfd&#039; file for mftool.</p><p>I tried looking at the example file on <a href="http://www.libnfc.org/libnfc/examples/mftool">http://www.libnfc.org/libnfc/examples/mftool</a> with a hex editor but I couldn&#039;t even find where it had the UID in the format?</p><p>I&#039;d love a bit more help in understanding the format?</p><p>Much Thanks &amp; Respect to Roel for a great API</p>]]></description>
			<author><![CDATA[dummy@example.com (roel)]]></author>
			<pubDate>Wed, 01 Jul 2009 15:11:22 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/40/mfd-readermaker/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Subversion repository]]></title>
			<link>http://www.libnfc.org/community/topic/18/subversion-repository/new/posts/</link>
			<description><![CDATA[<p>Hi,</p><p>Thanks a lot for your efforts.</p><p>Seeing &quot;Install rule&quot; request (topic in this forum), I would like to provide a patch for your Makefile to be able to do this. But when I go on googlecode svn, it seems to be older than archive &quot;libnfc-1.1.0.tar.gz&quot;.</p><p>So my question is: if I want to use/improve development version of libnfc, which one should I use ?</p><p>Thanks again.</p><p>-- <br />Romuald</p>]]></description>
			<author><![CDATA[dummy@example.com (rconty)]]></author>
			<pubDate>Thu, 30 Apr 2009 12:27:35 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/18/subversion-repository/new/posts/</guid>
		</item>
		<item>
			<title><![CDATA[Install rule would be nice]]></title>
			<link>http://www.libnfc.org/community/topic/15/install-rule-would-be-nice/new/posts/</link>
			<description><![CDATA[<p>Hello!</p><p>An install rule in the linux-makefile would be nice.</p><p>regards.<br />Philipp</p>]]></description>
			<author><![CDATA[dummy@example.com (dexter2)]]></author>
			<pubDate>Thu, 16 Apr 2009 15:43:31 +0000</pubDate>
			<guid>http://www.libnfc.org/community/topic/15/install-rule-would-be-nice/new/posts/</guid>
		</item>
	</channel>
</rss>

