Date: Wed, 6 Dec 2006 16:49:14 -0200
From: Cris <ml133@netpole.com.br>
To: bluez-devel@lists.sourceforge.net
Message-Id: <20061206164914.6718738c.ml133@netpole.com.br>
In-Reply-To: <1165418898.2756.84.camel@localhost>
References: <20061206111617.d8f16a0c.ml133@netpole.com.br>
	<1165412385.2756.52.camel@localhost>
	<20061206131754.39cddee0.ml133@netpole.com.br>
	<1165418898.2756.84.camel@localhost>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] suggestion for device control
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

On Wed, 06 Dec 2006 16:28:18 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:

> > Hm. With raw, you do mean:
> > 
> >   socket (AF_BLUETOOTH, SOCK_RAW, BTPROTO_HCI);
> > 
> > right? or is there something else I need to set to raw?
> 
> that is not enough. You have to set the device into raw mode. Not only
> open the raw socket. Check the source code for examples.

Right. Forgot to mention

	ioctl (sd, HCISETRAW, 1);

This was already in my code which noticed kernel interference. And
I've set all bits for events and packet types (if that matters
regarding raw mode) when calling setsockopt with a filter. I'm looking
at hcidump.c and can't see anything else which might be related to
setting a device into raw mode. Should I see some other source?  What
else do I need?

-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel