From e1b03af3097ef43b7f2d3dd220e69c38be463c3f Mon Sep 17 00:00:00 2001 From: John Whittington Date: Mon, 5 Dec 2022 12:24:47 +0100 Subject: [PATCH] known issues section --- Cargo.lock | 2 +- README.md | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/Cargo.lock b/Cargo.lock index 2cf41e7c..9533b574 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -210,7 +210,7 @@ dependencies = [ [[package]] name = "cyme" -version = "1.0.2" +version = "1.1.0" dependencies = [ "assert-json-diff", "clap", diff --git a/README.md b/README.md index ebfee702..5f726d05 100644 --- a/README.md +++ b/README.md @@ -93,3 +93,9 @@ One can also be supplied with `--config`. Copy or refer to './doc/cyme_example_c See './doc/cyme_example_config.json' for an example of how icons can be defined and also the [docs](https://docs.rs/cyme/latest/cyme/icon/enum.Icon.html). The config can exclude the "user"/"colours" keys if one wishes not to define any new icons/colours. Icons are looked up in an order of User -> Default. For devices: `VidPid` -> `VidPidMsb` -> `Vid` -> `UnknownVendor` -> `get_default_vidpid_icon`, classes: `ClassifierSubProtocol` -> `Classifier` -> `UndefinedClassifier` -> `get_default_classifier_icon`. User supplied colours override all internal; if a key is missing, it will be `None`. + +# Known Issues + +* Version major BCD Device difference between libusb and macOS `system_profiler`: If the major version is large, libusb seems to read a different value to macOS. I don't think it's a parsing error but open to ideas. +* libusb cannot read special non-user Apple buses; T2 chip for example. These will still be listed by `system_profiler`. The result is that when merging for verbose data, these will not print verbose information. Use `--force-libusb` to ignore them. +* `sudo` is required to read Linux root_hub string descriptors - a stderr will be printed regarding this. The program works fine without these however.