Onboard

  1. Bug #1366421
  2. Comment #39

Comment 39 for bug 1366421

Revision history for this message
Ritesh Raj Sarraf (rrs) wrote : Re: [Bug 1366421] Re: d-bus method for setting the auto-show option

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sun, 2016-12-11 at 00:09 +0000, marmuta wrote:
> Hmm, interesting. Do these ideapad key-strokes arrive in xinput? That's
> where we could receive them in Onboard.
>
> That's for the ideapad device:
> $ xinput test-xi2 11   # Note the device id may change here, better check with
> "xinput"
>
> and that one for the core keyboard:
> $ xinput test-xi2 3
>

Here's the output you asked for:

rrs@learner:~/rrs-home/Community/linux-upstream_GIT (broken-mmc)$ xinput test-
xi2 3
Virtual core keyboard                    id=3 [master keyboard
(2)]
 Reporting 1 classes:
  Class originated from: 12. Type: XIKeyClass
  Keycodes supported: 248

EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyNormal (detail NotifyNonlinear)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 10 (FocusOut)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyGrab (detail NotifyNonlinear)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyUngrab (detail NotifyNonlinear)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 14 (RawKeyRelease)
    device: 3 (12)
    detail: 36
    valuators:

EVENT type 3 (KeyRelease)
    device: 3 (12)
    detail: 36
    flags:
    root: 1498.00/822.00
    event: 1411.00/671.00
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0xe5 event 0x2800001 child 0x0
EVENT type 13 (RawKeyPress)
    device: 3 (12)
    detail: 126
    valuators:

EVENT type 2 (KeyPress)
    device: 3 (12)
    detail: 126
    flags:
    root: 1498.00/822.00
    event: 1411.00/671.00
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0xe5 event 0x2800001 child 0x0
EVENT type 1 (DeviceChanged)
    device: 3 (11)
    reason: SlaveSwitch
 Reporting 1 classes:
  Class originated from: 11. Type: XIKeyClass
  Keycodes supported: 248

EVENT type 13 (RawKeyPress)
    device: 3 (11)
    detail: 201
    valuators:

EVENT type 10 (FocusOut)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyGrab (detail NotifyAncestor)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 14 (RawKeyRelease)
    device: 3 (11)
    detail: 201
    valuators:

EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyUngrab (detail NotifyAncestor)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 1 (DeviceChanged)
    device: 3 (12)
    reason: SlaveSwitch
 Reporting 1 classes:
  Class originated from: 12. Type: XIKeyClass
  Keycodes supported: 248

EVENT type 14 (RawKeyRelease)
    device: 3 (12)
    detail: 126
    valuators:

EVENT type 3 (KeyRelease)
    device: 3 (12)
    detail: 126
    flags:
    root: 1498.00/822.00
    event: 1411.00/671.00
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    valuators:
    windows: root 0xe5 event 0x2800001 child 0x0
EVENT type 1 (DeviceChanged)
    device: 3 (11)
    reason: SlaveSwitch
 Reporting 1 classes:
  Class originated from: 11. Type: XIKeyClass
  Keycodes supported: 248

EVENT type 13 (RawKeyPress)
    device: 3 (11)
    detail: 200
    valuators:

EVENT type 10 (FocusOut)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyGrab (detail NotifyAncestor)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 14 (RawKeyRelease)
    device: 3 (11)
    detail: 200
    valuators:

EVENT type 9 (FocusIn)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyUngrab (detail NotifyAncestor)
    flags:  [same screen]
    buttons:
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1498.00 / 822.00
    event x/y: 1411.00 / 671.00
EVENT type 10 (FocusOut)
    device: 3 (3)
    windows: root 0xe5 event 0x2800001 child 0x0
    mode: NotifyNormal (detail NotifyNonlinear)
    flags:  [same screen]
    buttons: 1
    modifiers: locked 0 latched 0 base 0 effective: 0
    group: locked 0 latched 0 base 0 effective: 0
    root x/y:  1595.00 / 895.00
    event x/y: 1508.00 / 744.00
EVENT type 1 (DeviceChanged)
    device: 3 (12)
    reason: SlaveSwitch
 Reporting 1 classes:
  Class originated from: 12. Type: XIKeyClass
  Keycodes supported: 248

EVENT type 13 (RawKeyPress)
    device: 3 (12)
    detail: 37
    valuators:

EVENT type 13 (RawKeyPress)
    device: 3 (12)
    detail: 54
    valuators:

^C
2016-12-11 / 15:50:59 ♒♒♒  ☹  => 130

> I hoped to locate the source of the codes 192 and 193 in
> drivers/platform/x86/ideapad-laptop.c, but can't seem to find it. I only
> looked at the vanilla kernel, though. Maybe the debian and ubuntu add
> patches.
>

I doubt that the Debian kernel adds patches. Not sure about Ubuntu.

> For curiosity, is there anything interesting in these sysfs folders. Key-
> strokes are a start, but I'd prefer a status bit. That way we could query what
> state the system is in when Onboard starts and won't have to wait for the next
> key-stroke.
> /sys/kernel/debug/ideapad/cfg
> /sys/kernel/debug/ideapad/status
>
>

root@learner:/sys/kernel/debug/ideapad# cat cfg
cfg: 0x017DE014

Capability: Bluetooth Wireless Camera
Graphic:
root@learner:/sys/kernel/debug/ideapad# cat status
Backlight max: 16
Backlight now: 3
BL power value: On
=====================
Radio status: Off(0)
Wifi status: Off(0)
BT status: On(1)
3G status: Off(0)
=====================
Touchpad status:On(1)
Camera status: On(1)

And this status is wrong. Because my wifi is on.

- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlhNK9UACgkQpjpYo/Lh
dWlfyRAAjjQkKZm92o42d88bB/k0t1vBcb5b0ePzoOLlCfUaujQYw+TMAqrDXOoF
0R32eeiho2KVaZ/oIr0bXtFrVTO/JBX1wIKsuFiaBf1vW8kX8k8JNbPND6niD6XD
Hf4MoX1aQYcZdn/5LKFf9XpvsSYZpWG8D9+qf9EP1WkA2mkP1ZicOV3WH2K0+T/X
kfXbaecwRw1n12wKkTFoQzRTy+X7xil1uS8o3Z4CghydR+Bx0eVUUWHHS+a90FAL
D7wQwsV7D/maPGaWd0PjAlJIhaysyQrdrFKGWVpHxZMw0tLPJ8AKGL2QNcO6iFrr
eK1zHHUWm2K5aOcFQ7PgWqSz1GyWlGXS7Rqoy6rItlNzYikHKnsDYa5hJWX29Zim
c61CdX6VXivGu5/TQ1ti9ecLx3s8VkBj/rd7CuCmXtDaADEcv6A3azSyyF5+bi62
vlVUlslfKTUOBD81DLUsmp/LZFMnLNof8PxKV8M+LUlvT7IgcbZNNEldeq1EBzfM
GZA/ZXtONgZHmQusi+M/ZUUkivw0uIRldZe8OCtH7cEQOvduNVFqJBDDETGVnMHc
6tD/JFkzIpI0A8+trb2dtqHE9cgUjJTrWPYu+paG2sZpa+mvKH21rL2lYo7RVdSn
glN+YryxHCkKJphrVnOzmf8cgG54EffML+1Fbhv949AhoGD+8W4=
=GY2w
-----END PGP SIGNATURE-----