From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-nfc@lists.01.org, linux-wireless@vger.kernel.org,
charles.gorand@effinnov.com
Subject: Re: [linux-nfc] NXP NFC version and ACPI
Date: Thu, 13 Dec 2018 22:11:41 +0100 [thread overview]
Message-ID: <77343b37-bd55-7249-2be1-f97e9d5de32e@gmail.com> (raw)
In-Reply-To: <6b57b417-d65f-040b-49b1-5b2accb691bb@linaro.org>
On 2018-12-13 21:57, Daniel Lezcano wrote:
> On 13/12/2018 21:50, Anders Rundgren wrote:
>> On 2018-12-13 21:44, Daniel Lezcano wrote:
>>>
<snip>
>>
>> Since all other PC vendors have ceased supporting NFC (Intel made it
>> useless), why bother?
>
> Well at least, I would like to have my laptop working correctly by
> supporting the NFC chip. I think it is not a big deal to have the driver
> supporting it.
>
> For my information, why Intel made it useless ?
The only high volume use of NFC in a PC would be for Secure Payments and Authentication where you use a mobile phone as payment credential holder or authenticator.
Intel rejected this idea. QR has (forever) taken NFC's place.
The QR phenomena is also getting strong in PoS terminal (shop) world since the NFC forum haven't realized that 7816 is an obsolete technology. 800 million Chinese have much better stuff than the West crippled by dated card level protocols.
Anders
>
>>>>
>>>> I dumped the ACPI DSDT table and got the id NXP1001. This one is not
>>>> listed in the match table of the nxp-nci driver.
>>>>
>>>> - is the driver missing for the so called NXP NPC300 ?
>>>> - should the NXP1001 matching string to be added to nxp-nci?
>>>> - is my firmware sending me garbage ?
>>>>
>>>> Thanks in advance for any input
>>>>
>>>> -- Daniel
>>>>
>>>>
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2018-12-13 21:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:38 NXP NFC version and ACPI Daniel Lezcano
2018-12-13 20:44 ` Daniel Lezcano
2018-12-13 20:50 ` [linux-nfc] " Anders Rundgren
2018-12-13 20:57 ` Daniel Lezcano
2018-12-13 21:11 ` Anders Rundgren [this message]
2019-05-13 20:15 ` Sedat Dilek
2019-05-14 6:42 ` Daniel Lezcano
2019-05-14 6:52 ` Sedat Dilek
2019-05-14 6:56 ` Sedat Dilek
2019-05-14 6:57 ` Daniel Lezcano
2019-05-14 7:12 ` Sedat Dilek
2019-05-14 7:49 ` Sedat Dilek
2019-05-14 8:17 ` Daniel Lezcano
2019-05-14 8:30 ` Sedat Dilek
2019-05-14 14:59 ` Sedat Dilek
2019-05-14 16:36 ` Daniel Lezcano
2019-05-19 16:46 ` Daniel Lezcano
2019-05-29 9:33 ` Sedat Dilek
2019-08-05 19:40 ` 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=77343b37-bd55-7249-2be1-f97e9d5de32e@gmail.com \
--to=anders.rundgren.net@gmail.com \
--cc=charles.gorand@effinnov.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-nfc@lists.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).