From: Marcel Holtmann <marcel@holtmann.org>
To: "Collin R. Mulliner" <collin@betaversion.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] patch for: RFComm dynamic channel allocation
Date: Thu, 08 Jul 2004 19:37:11 +0200 [thread overview]
Message-ID: <1089308231.4857.45.camel@pegasus> (raw)
In-Reply-To: <20040708165219.16a1d6db@coredump>
Hi Collin,
> just found and fixed the problem with dynamic rfcomm channel allocation.
> My code binds to a specific local bdaddr, the rfcomm tool binds to ANY.
> This case was not handled correctly. The fix is simple, see attachment.
I don't get the point of your fix, because bind() to a specific BD_ADDR
and to BDADDR_ANY are totally different and can result in different
dynamic channel allocations.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-08 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 14:52 [Bluez-devel] patch for: RFComm dynamic channel allocation Collin R. Mulliner
2004-07-08 17:37 ` Marcel Holtmann [this message]
2004-07-08 18:08 ` Collin R. Mulliner
2004-07-08 18:36 ` Marcel Holtmann
[not found] ` <20040709012301.5a966440@coredump>
2004-07-09 10:15 ` Marcel Holtmann
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=1089308231.4857.45.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=collin@betaversion.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.