Repository navigation
trigger device watcher on bind and unbind events - #14949
Conversation
![aikido-pr-checks[bot]](https://avatars.githubusercontent.com/in/898896?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Updates the Linux udev device watcher to treat bind/unbind udev actions as device-change events, ensuring device enumeration is triggered on hardware reset scenarios tracked by RSDSO-20233.
Changes:
- Extend the udev action filter to include
bindandunbindin addition toaddandremove. - Update inline comments to document that hardware reset can surface as
unbind/bindrather thanremove/add.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| model = sysname; | ||
| os << model; | ||
| if( model != sysname ) | ||
|
|
There was a problem hiding this comment.
Interesting, new SKUs do not have intel what do we have with D401
There was a problem hiding this comment.
Lets change to realsense and check we get here
There was a problem hiding this comment.
I ll change it to RealSense, as we talked
|
|
||
| const string udev_action = udev_device_get_action( udev_dev ); | ||
| if( udev_action == "add" || udev_action == "remove" ) | ||
| if( udev_action == "add" || udev_action == "remove" || udev_action == "bind" || udev_action == "unbind" ) |
There was a problem hiding this comment.
Can you explain?
Any rest can be added to reproduce before and pass after the fix?
Same issue on Ubuntu x86 ?
There was a problem hiding this comment.
answered in the jira ticket
Tracked by: RSDSO-20233