From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Linux NFC <linux-nfc@ml01.01.org>
Subject: Re: [GIT] [3.13] NFC updates
Date: Fri, 18 Oct 2013 14:00:21 -0400 [thread overview]
Message-ID: <20131018180021.GF28130@tuxdriver.com> (raw)
In-Reply-To: <20131015161917.GF30191@zurbaran>
On Tue, Oct 15, 2013 at 06:19:17PM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the first NFC pull request for the 3.13 kernel.
>
> It's a fairly big one, with the following highlights:
>
> - NFC digital layer implementation: Most NFC chipsets implement the NFC
> digital layer in firmware, but others have more basic functionalities
> and expect the host to implement the digital layer. This layer sits
> below the NFC core.
>
> - Sony's port100 support: This is "soft" NFC USB dongle that expects the
> digital layer to be implemented on the host. This is the first user of
> our NFC digital stack implementation.
>
> - Secure element API: We now provide a netlink API for enabling,
> disabling and discovering NFC attached (embedded or UICC ones) secure
> elements. With some userspace help, this allows us to support NFC
> payments.
> Only the pn544 driver currently supports that API.
>
> - NCI SPI fixes and improvements: In order to support NCI devices over
> SPI, we fixed and improved our NCI/SPI implementation. The currently
> most deployed NFC NCI chipset, Broadcom's bcm2079x, supports that mode
> and we're planning to use our NCI/SPI framework to implement a
> driver for it.
>
> - pn533 fragmentation support in target mode: This was the only missing
> feature from our pn533 impementation. We now support fragmentation in
> both Tx and Rx modes, in target mode.
>
> The following changes since commit b75ff5e84bb6c2d43a8ec39b240c80f0543821f0:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-09-19 13:57:28 -0500)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next.git tags/nfc-next-3.13-1
>
> for you to fetch changes up to ddc1a70b5f2a07a932ed31f989d63937bb813439:
>
> NFC: Fix SE API related sparse warning (2013-10-07 14:18:44 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-10-18 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 16:19 [GIT] [3.13] NFC updates Samuel Ortiz
2013-10-18 18:00 ` John W. Linville [this message]
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=20131018180021.GF28130@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).