public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Vicki Pfau <vi@endrift.com>
To: linux-bluetooth@vger.kernel.org
Cc: Vicki Pfau <vi@endrift.com>
Subject: [PATCH BlueZ] hog-lib: Increase maximum report map size
Date: Wed,  3 Aug 2022 15:57:17 -0700	[thread overview]
Message-ID: <20220803225716.1287921-1-vi@endrift.com> (raw)

Though a 512 byte report map size seems plenty large, there exist some devices
(e.g. Brydge W-Touch) that send larger reports. There is no protocol-defined
maximum size so doubling the maximum size is safe, and should hopefully fix
most real-world failures.
---
 profiles/input/hog-lib.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/profiles/input/hog-lib.c b/profiles/input/hog-lib.c
index 4a9c60185..9f3eb428c 100644
--- a/profiles/input/hog-lib.c
+++ b/profiles/input/hog-lib.c
@@ -64,7 +64,7 @@
 #define HOG_PROTO_MODE_BOOT    0
 #define HOG_PROTO_MODE_REPORT  1
 
-#define HOG_REPORT_MAP_MAX_SIZE        512
+#define HOG_REPORT_MAP_MAX_SIZE        1024
 #define HID_INFO_SIZE			4
 #define ATT_NOTIFICATION_HEADER_SIZE	3
 
-- 
2.37.1


             reply	other threads:[~2022-08-03 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 22:57 Vicki Pfau [this message]
2022-08-03 23:55 ` [PATCH BlueZ] hog-lib: Increase maximum report map size Luiz Augusto von Dentz
2022-08-04  0:05   ` Vicki Pfau
2022-08-04  0:16     ` Luiz Augusto von Dentz
2022-08-04  0:18       ` Vicki Pfau
2022-08-10  2:02       ` Vicki Pfau
2022-08-10 20:13         ` Luiz Augusto von Dentz
2022-08-15 18:09           ` Luiz Augusto von Dentz
2022-08-16  1:49             ` Vicki Pfau
2022-08-16 18:31               ` Luiz Augusto von Dentz
2022-08-16 20:05                 ` Luiz Augusto von Dentz
2022-08-04  0:00 ` [BlueZ] " bluez.test.bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220803225716.1287921-1-vi@endrift.com \
    --to=vi@endrift.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox