From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Understanding BlueZ source code
Date: Thu, 02 Dec 2004 14:10:05 +0100 [thread overview]
Message-ID: <1101993005.7350.2.camel@pegasus> (raw)
In-Reply-To: <20041202130115.19341.qmail@web53207.mail.yahoo.com>
Hi Filipa,
> I need to analyze the Bluetooth code so I could
> identify the most computer intensive functions. As
> BlueZ is a well tested stack I decided to profile it.
>
> For that, I need the .c files and not only the .o
> files, so I cannot use the patches to include BlueZ in
> the kernel. I decided to use the old bluez-kernel-2.3
> package. I know that it is not the latest version, but
> I think it is the only way for me to access the .c
> files, am I right?
you are kidding me, right?
> Another question is that I only need the bluetooth
> stack and the drivers. That is included on the
> bluez-kernel package or I also have to use
> bluez-utils and bluez-lib?
You need the Bluetooth subsystem in the Linux kernel, the HCI drivers,
the Bluetooth library and the tools. However it actually depends on what
part you wanna profile. Bluetooth is not a small piece of software.
> And finally, if someone could give a link to the
> description of the code so I could understand the
> BlueZ stack, that would be great! The best I could
> find was Linux Unwired, but they describe more how to
> install and work with BlueZ, not really how BlueZ is
> done.
Use the source, Luke ;)
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-12-02 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 13:01 [Bluez-users] Understanding BlueZ source code Filipa Duarte
2004-12-02 13:10 ` 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=1101993005.7350.2.camel@pegasus \
--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