From: "vaishali paisal" <vaishalipaisal@rediffmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Can anybody help plz?
Date: 5 Apr 2005 11:46:04 -0000 [thread overview]
Message-ID: <20050405114604.26990.qmail@webmail18.rediffmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hello all,
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?
I am new to BlueZ and kernel programming stuff.
Thanks in advance.
[-- Attachment #2: Type: text/html, Size: 862 bytes --]
next reply other threads:[~2005-04-05 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 11:46 vaishali paisal [this message]
2005-04-05 15:14 ` [Bluez-users] Can anybody help plz? 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=20050405114604.26990.qmail@webmail18.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