Re: ACR122U response frames contain wrong sequence numbers

Ludovic Rousseau <[email protected]>
Newsgroups gmane.comp.lib.muscle
Message-ID <CAGstE8A+ZBTZZuZTiXtxxqEEupH6N795Sjx4y_tRyfSSaAdiaw@mail.gmail.com>
2013/9/8 Eugene Crosser <[email protected]>:
> Hi!

Hello,

> The attached diff introduces a workaround for the bug in the ACR122U reader that
> makes it use "one less" sequence number in the response frame if the request
> frame was longer than 64 bytes.
>
> It works for me (and does not break on another "correct" CCID reader that I have
> at hand). Whether you want to merge it, or rework it, or drop it altogether if
> of course entirely up to you. I just wanted to share it in case it could be
> useful for somebody.
>
> It is possible that the bug is specific to a subset of the ACR122U readers, and
> there exist readers with the USB ID 072f:2200 that do not have this bug. My
> patch _should not_ break on them, but of course I had no way to test it.

I do not plan to include your patch in my driver. The reader is too
bogus for me.
But if you publish your patch somewhere (in your blog, website, etc.)
I can add a link to the patch.

Bye

-- 
 Dr. Ludovic Rousseau
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.