From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] broadcast packets
Date: Wed, 11 Jan 2006 09:36:15 +0100 [thread overview]
Message-ID: <1136968575.26114.8.camel@localhost.localdomain> (raw)
In-Reply-To: <43C4C236.5060100@in.tum.de>
Hi Aleksandar,
> Marcel, could you please answer me that ? :)
I already told you everything I know and I have no idea why you still
stick to the broadcast thing. Once you have established the piconet
between two devices, you can use it to transfer data. Doing everything
on HCI level is not a good idea. Use at least the L2CAP level for it,
but you might need to add some kernel code to make it work properly. The
broadcast stuff is not really used in any Bluetooth application so far.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-11 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 23:14 [Bluez-users] ms intellimouse/wheel p er
2006-01-05 0:26 ` Marcel Holtmann
2006-01-05 13:06 ` dave sailer
2006-01-07 17:24 ` [Bluez-users] " Nicolas STRANSKY
2006-01-08 15:53 ` [Bluez-users] broadcast packets Aleksandar Kanchev
2006-01-11 8:30 ` Aleksandar Kanchev
2006-01-11 8:36 ` Marcel Holtmann [this message]
2006-02-05 21:54 ` Aleksandar Kanchev
[not found] <443E0664.50904@sacet.com>
[not found] ` <443E08C5.7010307@sacet.com>
2006-04-13 8:22 ` [bluez-users] Broadcast Packets Laurent DANIEL
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=1136968575.26114.8.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-users@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).