public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Cris <ml133@netpole.com.br>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] suggestion for device control
Date: Wed, 6 Dec 2006 13:17:54 -0200	[thread overview]
Message-ID: <20061206131754.39cddee0.ml133@netpole.com.br> (raw)
In-Reply-To: <1165412385.2756.52.camel@localhost>

On Wed, 06 Dec 2006 14:39:45 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:

> you can tell the kernel to switch a HCI device into raw mode and after
> that point you have full control over that device.

I am opening the devices in raw mode, but nevertheless I capture
reconfiguration commands from the kernel at connection time. I didn't
yet reach the point to be able to tell how much the kernel actually
interfers, but it does act at connection configuration time and
l2cap/rfcomm do kick in on raw sockets. I even tried to unload the
l2cap/rfcomm kernel modules, but they get reloaded at some point. Is
there something else I have to switch off? (I did stop the bluetooth
daemons like hcid, sdpd, rfcommd).

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?

Thanks,

-- 
Cris

-------------------------------------------------------------------------
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

  reply	other threads:[~2006-12-06 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 13:16 [Bluez-devel] suggestion for device control Cris
2006-12-06 13:39 ` Marcel Holtmann
2006-12-06 15:17   ` Cris [this message]
2006-12-06 15:28     ` Marcel Holtmann
2006-12-06 18:49       ` Cris
2006-12-08 10:16         ` Marcel Holtmann
2006-12-08 11:24           ` Cris

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=20061206131754.39cddee0.ml133@netpole.com.br \
    --to=ml133@netpole.com.br \
    --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