public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Kumlien <pomac@vapor.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	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:26:40 +0200	[thread overview]
Message-ID: <1095877600.3211.15.camel@big> (raw)
In-Reply-To: <1095842833.5762.27.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]

On Wed, 2004-09-22 at 10:47, Marcel Holtmann wrote:
> Hi Ian,
> 
> > Since some kernel version i can't exactly remember which, i have been
> > unable to use usb, i have tested with with 2.6.8 -> 2.6.9-rc2-bk7 and i
> > also applied your patches for 2.6.8.
> > 
> > I have 2 usb dongles, one old that did work once, and one new that seems
> > to be working like the older but it doesn't work with linux.
> > 
> > Both are based on the CSR chipset, here is the new ones entry from the
> > hw support list:
> > MSI MS-6967 CSR 1.1 hci_usb working Dave Beckett
> > 
> > Som logs from insertions:
> > usb 1-3.4: new full speed USB device using address 12
> > ehci_hcd 0000:00:02.2: qh f7e54780 (#0) state 1
> > hci_usb_intr_rx_submit: hci0 intr rx submit failed urb d968cd74 err -28
> > 
> > usb 1-4.4: new full speed USB device using address 13
> > ehci_hcd 0000:00:02.2: qh f7e54900 (#0) state 1
> > hci_usb_intr_rx_submit: hci1 intr rx submit failed urb d315eef4 err -28
> > 
> > both of these are connected to usb 2.0 hubs (this machine does usb 2.0)
> 
> this looks like an USB problem to me. Try to connect it to USB 1.1 ports
> and see if this works.

The problem is, this computer doesn't have a usb 1.1 port.
But it should basically fallback, and afair it worked with a cable
direct to the computer, i haven't tested that since... because i need
the hubs.

But if it indeed is a usb 1.1  vs 2.0 problem then it has to be
something broken in the kernel... Anyone else using this with usb 2.0?

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

  reply	other threads:[~2004-09-22 18:26 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 [this message]
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
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=1095877600.3211.15.camel@big \
    --to=pomac@vapor.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=bluez-users@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