public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Elias, Ilan" <ilane@ti.com>
To: "lauro.venancio@openbossa.org" <lauro.venancio@openbossa.org>,
	"samuel@sortiz.org" <samuel@sortiz.org>,
	"aloisio.almeida@openbossa.org" <aloisio.almeida@openbossa.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: [RFC] NFC: Add RF technology specific parameters to target info
Date: Wed, 21 Dec 2011 14:18:33 +0000	[thread overview]
Message-ID: <B30D1FD582D6484ABF57420512E5803504FE1669@DNCE03.ent.ti.com> (raw)

Hi Samuel, Lauro, Aloisio,

Currently, the target information (sent as response to NFC_CMD_GET_TARGET) contains the following: target index, protocols, sens_res, and sel_res.
As far as I understand, the sens_res (2 Octets) and sel_res (1 Octet) fields are suitable only for tech A.

It seems that several RF technology specific parameters should be added to the target info:
1) For tech A: NFCID1 (0, 4, 7, or 10 Octets), and NFCID1 Length (1 Octet).
2) For tech B: SENSB_RES Response (11 or 12 Octets), and SENSB_RES Response Length (1 Octet).
3) For tech F: SENSF_RES Response (16 or 18 Octets) and SENSF_RES Response Length (1 Octet).

For example, Android LibNfc and OpenNfc stacks (and the application above) expect those fields.
In some technologies, it's required to use those fields in upper layers, e.g. in Mifare classic the tag ID is used during authentication (the tag ID can be found in each of the information fields mentioned above for each tech by different name).

I'll appreciate your comments on this issue.

Thanks & BR,
Ilan

             reply	other threads:[~2011-12-21 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 14:18 Elias, Ilan [this message]
2011-12-21 14:49 ` [RFC] NFC: Add RF technology specific parameters to target info Samuel Ortiz

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=B30D1FD582D6484ABF57420512E5803504FE1669@DNCE03.ent.ti.com \
    --to=ilane@ti.com \
    --cc=aloisio.almeida@openbossa.org \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=samuel@sortiz.org \
    /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