From: Valdis.Kletnieks@vt.edu
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jiri Kosina <jkosina@suse.cz>,
Greg Kroah-Hartman <gregkh@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: Wonkiness with keyboard adapter - not sure if it's in USB or input systems
Date: Tue, 26 Apr 2011 15:12:16 -0400 [thread overview]
Message-ID: <23191.1303845136@localhost> (raw)
In-Reply-To: Your message of "Tue, 26 Apr 2011 14:55:57 EDT." <Pine.LNX.4.44L0.1104261453300.2035-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On Tue, 26 Apr 2011 14:55:57 EDT, Alan Stern said:
> On Tue, 26 Apr 2011 Valdis.Kletnieks@vt.edu wrote:
> > Bus 001 Device 006: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
> Have you tried testing the adapter by plugging it in after the system
> is running?
It works fine at the Grub screen.
It *doesn't* work for the kernel when it initially starts up, even though a few
seconds ago the hardware worked just fine.
It *does* work after I've unplugged/replugged it - I've tested both the USB
side and the PS2 side, in either case it starts working.
I'm not sure what difference "plug it in after it's running" and "unplug/
replug" will have. I suppose I could test that, but I'm suspecting the results
will be "it works fine after plugging it in once the kernel is up".
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-04-26 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 15:47 Wonkiness with keyboard adapter - not sure if it's in USB or input systems Valdis.Kletnieks
2011-04-26 18:55 ` Alan Stern
2011-04-26 19:12 ` Valdis.Kletnieks [this message]
2011-04-26 21:29 ` Jiri Kosina
2011-04-27 0:17 ` Valdis.Kletnieks
2011-04-27 17:23 ` Alan Stern
2011-04-27 17:27 ` Dr. David Alan Gilbert
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=23191.1303845136@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).