Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for HID SAM communication with SEOS cards #2704

Merged
merged 13 commits into from
Jan 6, 2025

Conversation

jkramarz
Copy link
Contributor

@jkramarz jkramarz commented Jan 4, 2025

No description provided.

Copy link

github-actions bot commented Jan 4, 2025

You are welcome to add an entry to the CHANGELOG.md as well

armsrc/sam_seos.c Outdated Show resolved Hide resolved
@iceman1001
Copy link
Collaborator

You also got a breaking build.
wrong type of the variable which pointer you are sending into the fct.

image

@jkramarz
Copy link
Contributor Author

jkramarz commented Jan 5, 2025

You also got a breaking build. wrong type of the variable which pointer you are sending into the fct.

I put a cast there now to silence the warning, as it's big enough.

I'll cleanup unnecessary code duplication between cmdhfseos.c and cmdhficlass.c and add one more small feature soon.

@iceman1001
Copy link
Collaborator

Lemme know when you think you are ready for merge

@jkramarz jkramarz force-pushed the feature/sam_seos branch 2 times, most recently from 8c1fa63 to 2539c66 Compare January 6, 2025 14:37
@jkramarz jkramarz changed the title WIP: support for HID SAM communication with SEOS cards support for HID SAM communication with SEOS cards Jan 6, 2025
@jkramarz
Copy link
Contributor Author

jkramarz commented Jan 6, 2025

@iceman1001, it's cleaned up and rebased.

@iceman1001 iceman1001 merged commit a531870 into RfidResearchGroup:master Jan 6, 2025
1 check passed
@iceman1001
Copy link
Collaborator

Excellent!

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.

2 participants