lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 25 Jul 2014 23:13:32 +0100
From:	Przemo Firszt <>
To:	Benjamin Tissoires <>
Cc:	Dmitry Torokhov <>,
	Jiri Kosina <>,
	Ping Cheng <>,
	Jason Gerecke <>,,
Subject: Re: [PATCH v2 00/10] Input - wacom: conversion to HID driver,
 series 2

Dnia 2014-07-24, czw o godzinie 14:13 -0400, Benjamin Tissoires pisze:
Hi Benjamin,
I'm testing the whole series including the OLED patch that's not on the
list yet.

Hardware: 2 x Intuos4 Wireless tested on usb and bluetooth until noted

What works:
1. Tablet in general, pressure, tilt, buttons etc.
2. Battery reporting (including gnome). The double wireless tablet bug
is gone:

$ ls /sys/class/power_supply/
AC  BAT0  wacom_ac_2  wacom_ac_3  wacom_battery_2  wacom_battery_3

3. Setting LED selector value
4. Setting LED selector brightness (default and pressed)
5. Rendering images to button displays works on usb ONLY.

$ i4oled -d /sys/bus/hid/drivers/wacom/0003\:056A\:00BC.0009/wacom_led/button0_rawimg -t Linux

On bluetooth writing image goes fine (no error), but there is nothing showing up,
so I suspect the brightness of OLED displays is not set properly.

That's the code before changes:

        led = wdata->led_selector | 0x04;
        buf = kzalloc(9, GFP_KERNEL);
        if (buf) {
                buf[0] = WAC_CMD_LED_CONTROL;
                buf[1] = led;
                buf[2] = value >> 2;
                buf[3] = value;
                /* use fixed brightness for OLEDs */
                buf[4] = 0x08;
                hid_hw_raw_request(hdev, buf[0], buf, 9, HID_FEATURE_REPORT,

I don't remember for sure, but I think the range of brightness might be different
over usb and over bluetooth.

TL;DR: the only thing that needs to be fixed is image-over-bluetooth, probably caused by not
setting or incorrect setting of OLED brightness. 

Kind regards,
Przemo Firszt

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists