Linux bluetooth development
 help / color / mirror / Atom feed
From: "Waldemar Rymarkiewicz" <waldemar.rymarkiewicz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Are there any docs to BlueZ implementation?
Date: Mon, 11 Dec 2006 10:03:39 +0100	[thread overview]
Message-ID: <9ed2cedd0612110103n56a873d7yb7bb4b1d88031ab1@mail.gmail.com> (raw)
In-Reply-To: <1165739418.5945.7.camel@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1800 bytes --]

Martin,

For sure will help me. Thanks,

Waldek


2006/12/10, Martin Röhricht <ml@felicis.org>:
>
> Hi Waldek,
>
> Am Freitag, den 08.12.2006, 17:25 +0100 schrieb Waldemar Rymarkiewicz:
> > Can I find any technical docs concernig BlueZ implementation (what,
> > where, data flow etc.)?  Is reverse engineering the only way to find
> > out how the stuff works?
> > I've  worked with Qualcomm BT stack (QBT) and wanna take a look what
> > is going on in BlueZ. Unfortunately have not experience with linux
> > kernel hacking :/ ....
>
> the implementation of L2CAP Flow Control Mode ended in a study thesis
> for my university. The thesis itself contains some information about my
> experiences in BlueZ kernel hacking and is written in English -- this
> may be worth a look:
> http://www.roehricht.info/files/studienarbeit_bluez.pdf
>
> Besides that it is rather hard to find BlueZ specific documentation.
> Mainly the source is the documentation. Anyway the source is easy to
> read once you got the basic understanding from the specification.
> You will mainly need the official specification as a reference. At the
> end of my thesis is a bibliography with some useful books that might
> help you, too.
>
> Martin
>
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #1.2: Type: text/html, Size: 2404 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

      reply	other threads:[~2006-12-11  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 16:25 [Bluez-devel] Are there any docs to BlueZ implementation? Waldemar Rymarkiewicz
2006-12-10  8:30 ` Martin Röhricht
2006-12-11  9:03   ` Waldemar Rymarkiewicz [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=9ed2cedd0612110103n56a873d7yb7bb4b1d88031ab1@mail.gmail.com \
    --to=waldemar.rymarkiewicz@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