1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
device: 0.847
graphic: 0.818
boot: 0.697
PID: 0.620
files: 0.513
ppc: 0.397
peripherals: 0.345
performance: 0.339
virtual: 0.335
architecture: 0.327
semantic: 0.325
socket: 0.252
risc-v: 0.227
hypervisor: 0.207
vnc: 0.206
kernel: 0.205
mistranslation: 0.168
register: 0.160
TCG: 0.152
x86: 0.148
debug: 0.148
VMM: 0.125
arm: 0.123
KVM: 0.096
assembly: 0.085
network: 0.081
i386: 0.080
user-level: 0.034
permissions: 0.020
wheel-axis=false does not get applied at hardware init stage
Description of problem:
`-device virtio-tablet,id=touch0,wheel-axis=false` does not get applied at initalization stage, causing android to see it and treat the device as a pointer instead of a tablet. it seems to look for the prop at init stage, I have verified that this is an issue by fixing it with a quick hack below. ~~setting `-device virtio-tablet,id=touch0,wheel-axis=true` will still work fine and cause android to pick it up as a pointer again~~
EDIT: It does not seem to work actually. if set when the default is set to false
Steps to reproduce:
1. Boot android based VM
2. test an app that forces touch only over pointer
Additional information:
```
diff --git a/hw/input/virtio-input-hid.c b/hw/input/virtio-input-hid.c
index a7a244a95d..3175f9c7d5 100644
--- a/hw/input/virtio-input-hid.c
+++ b/hw/input/virtio-input-hid.c
@@ -477,7 +477,7 @@ static struct virtio_input_config virtio_tablet_config_v2[] = {
};
static Property virtio_tablet_properties[] = {
- DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, true),
+ DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, false),
DEFINE_PROP_END_OF_LIST(),
};
```
|