-
Notifications
You must be signed in to change notification settings - Fork 66
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
ZMK Rebase v23.12 #25
Conversation
app/src/hog.c
Outdated
} | ||
|
||
struct bt_gatt_notify_params notify_params = { | ||
.attr = &hog_svc.attrs[13], |
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.
This needs to be updated to .attr = &hog_svc.attrs[16],
. Each BT_GATT_CHARACTERISTIC
adds two items to the attrs
array, so the LED report adds 3 items before the mouse items.
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.
Does that mean that this change (taken from the upstream PR) is also insufficient, since it only offsets the index for the consumer report by 2 rather than by 3?
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.
No, the consumer report upstream was added after the mouse report, so it doesn't affect the index of the mouse report
d463963
to
f17bd88
Compare
f17bd88
to
571d91a
Compare
571d91a
to
c652138
Compare
Rebased to upstream ZMK 55aed8e |
74a619c
to
179e6dc
Compare
d28e9fc
to
c0dbb3c
Compare
08ba7d2
to
e3bf640
Compare
Rebases Glove80's patchset onto upstream ZMK at d7d9eed (Wed Nov 15 11:16:59 2023 -0800).
Additionally includes in PR#11 (name Bluetooth device using serial number prefix) and PR#24 (validate devicetree root entity names when remote building).