From: Otto Wyss <otto.wyss@orpatec.ch>
To: linux-kernel@vger.kernel.org
Subject: USB-Keyboard through an USB-Switchbox
Date: Fri, 28 Apr 2006 21:25:50 +0200 [thread overview]
Message-ID: <44526C3E.5080200@orpatec.ch> (raw)
I'm using now again a second computer with a single USB keyboard through
an USB switchbox. Switching between computers is equivalent to connect
and disconnect the USB keyboard rather often. After this
disconnect/connect I still happen to experience times when the USB stack
can't synchronize again, leaving me without access to the computer
(kernel 2.6.12-9). I since I've mentioned this already several years ago
I though this might be solved but it seems Linux isn't able to build a
state-of-the-art USB stack which is able to synchronize in _each_ case.
Is there anything I can do to help find out why the USB doesn't work? Is
there a log anywhere on they system?
O. Wyss
--
Cross-platform: http://wyoguide.sf.net/index.php?page=Cross-platform.html
next reply other threads:[~2006-04-28 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 19:25 Otto Wyss [this message]
2006-04-30 4:36 ` USB-Keyboard through an USB-Switchbox Greg KH
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=44526C3E.5080200@orpatec.ch \
--to=otto.wyss@orpatec.ch \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox