All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problem with hci_usb
Date: Tue, 02 Mar 2004 21:03:14 +0000	[thread overview]
Message-ID: <4044F692.3080605@superbug.demon.co.uk> (raw)
In-Reply-To: <1078247120.9057.85.camel@localhost>

Nils Faerber wrote:
> Hi!
> I just found a quite strange problem with the hci_usb driver.
> We have a Fujitsu Siemens Lifebook with builtin Bluetooth here. This
> seems to be a CSR chipset connected via USB internally.
> The problem is that the chipset is set to SCO-PCM not SCO-HCI.
> Subsequently when SCO is enabled in the hci_usb driver something goes
> wrong and the usb-uhci driver constanly generates interrupts which are
> accounted to the UHCI and as ERR interrupts (in /proc/interrupts).
> Enabling debugging for USB does not produce anything new.
> What helped a lot is to disable the SCO option for the hci_usb driver.
> But this solution is quite unsatisfying since externally connected USB
> Bluetooth dongles would bow also not be able to use SCO over HCI even if
> they support it.
> 
> This is kernel 2.4.25 without additional patches.
> 
> The hci_usb in 2.6.3 must be somewhat different.
> It reports unsupported isochronous URBs (sorry, might be wrong, this is
> from my memory since I do not have 2.6.3 logs anymore) and disbled it at
> device startup. No more unnecessary interrupts and especially no ERR
> interrupts here.
> 
> So, are those changes also available as patch to fix the 2.4.25 driver?
> The current 2.4.25-mh1 patch at least does not seem to include a fix for
> this problem...
> 
> Apart from that, works like a charm! (Oh, I had to increase the USB
> hub.c DEBOUNCE_TIMEOUT from 400 to 1500 to make the device detect
> work...)
> 
> CU
>   nils faerber
> 

SCO support in bluez is still in development.
Once it works correctly in 2.6.x, someone might back port it to 2.4.x, 
but there is no point in back porting something until it is finished.
Everything you describe above is "known issues".

Cheers
James



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-03-02 21:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 17:05 [Bluez-devel] Problem with hci_usb Nils Faerber
2004-03-02 17:30 ` Marcel Holtmann
2004-03-02 18:42   ` Nils Faerber
2004-03-02 19:42     ` Marcel Holtmann
2004-03-02 21:03 ` James Courtier-Dutton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-02 21:47 Williams, Richard
2004-03-02 22:15 ` Marcel Holtmann
2004-03-03  0:52 ` James Courtier-Dutton
2004-03-03 12:50 Williams, Richard

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=4044F692.3080605@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=nils.faerber@kernelconcepts.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.