From: Ian Kumlien <pomac@vapor.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [2.6.8 ->] Problems, hci_usb dosn't work.
Date: Wed, 22 Sep 2004 20:49:30 +0200 [thread overview]
Message-ID: <1095878969.3211.23.camel@big> (raw)
In-Reply-To: <1095878303.6223.93.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
On Wed, 2004-09-22 at 20:38, Marcel Holtmann wrote:
> Hi Ian,
>
> > > this problem was reported two or three times, but I am unable to
> > > reproduce it with my USB 2.0 host controllers.
> >
> > ohci_hcd 0000:00:02.1: nVidia Corporation nForce2 USB Controller (#2)
> > ohci_hcd 0000:00:02.1: irq 185, pci mem f8818000
> > ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
>
> your IRQ looks very weird. I have never seen an IO-APIC system assigning
> IRQ 185 to any device. Does any other USB device works in conjunction
> with this controller?
2 joysticks, one 6in1 card reader and one muvodrive, it all works.
And, it registers the device correctly it just can't read from it.
And yeah i know, it's part of the nvidia workaround:
cat /proc/interrupts
CPU0
0: 91522201 XT-PIC timer
1: 17141 IO-APIC-edge i8042
8: 4 IO-APIC-edge rtc
9: 0 IO-APIC-level acpi
14: 341508 IO-APIC-edge ide0
15: 1917703 IO-APIC-edge ide1
177: 0 IO-APIC-level ohci_hcd
185: 0 IO-APIC-level ohci_hcd
193: 347701 IO-APIC-level ehci_hcd
201: 4266340 IO-APIC-level EMU10K1
209: 3869397 IO-APIC-level eth0
217: 11455874 IO-APIC-level nvidia
NMI: 8253
LOC: 91523920
ERR: 0
MIS: 0
hurrm ohci_hcd should have data... hurrrm, it might be LKML related
after all.. =P
(I might have left the experimental 'ohci' support in ehci on in this
kernel.)
> > What controller do you use? and what usb1.1 driver?
>
> I use a NEC controller with an OHCI for USB 1.1 stuff.
Heh ok
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-22 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 22:50 [Bluez-devel] [2.6.8 ->] Problems, hci_usb dosn't work Ian Kumlien
2004-09-22 8:47 ` Marcel Holtmann
2004-09-22 18:26 ` Ian Kumlien
2004-09-22 18:29 ` Marcel Holtmann
2004-09-22 18:32 ` Ian Kumlien
2004-09-22 18:38 ` Marcel Holtmann
2004-09-22 18:49 ` Ian Kumlien [this message]
2004-09-22 18:52 ` Marcel Holtmann
2004-09-22 19:20 ` Ian Kumlien
2004-09-22 19:26 ` Marcel Holtmann
2004-09-22 21:51 ` Ian Kumlien
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=1095878969.3211.23.camel@big \
--to=pomac@vapor.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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