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.

Sign up for GitHub

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

Jump to bottom

No such device error for Linux should be considered as missing file #28

Closed
svartalf opened this issue May 29, 2019 · 0 comments
Closed

No such device error for Linux should be considered as missing file #28

svartalf opened this issue May 29, 2019 · 0 comments
Labels
A-battery Area: battery crate C-bug Something isn't working O-linux Operating system: Linux

Comments

@svartalf
Copy link
Owner

svartalf commented May 29, 2019 •
edited
Loading

Originally reported at svartalf/rust-battop#7

It seems that some drivers are creating the files at sysfs, but attempt to read them fails with the ENODEV error.
Same issue can be observed here with a current_now file.

I suppose it would be okay to consider the ENODEV errors as a "missing file" result.
@svartalf svartalf mentioned this issue May 30, 2019
Closed
@svartalf svartalf added A-battery Area: battery crate C-bug Something isn't working O-linux Operating system: Linux labels May 30, 2019
davidkna added a commit to davidkna/rust-battery that referenced this issue Jul 31, 2023
@davidkna
fix: replace mach with mach2 fork (svartalf#28)
ada2f1b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-battery Area: battery crate C-bug Something isn't working O-linux Operating system: Linux
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@svartalf