On 4/16/07, Bjorn Helgaas <bjorn.helgaas@xxxxxx> wrote:
On Monday 16 April 2007 13:59, marco wrote: > ... It is still a problem which renders the > pen unusable after a suspend. > I am happy to run any tests you need. > Attatched are a dmesg right after a reboot when the pen is working > dmesg.wpen and another dmesg after I suspend the laptop and the pen no > longer works. Here's your trackpoint device: [17179584.620000] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [17179584.640000] input: TPPS/2 IBM TrackPoint as /class/input/input2
This is trackpoint (small rubber-head stick in the middle of laptop keyboard) that has nothing to do with Wacom tablet.
After resume, it looks like it's associated with a different input device: [17179770.968000] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [17179770.984000] input: TPPS/2 IBM TrackPoint as /class/input/input4 I'm sure that alone would be enough to confuse X.
No, it should be fine as long as /dev/input/mice is used.
It seems a bit strange that the device is associated differently after resume, but I don't know enough about input drivers to know whether that's by design or not.
It should not change input devices, I would like to see output of boot and suspend/resume cycle with "i8042.debug log_buf_len=131072" kernel boot options.
And I can't figure out what device that really is. For some reason, I thought it was ttyS0, but you seem to be using drivers/input/mouse/trackpoint.c, which looks like PS/2 stuff, not serial. And the wiki you referenced mentions /dev/wacom. I have no idea how that's wrapped up with this, although drivers/usb/input/wacom* is all USB stuff, and I assume your trackpoint is not a USB device (or is it?)
As far as I understand Marco has a serial Wacom table. There is no in-kernel driver for serial wacoms, they are handled entirely in userspace (X). -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
