From: "Martin Röhricht" <ml@felicis.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Question about L2CAP sockets
Date: Mon, 13 Mar 2006 10:45:28 +0100 [thread overview]
Message-ID: <1142243128.30440.15.camel@localhost.localdomain> (raw)
Hello together,
I'm currently recoding some functions to provide Flow Control mechanism
on the L2CAP layer. Incoming Configuration Requests, Configuration
Responses and Information Requests are mostly done. Now I try to do the
corresponding work for an incoming Information Response. In order to
keep track of the results (let's say I sent an info request about
supported flow control) I need to store those results somewhere from
where I can use them for a reasonable configuration request (if the
remote peer doesn't support Flow Control, then we don't need request any
Flow Control options any more). I thought these pieces of information
belong to the corresponding socket, but now I have quite some trouble to
access the socket struct from l2cap_information_rsp() as the only
informational field I have is the l2cap_conn struct.
So is there a way to obtain the socket just from the connection struct?
My only idea is to use the function:
static inline struct *l2cap_get_chan_by_ident(struct l2cap_chan_list *l,
u8 ident)
as we have two candidate fields -- rx_ident and tx_ident -- in our
connection struct. But I don't know if that might work.
Is there anybody who may help me out a bit with the l2cap stuff?
Martin
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-03-13 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 9:45 Martin Röhricht [this message]
2006-03-13 10:54 ` [Bluez-devel] Question about L2CAP sockets Martin Röhricht
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=1142243128.30440.15.camel@localhost.localdomain \
--to=ml@felicis.org \
--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