From: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
To: sedat.dilek@gmail.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-nfc@lists.01.org
Subject: Re: [linux-nfc] ThinkPad T470 and NXP PN5xx (PN547 or PN548)
Date: Mon, 13 May 2019 14:28:03 +0300 [thread overview]
Message-ID: <3b7065a2-694f-63bf-fba3-a1641a03ea76@intel.com> (raw)
In-Reply-To: <CA+icZUVMjCWwuC-ee1-+EPU6+mYqFZ7w4ai4t4EJcrsvZ2_BYg@mail.gmail.com>
Hi Sedat, Andy,
Andy, thanks a lot for extending and cleaning that up.
> Unsure, why the pn544_i2c NFC driver shipped with the Linux v5.1.1
does not work.
I briefly looked into drivers/nfc/pn544, that seems like an HCI based chip (as opposed to NCI based PN547).
It might be that changes that Andy posted are already sufficient for PN547 to just work with neard (if I am not missing anything).
# sudo apt-get install neard neard-tools
# man nfctool
Regards,
Oleg
next prev parent reply other threads:[~2019-05-13 11:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 13:46 ThinkPad T470 and NXP PN5xx (PN547 or PN548) Sedat Dilek
2019-05-10 7:43 ` Sedat Dilek
2019-05-10 16:40 ` Andy Shevchenko
2019-05-10 19:51 ` Sedat Dilek
2019-05-10 18:55 ` [linux-nfc] " Oleg Zhurakivskyy
2019-05-10 19:40 ` Sedat Dilek
2019-05-11 13:27 ` Oleg Zhurakivskyy
2019-05-13 9:27 ` Sedat Dilek
2019-05-13 9:50 ` Andy Shevchenko
[not found] ` <CA+icZUWXSup0BfXNZXxcrAAbu-b9KCiBU++OkC+eFqacMrTwRg@mail.gmail.com>
2019-05-13 10:57 ` Andy Shevchenko
2019-05-13 11:07 ` Sedat Dilek
[not found] ` <CA+icZUVDTx_ZUuOgHVDmg5_a4tgrRkPp880+0KPaRJ1d=zF5VQ@mail.gmail.com>
2019-05-13 11:22 ` Sedat Dilek
2019-05-13 12:40 ` Andy Shevchenko
2019-05-13 13:32 ` Sedat Dilek
2019-05-13 14:11 ` Andy Shevchenko
2019-05-13 14:23 ` Sedat Dilek
2019-05-13 19:46 ` Sedat Dilek
2019-05-13 20:02 ` Sedat Dilek
2019-05-13 10:15 ` Oleg Zhurakivskyy
2019-05-13 10:51 ` Sedat Dilek
2019-05-13 11:28 ` Oleg Zhurakivskyy [this message]
2019-05-13 11:31 ` Sedat Dilek
2019-05-13 11:50 ` Sedat Dilek
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=3b7065a2-694f-63bf-fba3-a1641a03ea76@intel.com \
--to=oleg.zhurakivskyy@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=sedat.dilek@gmail.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