From: Rymarkiewicz Waldemar <waldemar.rymarkiewicz@tieto.com>
To: Eric Lapuyade <eric.lapuyade@linux.intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-nfc@lists.01.org" <linux-nfc@lists.01.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"eric.lapuyade@intel.com" <eric.lapuyade@intel.com>
Subject: Re: [linux-nfc] [PATCH 2/2] NFC: Correct outgoing frame before requeueing
Date: Fri, 7 Sep 2012 10:08:06 +0200 [thread overview]
Message-ID: <5049AB66.1070907@tieto.com> (raw)
In-Reply-To: <5049A58F.2060905@linux.intel.com>
Hi Eric,
>> BTW I see the headroom for pn544 is 2 but it make use of 1 byte (len).
>> Is that correct?
>
> That question made me go back to have a closer look. With shdlc
> currently adding the len and crc, there would be no reason for the
> driver to request any headroom. If you look at the comment above
> PN544_CMDS_HEADROOM, it says "Largest headroom needed for outgoing
> custom commands". The headroom it requests it not for len, it is used by
> the driver to insert special bytes when handling a
> pn544_hci_data_exchange for a reader F gate, which is a special case.
That makes sense. I guess in 1/2 patch PN544_CMDS_HEADROOM should be 3
() now. Will fix that.
> I didn't remember that when I wrote the previous answer, and this
> defeats my second suggestion. I suggest we go with my first suggestion:
>
> - Specify that the driver xmit MUST NOT modify skb. It shall remove
> anything it inserts or appends before returning from xmit.
It sounds sane.
Thanks,
/Waldek
next prev parent reply other threads:[~2012-09-07 8:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 10:22 [PATCH 1/2] NFC: Remove crc generation from shdlc layer Waldemar Rymarkiewicz
2012-09-06 10:22 ` [PATCH 2/2] NFC: Correct outgoing frame before requeueing Waldemar Rymarkiewicz
2012-09-06 16:17 ` [linux-nfc] " Eric Lapuyade
2012-09-07 6:38 ` Rymarkiewicz Waldemar
2012-09-07 7:43 ` Eric Lapuyade
2012-09-07 8:08 ` Rymarkiewicz Waldemar [this message]
2012-09-06 16:02 ` [linux-nfc] [PATCH 1/2] NFC: Remove crc generation from shdlc layer Eric Lapuyade
2012-09-07 8:08 ` Eric Lapuyade
2012-09-07 8:11 ` Rymarkiewicz Waldemar
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=5049AB66.1070907@tieto.com \
--to=waldemar.rymarkiewicz@tieto.com \
--cc=eric.lapuyade@intel.com \
--cc=eric.lapuyade@linux.intel.com \
--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).