Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Can anybody help plz?
Date: Tue, 05 Apr 2005 17:14:41 +0200	[thread overview]
Message-ID: <1112714081.12406.45.camel@notepaq> (raw)
In-Reply-To: <20050405114604.26990.qmail@webmail18.rediffmail.com>

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

      reply	other threads:[~2005-04-05 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 11:46 [Bluez-users] Can anybody help plz? vaishali  paisal
2005-04-05 15:14 ` 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=1112714081.12406.45.camel@notepaq \
    --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