Linux bluetooth development
 help / color / mirror / Atom feed
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: Mon, 16 Apr 2007 20:11:15 +0530	[thread overview]
Message-ID: <57c68ddc0704160741y7399f051rd3aaf6fe885cd57c@mail.gmail.com> (raw)
In-Reply-To: <1176731130.30165.26.camel@aeonflux.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 1500 bytes --]

hi Marcel,
                 I am using using kernel 2.4.26.
                 cant find anything with dmesg output.

                 When trying to run hcid at the prompt i am getting message

                  Can't init device hci1 : Connection time out.

                 What can be the possible reasons for this ???

regards
siddhant


On 4/16/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi,
>
> >     I am using bluez on arm single board computer and i am facing this
> > strange problem.
> >
> > When i am using only one bluetooth dongle , hciconfig correctly
> > reports the bluetooth address of the dongle but when i insert a second
> > dongle then the second dongles bt address is reported as
> > 00:00:00:00:00:00 .
> >
> > Both the dongles individually work fine.
> >
> > Can anyone tell me what can be the cause for such a problem ????
>
> never tried it on ARM machines. Check the output of dmesg. Maybe your
> USB stack has a problem on ARM. Do you run the latest 2.6 kernel?
>
> 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: 2678 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

  reply	other threads:[~2007-04-16 14:41 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 [this message]
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

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=57c68ddc0704160741y7399f051rd3aaf6fe885cd57c@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