From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Exactly how the sockets are being used in between the user space and kernel?
Date: Thu, 14 Apr 2005 12:38:19 +0200 [thread overview]
Message-ID: <1113475099.8989.8.camel@pegasus> (raw)
In-Reply-To: <20050414102914.4371.qmail@webmail17.rediffmail.com>
Hi Vaishali,
> 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.
this mailing list (or any other BlueZ related list) is not for educating
you in how sockets work. Get yourself a book about that topic. For
example Linux Device Drivers.
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
prev parent reply other threads:[~2005-04-14 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 10:29 [Bluez-users] Exactly how the sockets are being used in between the user space and kernel? vaishali paisal
2005-04-14 10:38 ` 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=1113475099.8989.8.camel@pegasus \
--to=marcel@holtmann.org \
--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