From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935557AbdACQmH (ORCPT ); Tue, 3 Jan 2017 11:42:07 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:50437 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759681AbdACQlb (ORCPT ); Tue, 3 Jan 2017 11:41:31 -0500 X-ME-Sender: X-Sasl-enc: nkHOy6QSrjVPQydNqNaXMzMvBlhb6ZWwNYyv60DgpD9f 1483461205 Date: Tue, 3 Jan 2017 09:33:24 -0700 From: Mark Greer To: Geoff Lansberry Cc: linux-wireless , Lauro Ramos Venancio , Aloisio Almeida Jr , Samuel Ortiz , robh+dt@kernel.org, mark.rutland@arm.com, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Justin Bronder , Jaret Cantu Subject: Re: [PATCH v3 3/3] nfc: trf7970a: Prevent repeated polling from crashing the kernel Message-ID: <20170103163324.GA3184@animalcreek.com> References: <1482380314-16440-1-git-send-email-geoff@kuvee.com> <1482380314-16440-3-git-send-email-geoff@kuvee.com> <20161224060141.GA9069@animalcreek.com> <20161224172439.GA15103@animalcreek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Animal Creek Technologies, Inc. User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [Please stop top-posting. Bottom-post only to these lists.] Hi Geoff & happy new year. On Tue, Dec 27, 2016 at 09:18:32AM -0500, Geoff Lansberry wrote: > Mark - I will split this off soon. OK > In the meantime - here is some more info about how we use it. > > We do use NFC structures. I did find an interesting clue in that > there are certain bottles that cause neard to segfault, I'm not sure > what is different about them. We write a string, like > "coppola_chardonnay_2015" to the bottles. Off the top of my head, it could be the length of the text. It would be useful to compare the data that works to the data that doesn't work. Can you install NXP's 'TagInfo' app on a smartphone and scan tags with working & non-working data? You can email the data from the app to yourself, edit out the cruft, and share here. > Come to think of it, I > haven't done anything special to make that an ndef record, just > assumed that it would happen by default, I'll look into this further. If you wrote the data using neard, it will be NDEF formatted. Since it is working this well, it is virtually guaranteed that the data is NDEF formatted. > Also, I've been running neard with --plugin nfctype2. Just in case > the problem was happening due to cycling through other tag types. It > didn't seem to make any difference, but I have not gone back to > default. Good to know, thanks. Mark --