View Single Post
Old 08-29-2024, 06:54 AM   #183
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 3,939
Karma: 17500001
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Quote:
Originally Posted by silvern0va View Post
I'm unsure if I'm doing this correctly but this is what I ended up with
I was just looking for the binary file, but I can deal with a text dump.
Code:
05 0c    Usage page (Consumer)
09 01    Usage (Consumer control)
a1 01    Collection (Application)

85 03    Report id (3)

15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 0b    Report count (11)
09 e9    Usage (Volume increment)
09 ea    Usage (Volume decrement)
09 cd    Usage (Play/Pause)
0a ae 01 Usage (AL Keyboard layout)
09 30    Usage (Power)
09 40    Usage (Menu)
09 46    Usage (Menu escape)
0a 23 02 Usage (AC Home)
09 b6    Usage (Scan previous track)
09 b5    Usage (Scan next track)
81 02    Input (Variable, Absolute)

95 01    Report count (1)
75 0d    Report size (13)
81 03    Input (Constant)

c0       End collection

05 0d    Usage page (Digitizer)
09 02    Usage (Pen)
a1 01    Collection (Application)

85 02    Report id (2)

09 22    Usage (Finger)
a1 02    Collection (Logical)

09 42    Usage (Tip switch)
15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

09 32    Usage (In range)
81 02    Input (Variable, Absolute)

95 06    Report count (6)
81 03    Input (Constant)

75 08    Report size (8)
09 51    Usage (Contact identifier)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

05 01    Usage page (Desktop)
26 ff 0f Logical maximum (4095)
75 10    Report size (16)
55 0e    Unit exponent (-2)
65 33    Unit (in³)
09 30    Usage (X)
35 00    Physical minimum (0)
46 b5 04 Physical maximum (1205)
81 02    Input (Variable, Absolute)

46 8a 03 Physical maximum (906)
09 31    Usage (Y)
81 02    Input (Variable, Absolute)

c0       End collection

05 0d    Usage page (Digitizer)
09 54    Usage (Contact count)
95 01    Report count (1)
75 08    Report size (8)
81 02    Input (Variable, Absolute)

85 08    Report id (8)

09 55    Usage (Contact count maximum)
25 05    Logical maximum (5)
b1 02    Feature (Variable, Absolute)

c0       End collection
That's pretty much ok.

I wouldn't (and I don't) put Physical maximum in. That complicates things.
Without that, 2048 means the center of the screen no matter how big it is.
Once you start putting in Physical maximum in, 2048 means 6" down on a display that might not even be that big.
OTOH, they do specify the units as cubic inches, so it's probably ignored anyway.

Usage 0x32 & 0x42 on the digitizer are correct.
I'd guess that hid.ko is mangling that and that evtest is working correctly.

In any case, it looks like it sends two HID reports, 0x03 (keys) and 0x02 (digitizer) all the time.

Did you try playing with all the modes on the ring?
It seems complicated to me.
Renate is offline   Reply With Quote