From: "vaishali paisal" <vaishalipaisal@rediffmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Exactly how the sockets are being used in between the user space and kernel?
Date: 14 Apr 2005 10:29:14 -0000 [thread overview]
Message-ID: <20050414102914.4371.qmail@webmail17.rediffmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
Hello Marcel,
Thanks for replying to my question.Can u please explain me how the socket communication is going on between the user space and kernel space?
I can find out the code defining new address familiy AF_BLUETOOTH.then new protocols for L2CAP,HCI and RFCOMM.
in bluez utilities i can find that in files like l2test.c the calls are being made to socket functions.
But i m unable to find out exactly how the other side i mean the kernel handles the socket calls.
If u can provide a sample code just expalining the socket concept i would be grateful to u.
Regards
vaishali
On Tue, 05 Apr 2005 Marcel Holtmann wrote :
>Hi,
>
> > I have a small problem in understanding the blueZ source code for
> > kernel 2.6.11.I am unable to find out exactly how the kernel
> > implementations of the l2cap layer,hcilayer and rfcomm layer are
> > interacting amongst themselves ?As well as how they interact with the
> > user space libraries?
> >
> > I have seen some functions in l2cap.c calling functions from
> > hci_core.c which have been put as EXPORT_SYMBOL() in hci_core.c.
> > Is it the way they are communicating or am i missing something?
>
>the module interaction is done by the exported symbols as you already
>realized. The upper layer modules like RFCOMM, BNEP etc. are using the
>L2CAP socket interface inside the kernel. All userspace tools are using
>the ioctls and the socket interfaces.
>
>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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-users
[-- Attachment #2: Type: text/html, Size: 2510 bytes --]
next reply other threads:[~2005-04-14 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 10:29 vaishali paisal [this message]
2005-04-14 10:38 ` [Bluez-users] Exactly how the sockets are being used in between the user space and kernel? Marcel Holtmann
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=20050414102914.4371.qmail@webmail17.rediffmail.com \
--to=vaishalipaisal@rediffmail.com \
--cc=bluez-users@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