From: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
To: Aivils Stoss <aivils-zFrTw0b2IqLyG1zEObXtfA@public.gmane.org>,
lud <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Samuel Thibault
<samuel.thibault-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jkosina-AlSwsSmVLrQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linuxconsole-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PROBLEM: USB keyboards works only 4 per PC host port
Date: Thu, 14 Aug 2008 18:49:48 -0700 [thread overview]
Message-ID: <20080814184948.093d2cad.rdunlap@xenotime.net> (raw)
In-Reply-To: <200808100408.37473.aivils-zFrTw0b2IqLyG1zEObXtfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Sun, 10 Aug 2008 04:08:37 +0100 Aivils Stoss wrote:
> On Saturday 09 August 2008 11:42:26 am Samuel Thibault wrote:
> > Aivils Stoss, le Fri 08 Aug 2008 07:02:24 +0100, a écrit :
> > > I suppose this is Linux kernel bug because i test keyboards under
> > > Windows, which support any schema of cascading of usb hubs.
> >
> > On the very same machine and hubs?
>
> Yes, on same machine. Under Windows i don't have evdev interface,
> checked only how keypress go to console.
> Of course to repeat a try You must have at least 5 keyboards and
> 1 7-port or 2 4-port hubs and kernel 2.6.22 and above. I allways
> got result - 5th, 6th, 7th keyboard does not send events to console
> or evdev.
[adding linux-usb mailing list]
Hi,
I finally got 5 USB keyboards together along with 2 hubs.
I daisy-chained the hubs and connected 1 keyboard to the hub that is
on the notebook computer USB port, then I connected 4 keyboards to the
second hub. They all worked for me, meaning that I can type on all of
them and have their characters show up on my console.
I'm testing with 2.6.7-rc2.
'usbtree' output of the USB subsystem is attached.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
[-- Attachment #2: usb-kbds.txt --]
[-- Type: text/plain, Size: 1890 bytes --]
/: Bus 05.Port 1: Dev 1, Class=root_hub, Drv=uhci_hcd/2p, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Drv=uhci_hcd/2p, 12M
|_ Port 1: Dev 2, If 0, Prod=Microsoft IntelliMouse® Explorer, Class=HID, Drv=usbhid, 1.5M
|_ Port 2: Dev 3, If 0, Prod=Generic USB Hub, Class=hub, Drv=hub/4p, 12M
|_ Port 1: Dev 8, If 0, Prod=Mobility USB EasiDock 200, Class=hub, Drv=hub/9p, 12M
|_ Port 1: Dev 17, If 0, Prod=API USB KB HUB, Class=hub, Drv=hub/3p, 12M
|_ Port 1: Dev 18, If 0, Prod=API USB KB HUB, Class=HID, Drv=usbhid, 12M
|_ Port 2: Dev 19, If 0, Prod=, Class=HID, Drv=usbhid, 1.5M
|_ Port 2: Dev 14, If 0, Prod=USB Keyboard, Class=HID, Drv=usbhid, 1.5M
|_ Port 2: Dev 14, If 1, Prod=, Class=HID, Drv=usbhid, 1.5M
|_ Port 3: Dev 13, If 0, Prod=USB Multimedia Keyboard, Class=HID, Drv=usbhid, 1.5M
|_ Port 3: Dev 13, If 1, Prod=, Class=HID, Drv=usbhid, 1.5M
|_ Port 4: Dev 11, If 0, Prod=Dell USB Keyboard Hub, Class=hub, Drv=hub/3p, 12M
|_ Port 1: Dev 12, If 0, Prod=Dell USB Keyboard, Class=HID, Drv=usbhid, 12M
|_ Port 1: Dev 12, If 1, Prod=, Class=HID, Drv=usbhid, 12M
|_ Port 8: Dev 9, If 0, Prod=Mobility PS/2 Keyboard And Mouse I/F, Class=HID, Drv=usbhid, 12M
|_ Port 9: Dev 10, If 0, Prod=Mobility USB Serial Converter, Class=vend., Drv=none, 12M
|_ Port 2: Dev 15, If 0, Prod=Multimedia Keyboard Hub, Class=hub, Drv=hub/3p, 12M
|_ Port 1: Dev 16, If 0, Prod=Multimedia Keyboard Hub, Class=HID, Drv=usbhid, 12M
|_ Port 1: Dev 16, If 1, Prod=, Class=HID, Drv=usbhid, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Drv=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Drv=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Drv=ehci_hcd/8p, 480M
next prev parent reply other threads:[~2008-08-15 1:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 6:02 PROBLEM: USB keyboards works only 4 per PC host port Aivils Stoss
2008-08-09 10:42 ` Samuel Thibault
2008-08-10 3:08 ` Aivils Stoss
[not found] ` <200808100408.37473.aivils-zFrTw0b2IqLyG1zEObXtfA@public.gmane.org>
2008-08-15 1:49 ` Randy Dunlap [this message]
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
[not found] ` <200808191527.06945.aivils-zFrTw0b2IqLyG1zEObXtfA@public.gmane.org>
2008-08-19 15:03 ` Alan Stern
2008-08-19 15:19 ` Randy Dunlap
[not found] ` <20080819081936.37fef673.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2008-08-19 15:23 ` Jiri Kosina
2008-08-19 17:55 ` Dmitry Torokhov
2008-08-20 5:40 ` Aivils Stoss
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 21:06 juanslayton-QP1aEjBt37AFQeE35raUng
2008-08-19 16:40 juanslayton
[not found] ` <25da0a65dd8a41208a8a0c0a.20080819094057.whnafynlgba-2RFepEojUI1A/VoSMG3fsAVB4TfmtpSe@public.gmane.org>
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=20080814184948.093d2cad.rdunlap@xenotime.net \
--to=rdunlap-/uha2rfvqtnk1umjsbkqmq@public.gmane.org \
--cc=aivils-zFrTw0b2IqLyG1zEObXtfA@public.gmane.org \
--cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxconsole-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=samuel.thibault-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).