From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fwd: Re: wait_for_sysfs needs an update to handle the device
Date: Sat, 06 Nov 2004 18:02:13 +0000 [thread overview]
Message-ID: <1099764133.15054.36.camel@localhost.localdomain> (raw)
In-Reply-To: <1098925336.41804518e7430@mail.utca.hu>
On Sat, 2004-11-06 at 09:08 -0800, Greg KH wrote:
> On Sat, Nov 06, 2004 at 08:51:26AM +0100, Csan wrote:
> > Yes. The reason I've waited a few days before I reply to this has been that
> > 2.6.9 hit the unstable repository and now I am running 2.6.9... and no
> > improvement around here:
> >
> > # ls -l /sys/bus/usb/devices
> > -r--r--r-- 1 root root 0 2004-11-06 07:05 /sys/bus/usb/devices
>
> Are you sure you actually _have_ a usb controller on this machine? It
> sure doesn't look like it.
Looks like a "normal" Intel controller. In earlier mails Csan posted
this:
# lspci
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02)
# dmesg | grep hcd
ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
ehci_hcd 0000:00:1d.7: irq 201, pci mem e0a5b000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
uhci_hcd 0000:00:1d.0: irq 177, io base 00001800
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
uhci_hcd 0000:00:1d.1: irq 185, io base 00001820
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
uhci_hcd 0000:00:1d.2: irq 193, io base 00001840
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
# /sys/bus/usb/devices:
T: Bus\x03 Lev\x01 Prnt\x01 Port\0 Cnt\x01 Dev#= 3 Spd\x12 MxCh= 0
D: Ver= 1.10 Cls‡(unk. ) Sub\x01 Prot\x01 MxPSd #Cfgs= 1
P: Vendor
12 ProdID\001 Rev= 5.25
C:* #Ifs= 3 Cfg#= 1 Atr¿ MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: AdÅ(I) Atr\x03(Int.) MxPS= 16 Ivl=1ms
E: Ad\x02(O) Atr\x02(Bulk) MxPS= 64 Ivl=0ms
E: AdÇ(I) Atr\x02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 0 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 9 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 17 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 25 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 33 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls‡(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E: Ad\x03(O) Atr\x01(Isoc) MxPS= 49 Ivl=1ms
E: AdÉ(I) Atr\x01(Isoc) MxPS= 49 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls˛(app. ) Sub\x01 Prot\0 Driver=(none)
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-11-06 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
2004-10-28 21:31 ` Kay Sievers
2004-10-28 23:41 ` Csan
2004-10-28 23:56 ` Kay Sievers
2004-10-29 1:37 ` Csan
2004-10-30 3:23 ` Kay Sievers
2004-10-30 16:00 ` Greg KH
2004-10-31 0:35 ` Kay Sievers
2004-11-06 7:51 ` Csan
2004-11-06 17:08 ` Greg KH
2004-11-06 18:02 ` Kay Sievers [this message]
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=1099764133.15054.36.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).