From: "Tianlei Zhao" <ztl.post@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci data flow
Date: Tue, 2 Jan 2007 17:16:28 +0800 [thread overview]
Message-ID: <6af20b8d0701020116q53944d1ct6825712e761d3afc@mail.gmail.com> (raw)
In-Reply-To: <4f436aae0612241219n2904ee46p7dfe9328afddf254@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 572 bytes --]
You can resort to the book "Linux Network Architecture" which has a skeletal
description of linux bluetooth stack.
On 12/25/06, Choi Sonim <choisonim@gmail.com> wrote:
>
> Hi all,
>
> I'm trying to understand the full loop of low level data flow
> when using a serial bluetooth device.
> Can someone please explain it in terms of kernel file names / functions ?
>
> User writing -> hci_sock_sendmsg -> hci_sched_tx ?
>
> User reading -> hci_sock_recvmsg -> ?
>
> where are the regular serial/uart functions are called ?
> where are the hci_ldisc.c functions called ?
>
>
[-- Attachment #1.2: Type: text/html, Size: 893 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-02 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 20:19 [Bluez-devel] hci data flow Choi Sonim
2007-01-02 9:16 ` Tianlei Zhao [this message]
2007-01-02 11:22 ` Choi Sonim
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=6af20b8d0701020116q53944d1ct6825712e761d3afc@mail.gmail.com \
--to=ztl.post@gmail.com \
--cc=bluez-devel@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