From: Arnd Bergmann <arnd@arndb.de>
To: Waldemar.Rymarkiewicz@tieto.com
Cc: matti.j.aaltonen@nokia.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, hthebaud@insidefr.com
Subject: Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip
Date: Tue, 15 Mar 2011 10:06:53 +0100 [thread overview]
Message-ID: <201103151006.53558.arnd@arndb.de> (raw)
In-Reply-To: <99B09243E1A5DA4898CDD8B7001114481082FAE39E@EXMB04.eu.tieto.com>
On Tuesday 15 March 2011 09:37:04 Waldemar.Rymarkiewicz@tieto.com wrote:
> >It sounds strange that this will be handled in user space,
> >since it won't have any idea if the hardware is available again.
>
> >I've tried to find the onfc stack that talks to this device
> >but couldn't see it. Do you have a URL for this?
>
> Here you are
>
> http://sourceforge.net/projects/open-nfc/
> http://www.open-nfc.org
I found these before, but I did not find code that opens your
device to read or write it. There is a .zip file with some
source code, but that seems to have no connection to your
driver and no build instructions.
Arnd
next prev parent reply other threads:[~2011-03-15 9:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:20 [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip Waldemar Rymarkiewicz
2011-03-10 13:52 ` Arnd Bergmann
2011-03-10 14:45 ` Waldemar.Rymarkiewicz
2011-03-10 16:20 ` Arnd Bergmann
2011-03-14 14:59 ` Waldemar.Rymarkiewicz
2011-03-14 15:34 ` Arnd Bergmann
2011-03-14 15:45 ` Waldemar.Rymarkiewicz
2011-03-14 16:00 ` Arnd Bergmann
2011-03-14 16:15 ` Waldemar.Rymarkiewicz
2011-03-14 17:01 ` Arnd Bergmann
2011-03-15 8:37 ` Waldemar.Rymarkiewicz
2011-03-15 9:06 ` Arnd Bergmann [this message]
2011-03-17 12:58 ` Waldemar.Rymarkiewicz
2011-03-17 13:07 ` Arnd Bergmann
2011-03-17 13:38 ` Waldemar.Rymarkiewicz
2011-03-17 13:54 ` Arnd Bergmann
2011-03-17 13:58 ` Waldemar.Rymarkiewicz
-- strict thread matches above, loose matches on Subject: below --
2011-03-18 10:40 Waldemar Rymarkiewicz
2011-03-18 10:40 ` Waldemar Rymarkiewicz
2011-03-18 11:03 ` Alan Cox
2011-03-18 15:00 ` Waldemar.Rymarkiewicz
2011-03-18 15:05 ` Arnd Bergmann
2011-03-18 15:12 ` Alan Cox
2011-03-18 15:15 ` Waldemar.Rymarkiewicz
2011-03-18 11:49 ` Wolfram Sang
2011-03-18 15:08 ` Waldemar.Rymarkiewicz
2011-03-18 15:31 ` Mark Brown
2011-03-18 16:43 ` Waldemar.Rymarkiewicz
2011-03-18 12:19 ` Arnd Bergmann
2011-03-18 12:51 ` Mark Brown
2011-03-18 14:20 ` Arnd Bergmann
2011-03-25 14:26 ` Samuel Ortiz
2011-03-29 8:00 ` Waldemar.Rymarkiewicz
2011-03-29 11:05 ` Arnd Bergmann
2011-03-29 11:59 ` Alan Cox
2011-03-29 12:04 ` Arnd Bergmann
2011-03-29 12:23 ` Alan Cox
2011-03-29 13:22 ` Arnd Bergmann
2011-03-31 14:16 ` Samuel Ortiz
2011-03-31 14:42 ` Waldemar.Rymarkiewicz
2011-03-31 14:49 ` Arnd Bergmann
2011-03-31 15:09 ` Samuel Ortiz
2011-03-31 15:24 ` Waldemar.Rymarkiewicz
2011-03-31 15:30 ` Samuel Ortiz
2011-04-01 18:19 ` Aloisio Almeida
2011-04-01 19:43 ` Arnd Bergmann
2011-06-06 20:22 ` Pavan Savoy
2011-06-06 20:30 ` Pavan Savoy
2011-06-06 20:46 ` Aloisio Almeida
2011-06-06 20:50 ` Samuel Ortiz
2011-03-18 15:50 ` Randy Dunlap
2011-03-18 15:57 ` Waldemar.Rymarkiewicz
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=201103151006.53558.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=hthebaud@insidefr.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.j.aaltonen@nokia.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