From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Aivils Stoss <aivils@latnet.lv>,
stern@rowland.harvard.edu, lud <linux-usb@vger.kernel.org>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxconsole-dev@lists.sourceforge.net
Subject: Re: PROBLEM: USB keyboards works only 4 per PC host port
Date: Tue, 19 Aug 2008 13:55:58 -0400 [thread overview]
Message-ID: <20080819135447.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0808191721560.18058@jikos.suse.cz>
On Tue, Aug 19, 2008 at 05:23:07PM +0200, Jiri Kosina wrote:
> On Tue, 19 Aug 2008, Randy Dunlap wrote:
>
> > > 2.6.22-1-mepis-smp
> > > Quite stable. Have oops sometime inside evdev. Support up to 16
> > > USB keyboards, where 4 hubs are plugged into PC and 4 keyboards on
> > > each hub. Any hub cascade support only 4 keyboards, where 5th or more
> > > is registered but don't send input events. Oops inside evdev , when
> > > USB keyboard unplugged. No slow down even all USB keyboards does
> > > not work properly. My be this one support more than 16 keyboards, but
> > > i don't have PC USB ports enough.
> > Has the evdev oops been reported and/or fixed? I think that we would
> > prefer to fix that soonish.
>
> We haven't seen the respective oops yet, or have I missed it?
>
> I'd bet it is fixed in newer kernels by patches that introduce proper
> locking into evdev code.
>
If evdev (or any other part of the input sybsystem) still oopses in
2.6.26 and 2.6.27 I would like to see that oops very much.
--
Dmitry
next prev parent reply other threads:[~2008-08-19 17:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 6:02 Aivils Stoss
2008-08-09 10:42 ` Samuel Thibault
2008-08-10 3:08 ` Aivils Stoss
2008-08-15 1:49 ` Randy Dunlap
2008-08-18 11:12 ` Aivils Stoss
2008-08-18 15:14 ` Jiri Kosina
2008-08-18 15:14 ` Randy Dunlap
2008-08-19 9:57 ` Aivils Stoss
2008-08-19 15:03 ` Alan Stern
2008-08-19 15:19 ` Randy Dunlap
2008-08-19 15:23 ` Jiri Kosina
2008-08-19 17:55 ` Dmitry Torokhov [this message]
2008-08-20 5:40 ` Aivils Stoss
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 21:06 juanslayton
2008-08-19 16:40 juanslayton
2008-08-19 18:21 ` Alan Stern
2008-08-19 19:12 ` David Brownell
2008-08-19 20:04 ` Alan Stern
2008-08-19 21:05 ` juanslayton
2008-08-02 6:05 Aivils Stoss
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=20080819135447.ZZRA012@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=aivils@latnet.lv \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
--cc=samuel.thibault@ens-lyon.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
all inboxes | Powered by JetHome®