From: Stephan Mueller <smueller@chronox.de>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Mattia Dongili <malattia@linux.it>,
platform-driver-x86@vger.kernel.org,
Jiri Kosina <jkosina@suse.cz>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: Sony Vaio Duo 11: getting middle mouse button to work
Date: Fri, 31 Jan 2014 05:31:53 +0100 [thread overview]
Message-ID: <13914184.mVhhUrzN60@myon.chronox.de> (raw)
In-Reply-To: <CAN+gG=HAXE4LT_tN+3tE8-T_L5g+2HAE35CN+z8KCEQcmJ=JWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Am Donnerstag, 30. Januar 2014, 22:50:25 schrieb Benjamin Tissoires:
Hi Benjamin,
> > Can you please help me how to do that? I install Windows in a KVM with
> > the mouse device as a USB-passthrough device -- shall I detach the Linux
> > USB driver?
>
> No, you don't have to detach the Linux USB driver (it's done for you
> by KVM IIRC).
Correct, libvirtd is the one that detaches the driver when I start the VM.
>
> > Now, shall I use hid-recorder on that device or rather usbmon while
> > Windows is booting?
>
> usbmon is the tool you need. hid-recorder will not work because the
> hid subsystem will be disconnected as the device is used by Windows.
>
> You can even use wireshark now. It gives you a nice interface and
> interpretation of the USB packets :)
Please see attached for the USB sniffing on the USB bus with the Crucialtec
touch pad when Windows starts up and shuts down. To drive the device, Windows
uses the Crucialtec driver according to its device settings display.
The attached log contains the log information for the mouse (device 001:005)
and the USB bridge (device 001:002). I cut out the listing for the touch pad
which is also attached to that bridge.
The strange thing, however, is the following: the mouse works in Windows when
I do not sniff on the USB bus using usbmon. But as soon as I start sniffing,
it does not work any more.
Is that log helpful?
Ciao
Stephan
--
| Cui bono? |
[-- Attachment #2: sony-vaio-duo-11-usbsniff.bz2 --]
[-- Type: application/x-bzip, Size: 1338 bytes --]
next prev parent reply other threads:[~2014-01-31 4:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 16:21 Sony Vaio Duo 11: getting middle mouse button to work Stephan Mueller
2014-01-25 3:17 ` Mattia Dongili
2014-01-25 4:51 ` Stephan Mueller
2014-01-29 14:53 ` Benjamin Tissoires
2014-01-29 14:59 ` Stephan Mueller
2014-01-29 15:07 ` Benjamin Tissoires
2014-01-30 3:48 ` Stephan Mueller
2014-01-30 21:44 ` Benjamin Tissoires
2014-01-30 22:07 ` Stephan Mueller
2014-01-31 3:50 ` Benjamin Tissoires
2014-01-31 4:31 ` Stephan Mueller [this message]
2014-01-31 16:20 ` Benjamin Tissoires
2014-01-31 21:02 ` Stephan Mueller
2016-08-11 21:27 Stefan Seidel
2016-08-12 9:29 ` Benjamin Tissoires
2016-08-12 19:41 ` Stefan Seidel
2016-08-12 20:02 ` Stefan Seidel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13914184.mVhhUrzN60@myon.chronox.de \
--to=smueller@chronox.de \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=malattia@linux.it \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.