From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Interwork of RFCOMM and L2CAP layers
Date: Thu, 16 Dec 2004 21:00:35 +0100 [thread overview]
Message-ID: <1103227236.6325.12.camel@notepaq> (raw)
In-Reply-To: <20041216134138.6218.qmail@web53205.mail.yahoo.com>
Hi Filipa,
> I am not a kernel developer but I would like to do
> profiling in BlueZ code as part of my PhD research,
> specifically on RFCOMM/L2CAP layers. I took the source
> code from my 2.4.22 kernel.
>
> I was expecting to see some functions on the RFCOMM
> files calling functions on the L2CAP files, as RFCOMM
> is a layer on top of the L2CAP layer. However I could
> not find any (actually there is one: rfcomm_init calls
> l2cap_load; but this last function is a dummy
> function).
>
> Could you please tell me where I could find
> information on how the RFCOMM and L2CAP layers
> interwork in the BlueZ implementation (I, of course,
> tryed Google and BlueZ web sites but I could not find
> information)?
the RFCOMM uses in-kernel socket programming to send or retrieve data
from the L2CAP layer.
> I would be particularly grateful if someone could give
> directions on how to use the BlueZ stack in a simple
> user space mode.
Check out l2test or rctest. This is all about socket programming.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-12-16 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 13:41 [Bluez-devel] Interwork of RFCOMM and L2CAP layers Filipa Duarte
2004-12-16 20:00 ` Marcel Holtmann [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=1103227236.6325.12.camel@notepaq \
--to=marcel@holtmann.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