- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.9k
debug_interface impl for DDS; rs-terminal with DDS #12270
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
Changes from all commits
1ec494c
              c364185
              9e8347f
              acf494c
              bc9571d
              691e52e
              1c6e2d5
              abfbf39
              becf0a7
              20fc8be
              File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
|  | @@ -339,13 +339,13 @@ namespace librealsense | |
|  | ||
| virtual std::vector<uint8_t> send( std::vector<uint8_t> const & data ) const; | ||
| virtual std::vector<uint8_t> send( command cmd, hwmon_response * = nullptr, bool locked_transfer = false ) const; | ||
| std::vector<uint8_t> build_command(uint32_t opcode, | ||
| static std::vector<uint8_t> build_command(uint32_t opcode, | ||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why do we need this as static? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In the beginning, I had the build-command code directly call the hw-monitor, but there is no hw-monitor object in the DDS device. So how can you build a command? Later I decided I didn't want the DDS code to even know what a hardware monitor is, and that we shouldn't assume to know how a device builds its commands, so I removed the hw-monitor references but this stayed. Currently, I think it's fine making it static as internally that's how it implemented (it calls a static function). Otherwise we would have to turn it into a virtual function and do some other work. I think that it's valid to go that way, but in a different PR and only if needed. | ||
| uint32_t param1 = 0, | ||
| uint32_t param2 = 0, | ||
| uint32_t param3 = 0, | ||
| uint32_t param4 = 0, | ||
| uint8_t const * data = nullptr, | ||
| size_t dataLength = 0) const; | ||
| size_t dataLength = 0); | ||
|  | ||
| void get_gvd(size_t sz, unsigned char* gvd, uint8_t gvd_cmd) const; | ||
| static std::string get_firmware_version_string(const std::vector<uint8_t>& buff, size_t index, size_t length = 4); | ||
|  | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't there an `explanation`` field in case of failure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what it's supposed to be getting in the next line... I copy-pasted, maybe there's a bug somewhere else, too -- I'll check.