public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bram Jansen <bramsbox@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: max 16 hci devices on usb 2.0
Date: Sat, 16 Jan 2010 17:44:23 -0800	[thread overview]
Message-ID: <1263692663.5591.54.camel@localhost.localdomain> (raw)
In-Reply-To: <BABDE7A517704C42BC70E146983535B6@radon>

Hi Bram,

> I have a question regarding the connection of 16 hci devices to a linux box.
> I've been looking around for quite some time and I was not able to find
> something useful, therefore I hope anyone of you guys is able to point me in
> the right direction.
> 
> We have used quite a few kernel versions to try to connect 16 hci devices to
> one system with usb 2.0 enabled.
> This gives a problem after 7 devices. Devices hci7-hci15 give timeouts and
> errors after initializing.
> 
> We solved this problem by disabling ehci in the kernel, so the bluetooth had
> to use usb 1.1 (ohci)
> with these settings it works without any problems and all 16 hci devices are
> initialized properly after insertion/boot
> 
> now there has come the need for usb 2.0 on the same system.
> 
> Is there a known solution for this issue?

you better ask such questions on the Linux USB mailing list since I have
no idea why sometimes the hubs causes problems.

As a side note. The 16 HCI devices limit is not fixed actually. You can
just compile your own libbluetooth with a different limit. The kernel
supports as many devices as you have memory :)

Regards

Marcel



      reply	other threads:[~2010-01-17  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 23:35 max 16 hci devices on usb 2.0 Bram Jansen
2010-01-17  1:44 ` Marcel Holtmann [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=1263692663.5591.54.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bramsbox@gmail.com \
    --cc=linux-bluetooth@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