Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ag@new-media-artists.de
Cc: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Master, Slave and Maximal Peers Questions
Date: Sat, 17 Jan 2004 16:28:37 +0100	[thread overview]
Message-ID: <1074353316.2629.148.camel@pegasus> (raw)
In-Reply-To: <FJENILNPNAGPJMMDOKDCMEBHDMAA.ag@new-media-artists.de>

Hi Andreas,

> >I don't see any reason why you can't connect a third device into this
> >piconet. Run "hcidump -w <file>" for the third connection, so we can see
> >what happens on the HCI layer.
> 
> you where right, there is no problem with connecting more than two with
> rfcomm. I just saw "device or resource busy" from rfcomm often in my logs so
> i assumed it would be that reason but it wasnt. Now i have to find out what
> was the reason for this. Any what would be the most obvious reasons for
> this, if any?

what is the correct errno that would be returned? Run hcidump as I told
you.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-17 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15  6:13 [Bluez-devel] Master, Slave and Maximal Peers Questions Andreas Gaufer
2004-01-15 12:22 ` Marcel Holtmann
2004-01-17 14:36   ` AW: " Andreas Gaufer
2004-01-17 15:28     ` Marcel Holtmann [this message]
2004-01-21  9:07       ` Andreas Gaufer

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=1074353316.2629.148.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=ag@new-media-artists.de \
    --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