linux-kernel - Re: [PATCH] Input - wacom: update the ABI doc according to latest changes

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20140805155322.Horde.z62yLr1B-ZT7v4rMGcPaVA9@webmail.firszt.eu>
Date:	Tue, 05 Aug 2014 15:53:22 +0000
From:	Przemo Firszt <przemo@...szt.eu>
To:	Benjamin Tissoires <benjamin.tissoires@...hat.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jiri Kosina <jkosina@...e.cz>,
	Ping Cheng <pinglinux@...il.com>,
	Jason Gerecke <killertofu@...il.com>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH] Input - wacom: update the ABI doc according to latest
 changes


Quoting Benjamin Tissoires <benjamin.tissoires@...hat.com>:

> Now the devices show up under hid no matter the connection. So update the
> sysfs path to the shortest and common one.
> The ABI has also been unified regarding the OLEDs, but Bluetooth handle
> only 1-bit images instead of 4.
>
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@...hat.com>
> ---
>
> Guys,
>
> by updating this and working on the g-s-d client side for OLEDs, I think now
> that we should also keep the oled*_img for Bluetooth and implement this file
> for USB too. The user space code gets messy quite fast due to the need to
> support old and new kernels, whereas if we handle the scrambling in  
> the kernel,
> it should be quite straightforward.
> Of course, we have to keep the current button<n>_rawimg for backward
> compatibility.
[..]
Hi Benjamin,
For whatever it's worth, you have my vote for scrambling for usb/bt in  
the kernel.
I'm not sure about requirement for backward compatibility (the user space will
be broken anyway).

I proposed it a while ago [1]

[1] http://www.gossamer-threads.com/lists/linux/kernel/1593583

Regards,
Przemo Firszt

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/