public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Schmidt <schmidt@nue.et-inf.uni-siegen.de>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave
Date: Mon, 06 Sep 2004 10:30:26 +0200	[thread overview]
Message-ID: <1094459425.5145.19.camel@notepaq> (raw)
In-Reply-To: <413B18F9.6010101@nue.et-inf.uni-siegen.de>

Hi Michael,

> I'm experiencing the following behavior with BlueZ and L2CAP:
> 
> After establishing an L2CAP connection between two nodes, only the 
> master of this connection is still able to:
> 
> - perform periodic device inquiries (i.e. search other devices
>    in 'Periodic_Inquiry_Mode')	
> - perform inquiry scans (i.e. be visible for other searching devices)
> 
> However, I would like to be able to do this as slave as well (at least, 
> to perform inquiry scans as slave).
> 
> Now I'm wondering whether:
> 
> - this is a restriction of BlueZ		or
> - this is a restriction of my BT chipsets	or
> - this is a restriction of Bluetooth		or
> - I'm doing (configuring) something wrong...
> 
> My environment:
> 
> SuSE Linux 9.0: kernel 2.4.21, bluez-libs 2.4, bluez-utils-2.3
> 
> I have tested and verified this behavior with the BrainBoxes BL-500 and
> BL-554 adapters.
> I'd be very grateful if someone of you could shed some light on this topic.

this sounds like a chip limitation. What does "hciconfig -a" say?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-09-06  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 13:47 [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-05 17:53 ` Collin R. Mulliner
2004-09-06  8:30 ` Marcel Holtmann [this message]
2004-09-06  8:50   ` Michael Schmidt
2004-09-06  9:17     ` Marcel Holtmann
2004-09-06 10:38       ` [Bluez-users] general question on the procedure of BlueZ Johannes
2004-09-06 11:21         ` Johannes
2004-09-07  7:56           ` Johannes
2004-09-06 11:43       ` [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-06  8:37 ` Xavier Garreau

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=1094459425.5145.19.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=schmidt@nue.et-inf.uni-siegen.de \
    /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