From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] raw mode
Date: Thu, 12 Apr 2007 12:26:51 +0200 [thread overview]
Message-ID: <1176373611.7049.14.camel@violet> (raw)
In-Reply-To: <46150ADA.1000503@gmx.de>
Hi Sebastian,
> if I simply change the product ID of my CSR dongle from
> 0a12:0001 to 0a12:0002 hciconfig will report "RAW" as device
> mode after rebooting:
> hci0: Type: USB
> BD Address: 00:16:41:18:7A:8C ACL MTU: 0:0 SCO MTU: 0:0
> UP RUNNING RAW
> RX bytes:66 acl:0 sco:0 events:0 errors:0
> TX bytes:15 acl:0 sco:0 commands:5 errors:0
>
>
> Does the Bluetooth drivers only assume it must be a raw mode
> because of the product ID? Or is there a "real" raw mode detected?
> And if there is such a raw mode how can raw frames be retrieved?
the RAW flag for HCI indicates the kernel doesn't handle any higher
protocol like L2CAP or RFCOMM for this device. It means you have to do
everything by yourself. So in theory you can write your own Bluetooth
protocol stack in userspace accessing the HCI in RAW mode and make use
of the BlueZ transport drivers.
The RAW mode is not a sniffer mode. However it gets set if you attach a
Bluetooth dongle from Frontline. They look like normal HCI devices, but
they are not.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-04-12 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 14:42 [Bluez-users] raw mode S. Vandersee
2007-04-12 10:13 ` Peter Stephenson
2007-04-12 10:26 ` Marcel Holtmann [this message]
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=1176373611.7049.14.camel@violet \
--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