Zissou PID application #436
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Arachnid
approved these changes
Jun 13, 2019
|
Feel free to email me with any questions you have about running the site - I'm happy to help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As announced in #429, I would like to separately apply for PID
CC1Dfor my Rust smartcard project. The code is Apache/MIT dual-licensed. Regarding host hardware: currently it runs on ST Nucleo L432KC. It will certainly run also on SoloKeys hardware, but the code is built generically to use the Rust embedded-hal traits and USB implementations, and I plan ports to at minimum the nRF52840 Dongle, and eventually the NXP LPC55S69 EVK and hopefully a custom USB dongle based on that chip.The reason I apply already now (the project is work-in-progress, but does answer-to-reset successfully) is that in order to integrate with the standard open source CCID driver, the USB descriptor needs to be added to that repository; lookup on whether a CCID "reader" is "supported" is done via VID/PID pair lookup.
Cheers, and thanks again for this great service!
P.S. I am planning to register an ISO/IEC 7816-5 "registered application provider identifier" (RID), and hand out "proprietary application identifier extensions" (PIX) to open source projects, similar to what you are doing here (the PIX can be up to 11 bytes, so there is even more to distribute than in your PID case). Perhaps you can share your experiences running such a service out of band at some point? I'm @nickray on IRC (freenode) also.