From: "Alfredo Dal'Ava Júnior" <alfredo.dalava@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Sample protocol over L2CAP
Date: Sat, 19 Nov 2005 18:14:52 -0200 [thread overview]
Message-ID: <437F87BC.2090907@gmail.com> (raw)
Hi All,
I'm looking for a start point to develop a new protocol over the L2CAP.
Any of you have a sample code?
Thanks,
[]s
Alfredo
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-11-19 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 20:14 Alfredo Dal'Ava Júnior [this message]
2005-11-19 20:24 ` [Bluez-devel] Sample protocol over L2CAP Collin R. Mulliner
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=437F87BC.2090907@gmail.com \
--to=alfredo.dalava@gmail.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;
as well as URLs for NNTP newsgroup(s).