From: Art Rothstein <art@mojo-working.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Role switch: Detecting, predicting, preventing
Date: Thu, 15 Feb 2007 15:30:53 -0800 [thread overview]
Message-ID: <45D4ED2D.7060706@mojo-working.com> (raw)
In-Reply-To: <1171527486.28302.14.camel@violet>
I have incorporated your hci_conn_info test into a minimal test case derived
from my application. You can find source, executable, and hcidump traces at
http://65.104.11.121/TwoAdapters . Both cases were run on the same desktop PC,
with the same two USB dongles. The client adapter was a Motorola PC850, and the
server an IOGear GBU211. Both run LM 1.2 on a member of the Broadcom 2035
family. The -386 traces were run with Ubuntu 2.6.17-11-386 installed on a hard
disk. The -generic traces were run with Ubuntu 2.6.17-10-generic, booted from
the Ubuntu 6.10 live CD. As before, hciconfig always reports SLAVE ACCEPT, and
the role change flows in the -386 case.
Thanks very much for your help.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-15 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 6:04 [Bluez-devel] Role switch: Detecting, predicting, preventing Art Rothstein
2007-02-15 8:18 ` Marcel Holtmann
2007-02-15 23:30 ` Art Rothstein [this message]
2007-03-02 17:35 ` Art Rothstein
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=45D4ED2D.7060706@mojo-working.com \
--to=art@mojo-working.com \
--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