Repository navigation
Add Jabra Link 380 (paired headset) support - #596
Merged
Merged
Conversation
The Link 380 dongle (PID 0x24c7) speaks the same GN Protocol (GNP) as the Link 390, but exposes the GNP vendor collection (0xFF00) on usage 0x01 instead of 0x05. getMetadata() reports the paired headset's name/serial. hid_utility.cpp: try usage_page/usage matching on all platforms, not just Windows. On Linux/macOS the Link 380's three collections all share interface 3, so the previous interface_number-only fallback opened the wrong (Telephony) collection and hid_open_path failed. Verified on hardware: battery (76%), sidetone read-back, lights, voice prompts, inactive time, volume limiter, and metadata (Jabra Evolve2 65).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes made
Adds support for the Jabra Link 380 dongle (PID
0x24c7), which speaks the same GN Protocol as the Link 390 but on vendor usage0xFF00/0x01. New device classJabraLink380 : JabraGNPDevice<0x04, 0x01>.hid_utility.cpp: usage_page/usage matching is now attempted on all platforms (previously Windows-only). On Linux/macOS the Link 380's three collections (Telephony, Vendor, Consumer) share interface 3, so the interface_number-only fallback could open the wrong collection.Checklist
Verification
Tested on hardware (Jabra Link 380 + Evolve2 65):
Unit tests: all passed (testLookupJabraLink380). clang-format 18 (WebKit): no changes needed.
--dev -- --list output