From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: RE: [Bluez-devel] HCI data packet
Date: Mon, 05 Sep 2005 14:00:28 +0200 [thread overview]
Message-ID: <1125921628.11955.6.camel@pegasus> (raw)
In-Reply-To: <20050901145400.BB3131EC845@mrelay1.st2.lyceu.net>
Hi Esther,
> Regarding HCI data packets and BlueZ...
>
> If I use the BlueZ command "hci_create_connection" and connect to another
> device, how do I sent an HCI data packet to this device?
you need to use the raw socket for it and then follow the H:4 protocol,
but doing any communication this way is not a good idea. You have to
deal with different packet sizes and handle the ACL-cont flag. Even for
a very simple protocol you should use L2CAP. The overhead of L2CAP is
really not that much.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-05 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 14:54 [Bluez-devel] HCI data packet Esther Lopez
2005-09-05 12:00 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 9:58 Esther Lopez
2005-08-24 10:01 ` Marcel Holtmann
2005-08-24 14:31 ` Esther Lopez
2005-08-24 15:14 ` Marcel Holtmann
2005-08-25 16:45 ` Esther Lopez
2005-09-01 14:40 ` Esther Lopez
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=1125921628.11955.6.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.