Repository navigation
descriptor: add Razer Blade 17 (2022), PID 0x028b, from issue #10 - #11
Merged
sqmagellan merged 1 commit intoOct 23, 2026
Merged
Conversation
Contributor
Author
|
Verification summary for approval of the pending workflow run:
Hardware details and fan measurements are in #10. Happy to adjust the descriptor (e.g. fan range, feature list) on review. |
CloudCorpRecords
force-pushed
the
model/blade-17-2022-028b
branch
from
October 20, 2026 17:44
a9d1102 to
61ef0d8
Compare
…lan#10 Signed-off-by: CloudCorpRecords <95189389+CloudCorpRecords@users.noreply.github.com>
CloudCorpRecords
force-pushed
the
model/blade-17-2022-028b
branch
from
October 20, 2026 19:54
61ef0d8 to
47eb1d7
Compare
Owner
|
Thanks for the PR. Before I merge:
The Manual-mode fan sweep from #10 would still help, but it doesn't block this. |
sqmagellan
added a commit
that referenced
this pull request
Oct 23, 2026
PR #11 makes the Blade 17 2022 (0x028b) a catalogued model, and a catalogued model never learned, so its known 0x05 to Max Fan "on" would have failed every Custom apply. KNOWN_LACKING now applies to a catalogued model too, through a record that starts with its entries and learns nothing more (UnsupportedLog::fixed): any other 0x05 there is still an error. 0x028b lists Max Fan. A model without an entry keeps no record, as before. Device::detect, the simulator and the CLI test detection all do the same; the 0x028b conformance run now never sends 0x070f, so the open question about Max Fan "off" no longer blocks it. CHANGELOG: #11's entry joins the Unreleased section, plus Max Fan as a lacking setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Closes #10.
Summary
Adds a
SUPPORTEDdescriptor for the Razer Blade 17 (2022), PID0x028b(stem prefixRZ09-0423; the reporting unit enumerates asRZ09-0423P), removes its now-redundantFAN_RANGE_BY_PIDfallback row, and lists it in the README reported-models table and CHANGELOG.Verified on hardware (reporting unit, Windows 11 10.0.26200)
auto json).auto json/auto infonow reportRazer Blade 17 (2022)instead of the generic untested profile.Not verified / known limits (also in #10)
(3500, 5000)range stays transcribed, not measured - same treatment as the Blade 18 entry from [model] Razer Blade 18 4090 2023, PID 0x02a0 #1.fan max enableanswers NotSupported (0x05), exit 4, on this EC.Checks
cargo test -p librazer: 191 passed + 2 doc-tests (GNU toolchain locally; MSVC linker unavailable on the reporting machine, so the Windows MSVC build is left to CI).cargo clippy -p librazer --all-targets -- -D warnings: clean.cargo fmt --all --check: clean.