Adding Ch375 dll64 access on windows #89
Open
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
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.
This is a follow up of #54 and refered to dual-driver backend of https://github.com/ch32-rs/wlink/blob/217f0e5136892ffcc6a80204a601bc1b62159505/src/usb_device.rs#L161-L168
It changed
device_handlefromDeviceHandle<rusb::Context>toOption<DeviceHandle<rusb::Context>>. So it can be none when using CH375 driver. When compiled on win64,ch375_indexstores the device index.On win64, it will first try to use CH375 backend, then try libusb if unsuccessful.
It has been tested on Win10 with both CH375 and WinUSB driver, and Mac OS 14.7 on M2.
This is my first rust code and hopefully the code quality is OK.