UMBRA-6: Add DeviceSpecs for the Viper line (9 PIDs) #14

Merged

David merged 1 commit from feat/viper-line-devicespecs-UMBRA-6 into main

2026-06-06 15:39:35 +02:00

David commented

2026-06-06 12:45:53 +02:00

Owner

UMBRA-6: Add DeviceSpecs for the Viper line (9 PIDs)

Registers the nine remaining Viper PIDs from OpenRazer's razermouse_driver.h as individual DeviceSpec files under crates/umbra-hid/src/models/, wired into the SUPPORTED table and resolvable via models::lookup.

PID	Model	Poll	Lighting	Battery / Idle
0x0078	Razer Viper	yes (0xFF)	Logo, txn 0x3f	none
0x007A	Razer Viper Ultimate (Wired)	yes (0xFF)	Logo, txn 0x3f	0xFF / 0xFF
0x007B	Razer Viper Ultimate (Wireless)	yes (0xFF)	Logo, txn 0x3f	0xFF / 0xFF
0x0091	Razer Viper 8KHz	None (rate2 path)	Logo, txn 0x1f	none
0x009E	Razer Viper Mini SE (Wired)	None (rate2 path)	none	0x1f / 0x1f
0x009F	Razer Viper Mini SE (Wireless)	None (rate2 path)	none	0x1f / 0x1f
0x00B8	Razer Viper V3 HyperSpeed	yes (0x1f)	none	0x1f / 0x1f
0x00C0	Razer Viper V3 Pro (Wired)	yes (0x1f)	none	0x1f / 0x1f
0x00C1	Razer Viper V3 Pro (Wireless)	None (rate2 path)	none	0x1f / 0x1f

How the values were sourced

Every transaction ID, poll rate, lighting zone, effect kind, and battery/idle flag was read branch-by-branch off razermouse_driver.c (the per-command transaction_id.id switches) and razer_mouse_probe (the CREATE_DEVICE_FILE registrations that decide which features each PID exposes), not assumed.

The original Viper / Ultimate (wired + wireless) / 8K run firmware, serial, dpi, and built poll paths on 0xFF; the SE and V3 generation moved to 0x1f.
The Chroma models (Viper, Ultimate, 8K) carry a single Logo zone with the full effect set (static / spectrum / reactive / breathing). The plain Viper and Ultimate run their logo effects on 0x3f; the 8K variant runs them on 0x1f.
The 8K, the Mini SE pair, and the V3 Pro wireless drive polling through the set_polling_rate2 / get_polling_rate2 HyperPolling path that umbra does not yet build, so poll_rate is None with a documented gap in each file's doc comment (mirroring the hyperpolling_dongle / deathadder_v4_pro precedent). The V3 HyperSpeed and V3 Pro wired keep the standard poll path on 0x1f.
DPI maxima are documented as sensor-derived assumptions: Focus+ 20K for Viper / Ultimate / 8K, Focus Pro 30K for the Mini SE and V3 HyperSpeed, Focus Pro 35K for the V3 Pro. The driver does not clamp DPI.

Acceptance criteria

models/mod.rs registers a DeviceSpec for every PID in the table, each in its own <model>.rs file.
Wired and wireless/receiver variants are separate specs; battery-carrying variants expose BatterySpec and, where the driver supports it, IdleSpec.
Each Features field's txn, poll rates, lighting zones, and effect kinds come from the matching driver branch; features with no umbra command builder are declared None with a doc comment.
DPI maxima documented as sensor-derived assumptions in each file's doc comment.
README "Supported devices" table lists every new model with VID:PID, DPI max, polling, lighting, and battery columns.
cargo fmt --check, cargo clippy --workspace --all-targets, and cargo test --package umbra-hid --no-default-features pass clean; registration covered by the new every_viper_line_pid_is_registered test.

🤖 Generated with Claude Code

