From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] How does data flow from USB Core to the bluetooth protocol stack
Date: Fri, 10 Feb 2006 02:00:52 +0100 [thread overview]
Message-ID: <1139533252.17280.40.camel@localhost> (raw)
In-Reply-To: <20060209125112.12551.qmail@web36111.mail.mud.yahoo.com>
Hi Swathi,
> I am a research student and i am trying to trace the
> working of Bluez.
> I was able to find out how the communication between
> the bluetooth USB adapter and host takes place. ie how
> the bluetooth device driver gets loaded and how the
> data collected in the bluetooth device driver is being
> passed onto the actual USB driver.
> I was not able to find out how the USB core passes the
> data which it collected from the bluetooth device
> driver onto the bluetooth protocol stack. ie how the
> kernel knows that this data belongs to bluez
the hci_usb driver attaches to the USB core and the Bluetooth core and
deals with all these things. Start looking at the source code.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-02-10 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 12:51 [Bluez-users] How does data flow from USB Core to the bluetooth protocol stack Swathi Mathur80
2006-02-10 1: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=1139533252.17280.40.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).