Bug 1539238 - Need this patch to use CTL-472 Wacom Tablet
Summary: Need this patch to use CTL-472 Wacom Tablet
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-27 03:07 UTC by Mikhail Golubev
Modified: 2018-03-28 22:58 UTC (History)
19 users (show)

Fixed In Version: kernel-4.14.16-200.fc26 kernel-4.14.16-300.fc27
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-02 16:56:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mikhail Golubev 2018-01-27 03:07:26 UTC
Description of problem:

  Wacom Tablet CTL-472/672 not recognized by kernel driver but with the patch in additional info works fine

Version-Release number of selected component (if applicable):
  4.13.9-300.fc27.x86_64 and later

How reproducible:
  always distro independent

Steps to Reproduce:
1. plug in the Tablet USB cable
2. type dmesg as root
3. see something bad


Actual results:
[   92.990626] usb 2-4: USB disconnect, device number 4
[   95.460038] usb 2-4: new full-speed USB device number 5 using ohci-pci
[   95.669098] usb 2-4: New USB device found, idVendor=056a, idProduct=037a
[   95.669102] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   95.669106] usb 2-4: Product: CTL-472
[   95.669109] usb 2-4: Manufacturer: Wacom Co.,Ltd.
[   95.669112] usb 2-4: SerialNumber: 7HE00L1027967
[   95.686257] input input29: Absolute device without dev->absinfo, refusing to register
[   95.686281] wacom: probe of 0003:056A:037A.0006 failed with error -22
[   95.694514] wacom 0003:056A:037A.0007: Unknown device_type for 'Wacom Co.,Ltd. CTL-472'. Ignoring.

  The Tablet does not work as pointer device


Expected results:
[ 1042.259971] input: Wacom One by Wacom S Pen as /devices/pci0000:00/0000:00:04.0/usb2/2-4/2-4:1.0/0003:056A:037A.0006/input/input35
[ 1042.263148] wacom 0003:056A:037A.0006: hidraw3: USB HID v1.10 Mouse [Wacom Co.,Ltd. CTL-472] on usb-0000:00:04.0-4/input0

  The Tablet works as pointer device


Additional info:

 I've got CTL-472 Wacom Tablet and I tested this simple patch below and it works so I can draw in inkscape with it

diff --git a/drivers/hid/wacom_wac.c b/drivers/hid/wacom_wac.c
index aa692e28b2cd..5f932ddcdc49 100644
--- a/drivers/hid/wacom_wac.c
+++ b/drivers/hid/wacom_wac.c
@@ -4376,6 +4376,12 @@  static const struct wacom_features wacom_features_0x360 =
 static const struct wacom_features wacom_features_0x361 =
 	{ "Wacom Intuos Pro L", 62200, 43200, 8191, 63,
 	  INTUOSP2_BT, WACOM_INTUOS3_RES, WACOM_INTUOS3_RES, 9, .touch_max = 10 };
+static const struct wacom_features wacom_features_0x37A =
+	{ "Wacom One by Wacom S", 15200, 9500, 2047, 63,
+	  BAMBOO_PEN, WACOM_INTUOS_RES, WACOM_INTUOS_RES };
+static const struct wacom_features wacom_features_0x37B =
+	{ "Wacom One by Wacom M", 21600, 13500, 2047, 63,
+	  BAMBOO_PEN, WACOM_INTUOS_RES, WACOM_INTUOS_RES };
 
 static const struct wacom_features wacom_features_HID_ANY_ID =
 	{ "Wacom HID", .type = HID_GENERIC, .oVid = HID_ANY_ID, .oPid = HID_ANY_ID };
@@ -4544,6 +4550,8 @@  const struct hid_device_id wacom_ids[] = {
 	{ USB_DEVICE_WACOM(0x343) },
 	{ BT_DEVICE_WACOM(0x360) },
 	{ BT_DEVICE_WACOM(0x361) },
+	{ USB_DEVICE_WACOM(0x37A) },
+	{ USB_DEVICE_WACOM(0x37B) },
 	{ USB_DEVICE_WACOM(0x4001) },
 	{ USB_DEVICE_WACOM(0x4004) },
 	{ USB_DEVICE_WACOM(0x5000) },

Comment 1 Laura Abbott 2018-01-27 09:48:17 UTC
That's great you have a patch. Please work with the upstream maintainers to get it merged.

Comment 2 Mikhail Golubev 2018-01-27 13:02:30 UTC
(In reply to Laura Abbott from comment #1)
> That's great you have a patch. Please work with the upstream maintainers to
> get it merged.

OK Actually It already there and will be merged in 4.16

https://patchwork.kernel.org/patch/10133291/

How long will it take to get it in f27?

Comment 3 Laura Abbott 2018-01-27 15:08:41 UTC
Okay, I went ahead and applied it to F26/F27 because it was accepted. This bug will be updated when it shows up in an F26/F27 build.

Comment 4 Mikhail Golubev 2018-01-27 21:30:49 UTC
(In reply to Laura Abbott from comment #3)
> Okay, I went ahead and applied it to F26/F27 because it was accepted. This
> bug will be updated when it shows up in an F26/F27 build.

Great! Thanx!

Comment 5 Fedora Update System 2018-02-01 04:16:14 UTC
kernel-4.14.16-300.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d09a73ce72

Comment 6 Fedora Update System 2018-02-01 04:17:37 UTC
kernel-4.14.16-200.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d82b617d6c

Comment 7 Fedora Update System 2018-02-01 19:09:40 UTC
kernel-4.14.16-200.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d82b617d6c

Comment 8 Fedora Update System 2018-02-01 19:31:00 UTC
kernel-4.14.16-300.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d09a73ce72

Comment 9 Fedora Update System 2018-02-02 16:56:49 UTC
kernel-4.14.16-200.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2018-02-02 17:39:26 UTC
kernel-4.14.16-300.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 elf00 2018-03-28 22:58:43 UTC
How to install this Patch?


Note You need to log in before you can comment on or make changes to this bug.