From: "zubiwat" <zubiwat@poczta.onet.pl>
To: "devel Bluetooth" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] RFCOMM problem
Date: Fri, 2 Apr 2004 01:12:34 +0200 [thread overview]
Message-ID: <008a01c4183e$d14649a0$fcca010a@lysydziadek> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Hi
I'm connected through L2CAP and what should I send now to connect RFCOMM. I know that it should be SABM and I should wait for UA but how to do this?
Where is a command to do this and how it looks like. RFCOMM packets are insight L2CAP as a command?
Can anyone tell me what it's like and howto make a command to send SABM and make rfcomm connection?
Regards
Maciej
[-- Attachment #2: Type: text/html, Size: 1021 bytes --]
next reply other threads:[~2004-04-01 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 23:12 zubiwat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 14:49 [Bluez-devel] New BQB Halam Rose
2004-04-09 11:44 ` [Bluez-devel] rfcomm Problem amine
2004-04-09 11:49 ` [Bluez-devel] Rfcomm problem amine
2004-04-09 12:05 ` Marcel Holtmann
2004-04-09 12:32 ` amine
2004-04-09 16:09 ` 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='008a01c4183e$d14649a0$fcca010a@lysydziadek' \
--to=zubiwat@poczta.onet.pl \
--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