public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Ian Kumlien <pomac@vapor.com>
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:52:47 +0200	[thread overview]
Message-ID: <1095879167.6223.104.camel@pegasus> (raw)
In-Reply-To: <1095878969.3211.23.camel@big>

Hi Ian,

> > > 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.

are these devices all USB 2.0 capable? If yes, then they are handled by
the ehci_hcd host controller driver.

> 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.)

Check that first and then report it to the Linux USB mailing list. It is
more an USB issue then LKML related.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-09-22 18:52 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
2004-09-22 18:52             ` Marcel Holtmann [this message]
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=1095879167.6223.104.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=pomac@vapor.com \
    /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