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

hidraw: only print errors when DEBUG_PRINTF is defined #25

Closed
wants to merge 1 commit into from

Conversation

z3ntu
Copy link
Collaborator

@z3ntu z3ntu commented Jun 17, 2019

Without this PR, the hidraw implementation prints messages to stderr, which the application using this library has no control over. This should be optional, just like it is in the libusb backend.

Originally signal11/hidapi#351

@Youw
Copy link
Member

Youw commented Jun 18, 2019

There're still printf(s)

@z3ntu
Copy link
Collaborator Author

z3ntu commented Jun 18, 2019

This kernel version check is necessary for one workaround for kernels < 2.6.34. As this release is over 9 years old, we can probably remove that workaround now...

And the printf("Can't create udev\n"); calls should be replaceable with #23

@Youw
Copy link
Member

Youw commented Jun 18, 2019

Sure, why not - will you update it?

@Qbicz Qbicz requested review from Qbicz, jdk, todbot and Youw June 24, 2019 21:24
@Youw
Copy link
Member

Youw commented Jun 24, 2019

@z3ntu please give your comment

@z3ntu
Copy link
Collaborator Author

z3ntu commented Jun 25, 2019

Yeah. Let's keep this PR on ice for now until #23 is ready and then adjust this one for hid_error function

@z3ntu
Copy link
Collaborator Author

z3ntu commented Jul 3, 2019

This is obsoleted by #23 now. Closing.

@z3ntu z3ntu closed this Jul 3, 2019
@z3ntu z3ntu deleted the pr_351 branch July 15, 2019 12:10
@mcuee mcuee added the hidraw Related to Linux/hidraw backend label Jul 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hidraw Related to Linux/hidraw backend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants