From: David Heidelberg <david@ixit.cz>
To: Michael Walle <michael@walle.cc>,
Krzysztof Kozlowski <krzk@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Michael Thalmeier <michael.thalmeier@hale.at>,
Raymond Hackley <raymondhackley@protonmail.com>,
Bongsu Jeon <bongsu.jeon@samsung.com>,
Mark Greer <mgreer@animalcreek.com>
Cc: netdev@vger.kernel.org
Subject: Re: Path forward for NFC in the kernel
Date: Fri, 17 Apr 2026 14:16:14 +0200 [thread overview]
Message-ID: <4ff7da97-3c85-4b05-aa6d-6d2c7b9bd97f@ixit.cz> (raw)
In-Reply-To: <DHVAXU7E031H.1CPZZA6ELD2DN@walle.cc>
On 17/04/2026 10:54, Michael Walle wrote:
> On Fri Apr 17, 2026 at 9:18 AM CEST, Krzysztof Kozlowski wrote:
>> Does anyone knows if the NFC stack/drivers actually works fine? Did
>> anyone test actual devices?
>
> I was working on a product which used an NFC part from NXP. We
> started with the upstream driver and libnfc and we did some
> bugfixes, that's also probably the reason I'm in the loop here ;).
>
> But eventually it was decided to switch to the libs provided by the
> vendor, because that at least somehow worked reliably (and you'll
> get support from the vendor).
So what we need is show vendor how wonderful Linux kernel is, thus he should
contribute to it and then switch to it (when nVidia can understand it's
beneficial to them, why not NXP).
David
>
> -michael
--
David Heidelberg
next prev parent reply other threads:[~2026-04-17 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 17:10 Path forward for NFC in the kernel Jakub Kicinski
2026-04-17 6:35 ` Michael Walle
2026-04-17 7:18 ` Krzysztof Kozlowski
2026-04-17 8:12 ` David Heidelberg
2026-04-17 8:54 ` Michael Walle
2026-04-17 12:16 ` David Heidelberg [this message]
2026-04-17 13:32 ` David Heidelberg
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=4ff7da97-3c85-4b05-aa6d-6d2c7b9bd97f@ixit.cz \
--to=david@ixit.cz \
--cc=bongsu.jeon@samsung.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=mgreer@animalcreek.com \
--cc=michael.thalmeier@hale.at \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=raymondhackley@protonmail.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