From: Samuel Ortiz <samuel@sortiz.org>
To: linux-wireless@vger.kernel.org
Subject: [ANN] NFC daemon open sourced
Date: Thu, 17 Nov 2011 13:38:02 +0100 [thread overview]
Message-ID: <1321533482.30184.6.camel@sortiz-mobl> (raw)
Hi All,
This is a quick announcement to let you know that we released our NFC
daemon code. It's available here:
git://git.kernel.org/pub/scm/network/nfc/neard.git
We named it neard, it works on top of the recently merged NFC kernel
subsystem, and it's GPLv2 licensed.
Beside managing the NFC adapters, targets and devices, the main idea of
neard is to expose the NFC data trough a simple D-Bus interface.
Currently we only support reader mode which means we expose the NDEF
records we get from the detected tags.
In the short term, we're working on adding the following features to
neard:
- Bluetooth OOB pairing support.
- Tag writing mode.
- NFC p2p support (This needs some kernel work as well) through npp and
SNEP.
The card emulation support is a bit of a longer term objective.
We should have our own neard development mailing list fairly soon, I'll
let you know when that happens.
Cheers,
Samuel.
next reply other threads:[~2011-11-17 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 12:38 Samuel Ortiz [this message]
2012-02-29 11:20 ` [ANN] NFC daemon open sourced Samuel Ortiz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1321533482.30184.6.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox