From: "Martin Röhricht" <ml@felicis.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Question about L2CAP sockets
Date: Mon, 13 Mar 2006 11:54:04 +0100 [thread overview]
Message-ID: <1142247244.10826.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1142243128.30440.15.camel@localhost.localdomain>
Am Montag, den 13.03.2006, 10:45 +0100 schrieb Martin R=F6hricht:
> So is there a way to obtain the socket just from the connection struct?
>=20
> 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.
I think I managed to use the right function arguments. My current
solution looks like this:
static inline int l2cap_information_rsp(struct l2cap_conn *conn, struct
l2cap_cmd_hdr *cmd, u8 *data)
{
[...]
struct sock *sk;
[...]
if (!(sk =3D l2cap_get_chan_by_ident(&conn->chan_list, cmd->ident)))
return 0;
[...]
l2cap_pi(sk)->info_mtu =3D __le16_to_cpup((__le16 *) rsp->data);
[...]
}
I tried to test this with two Siemens mobilephones (S55 and S75) and a
Windows XP machine, but none of them seems to make use of any
information requests at all ...=20
Perhaps somebody knows of a device that tries to inform itself about
it's remote partner before sending requests?
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
prev parent reply other threads:[~2006-03-13 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 9:45 [Bluez-devel] Question about L2CAP sockets Martin Röhricht
2006-03-13 10:54 ` Martin Röhricht [this message]
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=1142247244.10826.6.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