From: "siddhant tewari" <siddhant.tewari@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] problem using two bluetooth dongles together
Date: Tue, 17 Apr 2007 10:26:27 +0530 [thread overview]
Message-ID: <57c68ddc0704162156p342351e0m402325c729c19662@mail.gmail.com> (raw)
In-Reply-To: <1176744531.30165.40.camel@aeonflux.holtmann.net>
[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]
hi Marcel,
Thanks for the advice , will surely port to 2.6 kernel.
regards
siddhant
On 4/16/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Siddhant,
>
> > I will try to upgrade to 2.6 kernel but since this is arm Single
> > Board Computer , i am not sure about the effort and time that would
> > be required to do so.
> >
> > I have another observation to share with you .
> >
> > When using two dongle , if i put hci0 down by hciconfig hci0 down
> > and then put hci1 up by hciconfig hci1 up
> > then hciconfig returns correct address for the second adapter as well.
> >
> > Also if i try to put hci1 up without putting hci0 down then same
> > thing
> > ----- "cannot contact hci1 connection timed out" message appears.
> >
> > Please reply if you can give me some hints about whats happening after
> > going through the above observation.
>
> I am pretty sure that is the USB subsystem. Since when you down the
> adapter all URBs will be canceled. So you can try to change the
> constants for the number of URBs in hci_usb.h and recompile your kernel.
> You can also try to disable ISOC transfers (SCO support for the driver)
> and see if that takes the bandwidth pressure from the USB bus.
>
> However, the 2.6 USB subsystem is really the way to go. No effort on
> porting to 2.6 is wasted.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 2533 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-04-17 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 13:08 [Bluez-users] problem using two bluetooth dongles together siddhant tewari
2007-04-16 13:45 ` Marcel Holtmann
2007-04-16 14:41 ` siddhant tewari
2007-04-16 15:36 ` Marcel Holtmann
2007-04-16 16:04 ` siddhant tewari
2007-04-16 17:28 ` Marcel Holtmann
2007-04-17 4:56 ` siddhant tewari [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=57c68ddc0704162156p342351e0m402325c729c19662@mail.gmail.com \
--to=siddhant.tewari@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/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