Skip to content

Conversation

@mranostay
Copy link

Some FeliCa cards only respond to 212 kbit polling requests
(for instance Hong Kong metro aka Octopus cards) so we should poll
for them after checking for 424 kbit high-speed functionality

Signed-off-by: Matt Ranostay [email protected]

Some FeliCa cards only respond to 212 kbit polling requests
(for instance Hong Kong metro aka Octopus cards) so we should poll
for them after checking for 424 kbit high-speed functionality

Signed-off-by: Matt Ranostay <[email protected]>
Copy link
Contributor

@SloCompTech SloCompTech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, have you tested it ?

@mranostay
Copy link
Author

Yes has been tested

if (candidates_count < 0)
return NULL;

// Poll for a FELICA 212 kbit tag (only if no 424 kbit tag was found)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we list both 212 and 424 kbit tags instead of listing 212 tags when no 424 is found?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guess one could... but does libfreefare support multiple readers? If not then it doesn't make too much sense to worry about that use case

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it does: as far as I can recall, I ran the test suite with 2 devices and 1 or 2 cards on each. Has less communication problems than with 1 device and 3+ tags 😄

But sometimes my memory tricks on me, and I don't have this hardware anymore to check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants