From: Arnd Bergmann <arnd@arndb.de>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Tomas Winkler <tomas.winkler@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next 1/3] mei: nfc: Initial nfc implementation
Date: Wed, 10 Apr 2013 21:46:12 +0200 [thread overview]
Message-ID: <201304102146.12800.arnd@arndb.de> (raw)
In-Reply-To: <20130410191945.GH4874@zurbaran>
On Wednesday 10 April 2013, Samuel Ortiz wrote:
> That works fine with the typical case where your pn544 is directly accessible
> through i2c. But if it's sitting behind the ME, you will need to send
> commands exported through this file to fetch the vendor and radio IDs, but
> also to send those HCI frames that the vanilla Android stack builds after
> encapsulating them into a struct mei_nfc_cmd. And this is all done through the
> /dev/mei interface.
You don't make it sound like a good reason to actually suppor this by adding
a public header for it.
Arnd
next prev parent reply other threads:[~2013-04-10 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 23:41 [char-misc-next 0/3 V6] Support NFC Device on MEI CL Bus Tomas Winkler
2013-04-08 23:41 ` [char-misc-next 1/3] mei: nfc: Initial nfc implementation Tomas Winkler
2013-04-10 17:25 ` Greg KH
2013-04-10 19:19 ` Samuel Ortiz
2013-04-10 19:46 ` Arnd Bergmann [this message]
2013-04-10 20:03 ` Greg KH
2013-04-10 21:15 ` Samuel Ortiz
2013-04-10 22:29 ` Arnd Bergmann
2013-04-10 22:52 ` Samuel Ortiz
2013-04-10 22:59 ` Greg KH
2013-04-08 23:41 ` [char-misc-next 2/3] mei: nfc: Add NFC device to the MEI bus Tomas Winkler
2013-04-08 23:41 ` [char-misc-next 3/3] mei: nfc: Implement MEI bus ops Tomas Winkler
2013-04-09 0:08 ` [char-misc-next 0/3 V6] Support NFC Device on MEI CL Bus Greg KH
2013-04-09 13:12 ` Winkler, Tomas
2013-04-09 13:46 ` 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=201304102146.12800.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=tomas.winkler@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