From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Pavan Savoy <pavan_savoy@yahoo.co.in>
Cc: linux-bluetooth@vger.kernel.org, shitiz_kumar@ti.com
Subject: Re: l2cap connection id in user-space
Date: Tue, 13 Apr 2010 18:39:38 -0300 [thread overview]
Message-ID: <20100413213938.GA1365@vigoh> (raw)
In-Reply-To: <956973.57311.qm@web94903.mail.in2.yahoo.com>
Hi Pavan,
* Pavan Savoy <pavan_savoy@yahoo.co.in> [2010-04-14 02:54:00 +0530]:
>
> --- On Wed, 14/4/10, Gustavo F. Padovan <gustavo@padovan.org> wrote:
>
> > From: Gustavo F. Padovan <gustavo@padovan.org>
> > Subject: Re: l2cap connection id in user-space
> > To: "Pavan Savoy" <pavan_savoy@yahoo.co.in>
> > Cc: linux-bluetooth@vger.kernel.org, shitiz_kumar@ti.com
> > Date: Wednesday, 14 April, 2010, 2:49 AM
> > Hi Pavan,
> >
> > * Pavan Savoy <pavan_savoy@yahoo.co.in>
> > [2010-04-14 02:26:41 +0530]:
> >
> > > Is there a possibility as of now for me to extract the
> > l2cap connection ID into my application ?
> >
> > bluez-hcidump does that. Look to its source code to learn
> > how.
>
> Yeah, correct, it does.
> However for that wouldn't I have to set filter for all ACL (or L2CAP) packets to even start receiving ACL (or L2CAP) packets ?
> strip off the l2cap_hdr and then get the channel ID from it.
>
> I was more or less looking to add in 1 more getsockopt option to specifically request for the l2cap_hdr ? (like the imtu/omtu which happens currently).
> Wouldn't this be the right way ?
No, we do not want such info on getsockopt. If you do that you'll have
to mantain it by yourself, which is not a good idea. The cid is L2CAP
specific, upper layers should not care about it.
>
> > >
> > > I require 2 sets of information about an L2CAP
> > connection in my bluetooth application, I require the
> > connection ID on connection to a remote headset/sink, and
> > also the maximum packet size for that connection (which I
> > think is the MTU, I can get via the getsockopt).
> > >
> >
--
Gustavo F. Padovan
http://padovan.org
next prev parent reply other threads:[~2010-04-13 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 20:56 l2cap connection id in user-space Pavan Savoy
2010-04-13 21:19 ` Gustavo F. Padovan
2010-04-13 21:24 ` Pavan Savoy
2010-04-13 21:39 ` Gustavo F. Padovan [this message]
2010-04-14 0:59 ` Marcel Holtmann
2010-04-14 5:51 ` Gustavo F. Padovan
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=20100413213938.GA1365@vigoh \
--to=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavan_savoy@yahoo.co.in \
--cc=shitiz_kumar@ti.com \
/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).