From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtman.org,
"Gustavo F. Padovan" <padovan@profusion.mobi>
Subject: Re: [PATCH 2/2] Bluetooth: Add Fixed Channels support to connect()
Date: Mon, 12 Jul 2010 18:46:52 -0300 [thread overview]
Message-ID: <1278971212.6282.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1278969545-26864-2-git-send-email-gustavo@padovan.org>
Hi Gustavo,
> All the Fixed Channel shall be set up with SOCK_DGRAM passing the channel
> id too. If you don't inform the channel id, L2CAP will use the
> Connectionless channel (0x0002), which was already the default channel for
> SOCK_DGRAM.
we actually can't do that. So the fixed channel have specific types
assigned with it. For example LE configures the ATT channel in basic
mode and HS uses ERTM on the AMP manager protocol.
However the only channel that we currently wanna access from user space
with SOCK_SEQPACKET is the ATT channel on LE. So we should disallow any
other access to fixed channels and use SOCK_DGRAM for raw access to the
signal channel as before. And SOCK_SEQPACKET for the ATT channel. All
other attempts to bind or connect a fixed channel should be rejected for
now.
Regards
Marcel
next prev parent reply other threads:[~2010-07-12 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 21:19 [PATCH 1/2] Bluetooth: Add Fixed Channels support to bind syscall Gustavo F. Padovan
2010-07-12 21:19 ` [PATCH 2/2] Bluetooth: Add Fixed Channels support to connect() Gustavo F. Padovan
2010-07-12 21:46 ` Marcel Holtmann [this message]
2010-07-13 17:26 ` [PATCH 1/2] Bluetooth: Add Fixed Channels support to bind syscall Anderson Lizardo
2010-07-13 17:30 ` Anderson Lizardo
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=1278971212.6282.7.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtman.org \
--cc=padovan@profusion.mobi \
/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).