public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Multi Dongle Problem
Date: Sat, 16 Jun 2007 09:43:35 +0200	[thread overview]
Message-ID: <1181979815.6846.71.camel@aeonflux.inter-touch.com> (raw)
In-Reply-To: <52222.190.30.202.149.1181668125.squirrel@www.y2knetworks.com.ar>

Hi,

> im making a program in C ... and was trying to use multi dongles ...
> this is the hcitool dev output:
> 
> Devices:
>         hci0    00:11:F6:0A:06:7B
>         hci1    00:11:F6:0A:06:63
> 
> and that i make in my program is this...
> 
> str2ba("00:11:F6:0A:06:7B",&bdaddr);
> dev_id = hci_get_route(&bdaddr);
> 
> but when u see the light of the dongles the hci1 is in use ...
> and the hci0 is in use when the program use sdp...

you have to give the source to sdp_connect().

> to solve this i make the link mode of hci0 MASTER ... but then dont care
> what i punt on the hci_get_route function... im making something wrong??

No. Never do that. It is wrong. The link mode is selecting a device.

> almost forgot... in some case the program finish with this error
> Failed to connect to SDP server: Interrupted system call ... what can be?...

Can't say that without seeing hcidump -X -V.

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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-06-16  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 17:08 [Bluez-devel] Multi Dongle Problem msaglietto
2007-06-16  7:43 ` 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=1181979815.6846.71.camel@aeonflux.inter-touch.com \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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