## UMBRA-6: Add DeviceSpecs for the Viper line (9 PIDs) Registers the nine remaining Viper PIDs from OpenRazer's `razermouse_driver.h` as individual `DeviceSpec` files under `crates/umbra-hid/src/models/`, wired into the `SUPPORTED` table and resolvable via `models::lookup`. | PID | Model | Poll | Lighting | Battery / Idle | |--------|-----------------------------------|------|----------------|----------------| | 0x0078 | Razer Viper | yes (0xFF) | Logo, txn 0x3f | none | | 0x007A | Razer Viper Ultimate (Wired) | yes (0xFF) | Logo, txn 0x3f | 0xFF / 0xFF | | 0x007B | Razer Viper Ultimate (Wireless) | yes (0xFF) | Logo, txn 0x3f | 0xFF / 0xFF | | 0x0091 | Razer Viper 8KHz | None (rate2 path) | Logo, txn 0x1f | none | | 0x009E | Razer Viper Mini SE (Wired) | None (rate2 path) | none | 0x1f / 0x1f | | 0x009F | Razer Viper Mini SE (Wireless) | None (rate2 path) | none | 0x1f / 0x1f | | 0x00B8 | Razer Viper V3 HyperSpeed | yes (0x1f) | none | 0x1f / 0x1f | | 0x00C0 | Razer Viper V3 Pro (Wired) | yes (0x1f) | none | 0x1f / 0x1f | | 0x00C1 | Razer Viper V3 Pro (Wireless) | None (rate2 path) | none | 0x1f / 0x1f | ### How the values were sourced Every transaction ID, poll rate, lighting zone, effect kind, and battery/idle flag was read branch-by-branch off `razermouse_driver.c` (the per-command `transaction_id.id` switches) and `razer_mouse_probe` (the `CREATE_DEVICE_FILE` registrations that decide which features each PID exposes), not assumed. - The original Viper / Ultimate (wired + wireless) / 8K run firmware, serial, dpi, and built poll paths on `0xFF`; the SE and V3 generation moved to `0x1f`. - The Chroma models (Viper, Ultimate, 8K) carry a single Logo zone with the full effect set (static / spectrum / reactive / breathing). The plain Viper and Ultimate run their logo effects on `0x3f`; the 8K variant runs them on `0x1f`. - The 8K, the Mini SE pair, and the V3 Pro wireless drive polling through the `set_polling_rate2` / `get_polling_rate2` HyperPolling path that umbra does not yet build, so `poll_rate` is `None` with a documented gap in each file's doc comment (mirroring the `hyperpolling_dongle` / `deathadder_v4_pro` precedent). The V3 HyperSpeed and V3 Pro wired keep the standard poll path on `0x1f`. - DPI maxima are documented as sensor-derived assumptions: Focus+ 20K for Viper / Ultimate / 8K, Focus Pro 30K for the Mini SE and V3 HyperSpeed, Focus Pro 35K for the V3 Pro. The driver does not clamp DPI. ### Acceptance criteria - [x] `models/mod.rs` registers a `DeviceSpec` for every PID in the table, each in its own `<model>.rs` file. - [x] Wired and wireless/receiver variants are separate specs; battery-carrying variants expose `BatterySpec` and, where the driver supports it, `IdleSpec`. - [x] Each `Features` field's txn, poll rates, lighting zones, and effect kinds come from the matching driver branch; features with no umbra command builder are declared `None` with a doc comment. - [x] DPI maxima documented as sensor-derived assumptions in each file's doc comment. - [x] README "Supported devices" table lists every new model with VID:PID, DPI max, polling, lighting, and battery columns. - [x] `cargo fmt --check`, `cargo clippy --workspace --all-targets`, and `cargo test --package umbra-hid --no-default-features` pass clean; registration covered by the new `every_viper_line_pid_is_registered` test. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

David added 1 commit

2026-06-06 12:45:53 +02:00

feat(umbra-hid): add DeviceSpecs for the Viper line

Check / fmt + clippy + build + tests (pull_request) Failing after 4s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

01480d28bf

Register the nine remaining Viper PIDs from OpenRazer's razermouse_driver.h, each as its own DeviceSpec file under crates/umbra-hid/src/models/ and wired into the SUPPORTED table: Viper (0x0078), Viper Ultimate wired/wireless (0x007A/0x007B), Viper 8KHz (0x0091), Viper Mini SE wired/wireless (0x009E/0x009F), Viper V3 HyperSpeed (0x00B8), and Viper V3 Pro wired/wireless (0x00C0/0x00C1).

Per-command transaction IDs, lighting zones, effect kinds, poll rates, and battery/idle support are read branch-by-branch off razermouse_driver.c and razer_mouse_probe, not assumed. The original Viper / Ultimate / 8K run firmware/serial/dpi (and built poll paths) on 0xFF; the SE and V3 generation moved to 0x1f. The Chroma models (Viper, Ultimate, 8K) carry a single Logo zone with the full effect set, on 0x3f for the plain models and 0x1f for the 8K variant. The 8K, the SE pair, and the V3 Pro wireless drive polling through the set_polling_rate2 path umbra does not yet build, so their poll_rate is None with a documented gap, mirroring the hyperpolling_dongle / deathadder_v4_pro precedent; the V3 HyperSpeed and V3 Pro wired keep the standard poll path on 0x1f.

DPI maxima are documented as sensor-derived assumptions (Focus+ 20K for Viper/Ultimate/8K, Focus Pro 30K for the SE and V3 HyperSpeed, Focus Pro 35K for the V3 Pro). The README "Supported devices" table lists every new model, and a new every_viper_line_pid_is_registered test covers registration plus the per-family txn, lighting, battery/idle, and poll-path splits.

#UMBRA-6

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>