Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 567056 - x11-drivers/xf86-input-wacom wrong postmessage about kernel option
Summary: x11-drivers/xf86-input-wacom wrong postmessage about kernel option
Status: RESOLVED DUPLICATE of bug 544712
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-28 23:53 UTC by Michael Gn. Gajda
Modified: 2015-12-07 11:25 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Gn. Gajda 2015-11-28 23:53:15 UTC
x11-drivers/xf86-input-wacom (version 0.24 up to ~0.32.0) reports:

 * If you use a USB Wacom tablet, you need to enable support in your kernel
 *   Device Drivers --->
 *     Input device support --->
 *       <*>   Event interface
 *       [*]   Tablets  --->
 *         <*>   Wacom Intuos/Graphire tablet support (USB)


while the kernel option is actually:                                                                                                         │  
 * CONFIG_HID_WACOM:
 * 
 * Say Y here if you want to use the USB or BT version of the Wacom Intuos
 * or Graphire tablet.
 * 
 * To compile this driver as a module, choose M here: the
 * module will be called wacom.
 * 
 * Symbol: HID_WACOM [=y]
 * Type  : tristate
 * Prompt: Wacom Intuos/Graphire tablet support (USB)
 *   Location:
 *     -> Device Drivers
 *       -> HID support
 *         -> HID bus support (HID [=y])
 *           -> Special HID drivers
 *   Defined at drivers/hid/Kconfig:813
 *   Depends on: INPUT [=y] && HID [=y]
 *   Selects: POWER_SUPPLY [=y] && NEW_LEDS [=y] && LEDS_CLASS [=y]


At least in kernel-4.0.0 upwards. Not sure about earlier kernels.
Comment 1 Chí-Thanh Christopher Nguyễn gentoo-dev 2015-12-07 11:25:22 UTC

*** This bug has been marked as a duplicate of bug 544712 ***